Unfortunately I am a Unix person (All my ARS systems are on Unix servers). Maybe Christopher Strauss or another Windows person can answer how to have the Windows service use the emailstart batch file (personally I thought that was what is supposed to be listed in the armonitor.conf (armonitor.cfg on windows) file) to actually run the email engine.
Fred From: Action Request System discussion list(ARSList) [mailto:[email protected]] On Behalf Of Mitchell, Sharon N. (MSFC-IS30)[SAIC] Sent: Tuesday, April 07, 2009 4:54 PM To: [email protected] Subject: Re: AUTHENTICATE PLAIN not working with Exchange 2007 Fred, Thank you!!! I added this to the debug file first, and it immediately received and processed the two emails that were stuck in the inbox. I sent another email to the dev server, added this to the emailstart.bat file and it worked too. However, when I send an email to the server (with the email engine running), it still gets stuck in the inbox. Even when I restart the email engine service, it stays in the inbox. I can run the emailstart (or debug) batch file, and the email is then received/processed. This is great progress… but any ideas on how to make this work all the time?? Another thing, and maybe I’m missing something….when I restart the email engine service, the stderr file is still showing Authentication failed error, but when I run the debug batch file, the error is not there ?? Thanks again, Sharon From: Action Request System discussion list(ARSList) [mailto:[email protected]] On Behalf Of Grooms, Frederick W Sent: Tuesday, April 07, 2009 4:03 PM To: [email protected] Subject: Re: AUTHENTICATE PLAIN not working with Exchange 2007 I’m wondering if this can be added to the emaild startup batch file the same way you trun on the debug. -Dmail.imap.auth.plain.disable=true Something like java -Dmail.debug=true -Dmail.imap.auth.plain.disable=true -Djava.library.path=${InstallPath} Fred From: Action Request System discussion list(ARSList) [mailto:[email protected]] On Behalf Of strauss Sent: Tuesday, April 07, 2009 2:51 PM To: [email protected] Subject: Re: AUTHENTICATE PLAIN not working with Exchange 2007 Well, on the Exchange 2007 server there is a setting under Server Configuration – Pop3 and IMAP – IMAP4 – Authentication tab – Logon Method that on my server defaulted to “Secure Login. A TLS connection is required for the client to authenticate to the server.” That is probably what your server has too, and when I monitor my aremail mailboxes from Outlook Express over IMAP, I have to use the SSL required checkboxes and SSL port in Advanced properties for the mailbox in Outlook Express in order for it to connect. I never ran into this with the sending mail client because I install Outlook 2007 and use MAPI, which uses a domain user for the mailbox, and the ARemail service actually runs under that same domain account. Outlook by default will make an encrypted connection to the Exchange server. The configuration on the Exchange server can also be changed in the dialog that I mentioned above to: “Plain text login (Basic authentication). No TLS connection is required for the client to authenticate to the server.” –OR- “Plain text authentication logon (integrated Windows authentication). No TLS connection is required for the client to authenticate to the server.” It looks like Exchange 2007 IMAP authentication can be set to two different plain text methods at the server-level, but your email admins will have to approve and perform that task. I have never had to change anything on the ARS side since I have always used MAPI with a mail client and mailbox profile installed on the AR server. Christopher Strauss, Ph.D. Call Tracking Administration Manager University of North Texas Computing & IT Center http://itsm.unt.edu/ From: Action Request System discussion list(ARSList) [mailto:[email protected]] On Behalf Of Mitchell, Sharon N. (MSFC-IS30)[SAIC] Sent: Tuesday, April 07, 2009 12:16 PM To: [email protected] Subject: AUTHENTICATE PLAIN not working with Exchange 2007 We just upgraded our dev server (and email engine) to 7.1 patch 6. We also installed JRE 1.5.0_18. Now we are changing our incoming email configuration (using IMAP with SSL required) to point to our Exchange 2007 server. It was working with Exchange 2003, but now it’s not with Exchange 2007. Here’s part of the debug file: DEBUG: getProvider() returning javax.mail.Provider[STORE,imap,com.sun.mail.imap.IMAPStore,Sun Microsystems, Inc] DEBUG: mail.imap.fetchsize: 16384 * OK The Microsoft Exchange IMAP4 service is ready. A0 CAPABILITY * CAPABILITY IMAP4 IMAP4rev1 AUTH=NTLM AUTH=GSSAPI AUTH=PLAIN IDLE NAMESPACE LITERAL+ A0 OK CAPABILITY completed. IMAP DEBUG: AUTH: NTLM IMAP DEBUG: AUTH: GSSAPI IMAP DEBUG: AUTH: PLAIN DEBUG: protocolConnect login, host=imap.ndc.nasa.gov, user=ndc\remedydev, password=<non-null> A1 AUTHENTICATE PLAIN + bmRjXG1zZmMtcmVtZWR5ZGV2AG5kY1xtc2ZjLXJlbWVkeWRldgAxcTJ3M2U0ciVUXlkmVSpJ A1 NO AUTHENTICATE failed. It looks like it’s not working because it uses AUTHENICATE PLAIN and Exchange 2007 doesn’t accept that (found that on a java sun forum). It says the work around is to disable AUTH PLAIN by using this command: prop.put("mail.imap.auth.plain.disable", "true"); My question is – where do you put this command? Is it on the Exchange server or the Remedy server? Remedy support says it should be changed on the Exchange server and our email guys say it should be changed on the Remedy server. If Remedy server, exactly where does it go? Any help would be greatly appreciated. Thanks, Sharon Windows 2003 AR Server/Email Engine 7.1 patch 6 Oracle 10g Exchange 2007
