You need to sign in to do that
Don't have an account?

Email2Case authenticating to Exchange Server 2007
Hi I'm trying to setup Email2Case and getting the following error:
ERROR Unable to connect to mail service.
Message: No login methods supported!;
nested exception is: com.sun.mail.iap.ProtocolException: No login methods supported!
Does anyone have instructions on Exchange 2007 setup? or any more info on this error?
<configFile>
<server1>
<url>mail.mydomain.com</url>
<protocol>imap</protocol>
<userName>support@mydomain.com</userName>
<password>myPassword</password>
<interval>5</interval>
<inbox>Inbox</inbox>
<readbox>movedToSalesForce</readbox>
<errorbox>error</errorbox>
</server1>
</configFile>
Message Edited by transcend on 02-20-2008 03:18 PM
ERROR Unable to connect to mail service.
Message: No login methods supported!;
nested exception is: com.sun.mail.iap.ProtocolException: No login methods supported!
Does anyone have instructions on Exchange 2007 setup? or any more info on this error?
<configFile>
<server1>
<url>mail.mydomain.com</url>
<protocol>imap</protocol>
<userName>support@mydomain.com</userName>
<password>myPassword</password>
<interval>5</interval>
<inbox>Inbox</inbox>
<readbox>movedToSalesForce</readbox>
<errorbox>error</errorbox>
</server1>
</configFile>
Message Edited by transcend on 02-20-2008 03:18 PM
you essentially create your generic email list in Exchange, and have it also deliver to the services email you generate in the org. that then will run an Apex Class you create.
there's an excellent example of creating tasks on the wiki that can easily be modified to create cases instead.
here's a code example that I have in play. I have an S-Control on the Case page layout that takes the webemail and webname fields and creates/updates a contact and associates it with the case, so i don't do it in the class itself, yet.
hope this helps
The one thing Paul's code won't do is thread emails into existing cases as E2C does. Don't worry, though, we're working on something for that... :)
I believe that's all E2C does, except it's more graceful in using a thread id, which we don't have in this scenario. Also, using an apex email service class allows you to be more creative with what happens _after_ you add the email to the existing case, like, changing status, reopening, etc.
is that pretty much what you were planning?
Message Edited by paul-lmi on 02-22-2008 02:39 PM
IMAP is enabled on my exchange server, but uses SSL, I don't see a way with Email2Case to specify SSL.
Could Apex Email Services be used to also create Contacts if a support case arrives from an unknown customer?
Thanks, Jay
If anyone gets some APEX code working that handles threading the emails to cases and new contact creation, please post. I don't have time at the moment to get that working, but that seems like a much better solution.
it takes a regex and searches the body of the email for it. returns the case.id, which will then trigger a new Task to be created rather than a Case, and in that Task, the WhatId is set to the CaseId, so it rolls up to the case.
After that, the Case status is changed to "Email from Customer", which effectively reopens it. I don't change the owner, as I use Escalation rules to do that if a case is in a certain status for too long (it will re-queue it).
How does this sound?
(Once I have threading fully tested, code covered, and running in our production environment, I'll post the code to the wiki and start on the Contact creation)
I eagerly await a chance to test!
:smileyhappy: Jay
Message: AUTHENTICATE failed.
...when trying to connect to Exchange 2007 (IMAP enabled, etc.)