Re: AUTHENTICATE PLAIN not working with Exchange 2007
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:arsl...@arslist.org] On Behalf Of Mitchell, Sharon N. (MSFC-IS30)[SAIC]
Sent: Tuesday, April 07, 2009 4:54 PM
To: arslist@ARSLIST.ORG
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:arsl...@arslist.org] On Behalf Of Grooms, Frederick W
Sent: Tuesday, April 07, 2009 4:03 PM
To: arslist@ARSLIST.ORG
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:arsl...@arslist.org] On Behalf Of strauss
Sent: Tuesday, April 07, 2009 2:51 PM
To: arslist@ARSLIST.ORG
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:arsl...@arslist.org] On Behalf Of Mitchell, Sharon N. (MSFC-IS30)[SAIC]
Sent: Tuesday, April 07, 2009 12:16 PM
To: arslist@ARSLIST.ORG
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
Re: AUTHENTICATE PLAIN not working with Exchange 2007
This worked! Thanks sooo much – to all of you that helped! I don’t know why I worked on this for days before turning to the list. Thanks again! Sharon From: Action Request System discussion list(ARSList) [mailto:arsl...@arslist.org] On Behalf Of Shyman, Jonathan Sent: Wednesday, April 08, 2009 9:16 AM To: arslist@ARSLIST.ORG Subject: Re: AUTHENTICATE PLAIN not working with Exchange 2007 Sharon, There is a batch file in the AREmail install folder that is used to install and uninstall the AREmail service on windows. It is called armaild.bat and looks something like this: @echo on rem Please note that paths CAN NOT include spaces rem %1 - Action to take; either install or uninstall rem %2 - Full Path to Java VM DLL ie. C:\Progra~1\Java\j2re1.4.1_01\bin\client\jvm.dll rem %3 - Email Daemon installation directory where libraries reside (arapi60.dll, arutil60.dll, armapi60.dll and jars) rem %4 - AR Library Version rem %5 - AR Server Name rem Example Usage : emaild.bat install C:\Progra~1\Java\j2re1.4.1_01\bin\client\jvm.dll C:\Progra~1\ARSyst~1\AREmail if %1 == install goto install if %1 == uninstall goto uninstall :install %~3\AREmaild -install BMC Remedy Email Engine - %5 %2 -Djava.library.path=%~3 -Djava.class.path=%~f3\emaildaemon.jar;%~f3\commons-configuration-1.3.jar;%~f3\commons-beanutils.jar;%~f3\commons-collections-3.2.jar;%~f3\commons-digester-1.7.jar;%~f3\commons-lang-2.2.jar;%~f3\icu4j.jar;%~f3\spring.jar;%~f3\commons-logging-1.1.jar;%~f3\commons-codec-1.3.jar;%~f3\Logger.jar;%~f3\log4j-1.2.14.jar;%~f3\arapi%4.jar;%~f3\arutil%4.jar;%~f3\arrpc%4.jar;%~f3\oncrpc.jar;%~f3\arcmn%4.jar;%~f3\activation.jar;%~f3\mail.jar;%~f3\imap.jar;%~f3\smtp.jar;%~f3\pop3.jar;%~f3\armapi%4.jar;%~f3;. -start com.bmc.arsys.emaildaemon.EmailDaemon -out %~f3\logs\stdout.log -err %~f3\logs\stderr.log -current %3 goto eof :uninstall %~3\AREmaild -uninstall BMC Remedy Email Engine - %5 goto eof :eof What you might be able to do is the following: 1. Modify the “-install” line above to include the java argument Fred gave you. In other words change: %~3\AREmaild -install BMC Remedy Email Engine - %5 %2 -Djava.library.path=%~3 -Djava.class.path=%~f3\emaildaemon.jar;%~f3\commons-configuration-1.3.jar;%~f3\commons-beanutils.jar;%~f3\commons-collections-3.2.jar;%~f3\commons-digester-1.7.jar;%~f3\commons-lang-2.2.jar;%~f3\icu4j.jar;%~f3\spring.jar;%~f3\commons-logging-1.1.jar;%~f3\commons-codec-1.3.jar;%~f3\Logger.jar;%~f3\log4j-1.2.14.jar;%~f3\arapi%4.jar;%~f3\arutil%4.jar;%~f3\arrpc%4.jar;%~f3\oncrpc.jar;%~f3\arcmn%4.jar;%~f3\activation.jar;%~f3\mail.jar;%~f3\imap.jar;%~f3\smtp.jar;%~f3\pop3.jar;%~f3\armapi%4.jar;%~f3;. -start com.bmc.arsys.emaildaemon.EmailDaemon -out %~f3\logs\stdout.log -err %~f3\logs\stderr.log -current %3 goto eof to %~3\AREmaild -install BMC Remedy Email Engine - %5 %2 -Djava.library.path=%~3 -Djava.class.path=%~f3\emaildaemon.jar;%~f3\commons-configuration-1.3.jar;%~f3\commons-beanutils.jar;%~f3\commons-collections-3.2.jar;%~f3\commons-digester-1.7.jar;%~f3\commons-lang-2.2.jar;%~f3\icu4j.jar;%~f3\spring.jar;%~f3\commons-logging-1.1.jar;%~f3\commons-codec-1.3.jar;%~f3\Logger.jar;%~f3\log4j-1.2.14.jar;%~f3\arapi%4.jar;%~f3\arutil%4.jar;%~f3\arrpc%4.jar;%~f3\oncrpc.jar;%~f3\arcmn%4.jar;%~f3\activation.jar;%~f3\mail.jar;%~f3\imap.jar;%~f3\smtp.jar;%~f3\pop3.jar;%~f3\armapi%4.jar;%~f3;. -Dmail.imap.auth.plain.disable=true -start com.bmc.arsys.emaildaemon.EmailDaemon -out %~f3\logs\stdout.log -err %~f3\logs\stderr.log -current %3 goto eof 2. Stop the email service and then go to a command prompt in the folder were the armaild.bat file is located and use it to remove and then reinstall the AREmail service. This should incorporate the new parameter in the service. You do this by running the uninstall command first like so: armaild uninstall full path to jvm.dll full path to email daemon libraries ar library version ar server name for example, on my VM this would be: armaild uninstall “C:\Program Files\Java\jre1.6.0_05\bin\client\jvm.dll” “C:\AR System\AREmail\VMWin2k3” 71 VMWIN2K3 Then check the services list on the server to make sure it goes away. Then add it back using: armaild install “C:\Program Files\Java\jre1.6.0_05\bin\client\jvm.dll” “C:\AR System\AREmail\VMWin2k3” 71 VMWIN2K3 Do not copy and paste the lines above. The windows command processor seems to not recognize the “ if you do and you’ll get errors. See if that works. J.T. Shyman Column Technologies Cell: 404-242-5407 From: Action Request System discussion list(ARSList) [mailto:arsl...@arslist.org] On Behalf Of Grooms, Frederick W Sent: Wednesday, April 08, 2009 9:42 AM To: arslist@ARSLIST.ORG Subject: Re: AUTHENTICATE PLAIN not working with Exchange 2007 Unfortunately I am a Unix person (All my ARS systems are on Unix servers). Maybe Christopher Strauss or another
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:arsl...@arslist.org] On Behalf Of Mitchell, Sharon N. (MSFC-IS30)[SAIC] Sent: Tuesday, April 07, 2009 12:16 PM To: arslist@ARSLIST.ORG 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
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:arsl...@arslist.org] On Behalf Of strauss
Sent: Tuesday, April 07, 2009 2:51 PM
To: arslist@ARSLIST.ORG
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:arsl...@arslist.org] On Behalf Of Mitchell, Sharon N. (MSFC-IS30)[SAIC]
Sent: Tuesday, April 07, 2009 12:16 PM
To: arslist@ARSLIST.ORG
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
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:arsl...@arslist.org] On Behalf Of Grooms, Frederick W
Sent: Tuesday, April 07, 2009 4:03 PM
To: arslist@ARSLIST.ORG
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:arsl...@arslist.org] On Behalf Of strauss
Sent: Tuesday, April 07, 2009 2:51 PM
To: arslist@ARSLIST.ORG
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:arsl...@arslist.org] On Behalf Of Mitchell, Sharon N. (MSFC-IS30)[SAIC]
Sent: Tuesday, April 07, 2009 12:16 PM
To: arslist@ARSLIST.ORG
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
