Hi Community,
i have problems to connect to our Exchange Server.
I made these configs in the Altlassian Jira Service Properties
-Djavax.net.debug=ssl:handshake:verbose
-Dmail.imaps.auth.plain.disable=true
-Dmail.imap.auth.plain.disable=true
-Dmail.debug=true
Powershell Test-NetConnection on Port 993 works.
I set the Exchange Server2013 IMAP4 Login method to "Basc authentication"
Here is the Debug Report.
2018-11-02 09:41:19,679 DEBUG [EXCHANGESERVER] https-jsse-nio-443-exec-24 USERXXX 581x235x1 1iah6f6 /secure/admin/VerifyPopServerConnection!update.jspa Getting session
2018-11-02 09:41:19,679 DEBUG [EXCHANGESERVER] https-jsse-nio-443-exec-24 USERXXX 581x235x1 1iah6f6 /secure/admin/VerifyPopServerConnection!update.jspa Debug messages from JavaMail session initialization will not appear in this log. These messages are sent to standard out.
2018-11-02 09:41:19,679 DEBUG [EXCHANGESERVER] https-jsse-nio-443-exec-24 USERXXX 581x235x1 1iah6f6 /secure/admin/VerifyPopServerConnection!update.jspa Session providers: [[javax.mail.Provider[STORE,imap,com.sun.mail.imap.IMAPStore,Oracle], javax.mail.Provider[STORE,imaps,com.sun.mail.imap.IMAPSSLStore,Oracle], javax.mail.Provider[TRANSPORT,smtp,com.sun.mail.smtp.SMTPTransport,Oracle], javax.mail.Provider[TRANSPORT,smtps,com.sun.mail.smtp.SMTPSSLTransport,Oracle], javax.mail.Provider[STORE,pop3,com.sun.mail.pop3.POP3Store,Oracle], javax.mail.Provider[STORE,pop3s,com.sun.mail.pop3.POP3SSLStore,Oracle]]]
2018-11-02 09:41:19,679 DEBUG [EXCHANGESERVER] https-jsse-nio-443-exec-24 USERXXX 581x235x1 1iah6f6 /secure/admin/VerifyPopServerConnection!update.jspa Session addressMap: [{rfc822=smtp}]
2018-11-02 09:41:19,679 DEBUG [EXCHANGESERVER] https-jsse-nio-443-exec-24 USERXXX 581x235x1 1iah6f6 /secure/admin/VerifyPopServerConnection!update.jspa DEBUG: getProvider() returning javax.mail.Provider[STORE,imaps,com.sun.mail.imap.IMAPSSLStore,Oracle]
2018-11-02 09:41:19,679 DEBUG [EXCHANGESERVER] https-jsse-nio-443-exec-24 USERXXX 581x235x1 1iah6f6 /secure/admin/VerifyPopServerConnection!update.jspa DEBUG IMAPS: mail.imap.fetchsize: 16384
2018-11-02 09:41:19,679 DEBUG [EXCHANGESERVER] https-jsse-nio-443-exec-24 USERXXX 581x235x1 1iah6f6 /secure/admin/VerifyPopServerConnection!update.jspa DEBUG IMAPS: mail.imap.ignorebodystructuresize: false
2018-11-02 09:41:19,679 DEBUG [EXCHANGESERVER] https-jsse-nio-443-exec-24 USERXXX 581x235x1 1iah6f6 /secure/admin/VerifyPopServerConnection!update.jspa DEBUG IMAPS: mail.imap.statuscachetimeout: 1000
2018-11-02 09:41:19,679 DEBUG [EXCHANGESERVER] https-jsse-nio-443-exec-24 USERXXX 581x235x1 1iah6f6 /secure/admin/VerifyPopServerConnection!update.jspa DEBUG IMAPS: mail.imap.appendbuffersize: -1
2018-11-02 09:41:19,679 DEBUG [EXCHANGESERVER] https-jsse-nio-443-exec-24 USERXXX 581x235x1 1iah6f6 /secure/admin/VerifyPopServerConnection!update.jspa DEBUG IMAPS: mail.imap.minidletime: 10
2018-11-02 09:41:19,679 DEBUG [EXCHANGESERVER] https-jsse-nio-443-exec-24 USERXXX 581x235x1 1iah6f6 /secure/admin/VerifyPopServerConnection!update.jspa DEBUG IMAPS: closeFoldersOnStoreFailure
2018-11-02 09:41:19,679 DEBUG [EXCHANGESERVER] https-jsse-nio-443-exec-24 USERXXX 581x235x1 1iah6f6 /secure/admin/VerifyPopServerConnection!update.jspa DEBUG IMAPS: trying to connect to host "EXCHANGESERVER.deloitte-cic.de", port 993, isSSL true
2018-11-02 09:41:19,742 DEBUG [EXCHANGESERVER] https-jsse-nio-443-exec-24 USERXXX 581x235x1 1iah6f6 /secure/admin/VerifyPopServerConnection!update.jspa * OK The Microsoft Exchange IMAP4 service is ready.
2018-11-02 09:41:19,742 DEBUG [EXCHANGESERVER] https-jsse-nio-443-exec-24 USERXXX 581x235x1 1iah6f6 /secure/admin/VerifyPopServerConnection!update.jspa A0 CAPABILITY
2018-11-02 09:41:19,742 DEBUG [EXCHANGESERVER] https-jsse-nio-443-exec-24 USERXXX 581x235x1 1iah6f6 /secure/admin/VerifyPopServerConnection!update.jspa * CAPABILITY IMAP4 IMAP4rev1 AUTH=PLAIN AUTH=NTLM AUTH=GSSAPI UIDPLUS MOVE ID CHILDREN IDLE NAMESPACE LITERAL+
2018-11-02 09:41:19,742 DEBUG [EXCHANGESERVER] https-jsse-nio-443-exec-24 USERXXX 581x235x1 1iah6f6 /secure/admin/VerifyPopServerConnection!update.jspa A0 OK CAPABILITY completed.
2018-11-02 09:41:19,742 DEBUG [EXCHANGESERVER] https-jsse-nio-443-exec-24 USERXXX 581x235x1 1iah6f6 /secure/admin/VerifyPopServerConnection!update.jspa DEBUG IMAPS: AUTH: PLAIN
2018-11-02 09:41:19,742 DEBUG [EXCHANGESERVER] https-jsse-nio-443-exec-24 USERXXX 581x235x1 1iah6f6 /secure/admin/VerifyPopServerConnection!update.jspa DEBUG IMAPS: AUTH: NTLM
2018-11-02 09:41:19,742 DEBUG [EXCHANGESERVER] https-jsse-nio-443-exec-24 USERXXX 581x235x1 1iah6f6 /secure/admin/VerifyPopServerConnection!update.jspa DEBUG IMAPS: AUTH: GSSAPI
2018-11-02 09:41:19,742 DEBUG [EXCHANGESERVER] https-jsse-nio-443-exec-24 USERXXX 581x235x1 1iah6f6 /secure/admin/VerifyPopServerConnection!update.jspa DEBUG IMAPS: protocolConnect login, host=EXCHANGESERVER.DOMAIN.DE, user=Username@Domain.de, password=<non-null>
2018-11-02 09:41:19,742 DEBUG [EXCHANGESERVER] https-jsse-nio-443-exec-24 USERXXX 581x235x1 1iah6f6 /secure/admin/VerifyPopServerConnection!update.jspa DEBUG IMAPS: AUTHENTICATE PLAIN command trace suppressed
2018-11-02 09:41:29,744 DEBUG [EXCHANGESERVER] https-jsse-nio-443-exec-24 USERXXX 581x235x1 1iah6f6 /secure/admin/VerifyPopServerConnection!update.jspa DEBUG IMAPS: IMAPStore non-store connection dead
2018-11-02 09:41:29,744 DEBUG [EXCHANGESERVER] https-jsse-nio-443-exec-24 USERXXX 581x235x1 1iah6f6 /secure/admin/VerifyPopServerConnection!update.jspa DEBUG IMAPS: AUTHENTICATE PLAIN command result: * BYE JavaMail Exception: java.net.SocketTimeoutException: Read timed out
So can somebody help me? or give me a hint..
Best Regards Alex
This looks a little odd to me. Jira appears to be configured to try to connect to a POP mailbox, and it is reaching the mail server ok at first. But then it's getting responses that look like they are from an IMAP service.
Jira supports both, but it can't work if you tell it to connect to one with parameters built for the other. That's why you're getting time-outs - the IMAP server is expecting Jira to send it IMAP shaped data, and Jira is giving it POP stuff. The server ignores it and carries on waiting IMAP data, then timing out when Jira doesn't do it.
Have another look at the config - I suspect you just need to flip the Jira data over to say "use an IMAP connection" and re-use mostly the same data.
Hi thanks for the answer. But if i change the Protocol i get a TimeOut but if i Change the Protocol and the wrong Port i get the Imap4 or Pop3 message.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
What you need to do is line up the right settings.
The server appears to be running IMAP and not POP. I say this because your question says it is responding with "OK The Microsoft Exchange IMAP4 service is ready", and then in your comment, you get "read timed out" when you try the other.
So. You need to use IMAP settings to connect to an IMAP service.
The settings in your screenshot look correct, but I'm worried about two settings. Could you try testing with
Protocol: IMAP, Port: 993
Protocol: Secure_IMAP, port: <blank>
Protocol: IMAP, port: <blank>
If all of those fails, then you're going to need to talk to your email admins to find out what they're actually running the service on (type and port)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Nic,
im checked the Exchange Server settings, too. The Ports are correct and i tried to let the Ports Blank everytime the same fault. On each Protocol if i use Pop or Imap.
Thats why im here ;) i dont know what else can i do...
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
It is not clear what the "same fault" is on these.
Could you confirm exactly what error you get when you try IMAP on port 993?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Getting session
Debug messages from JavaMail session initialization will not appear in this log. These messages are sent to standard out.
Session providers: [[javax.mail.Provider[STORE,imap,com.sun.mail.imap.IMAPStore,Oracle], javax.mail.Provider[STORE,imaps,com.sun.mail.imap.IMAPSSLStore,Oracle], javax.mail.Provider[TRANSPORT,smtp,com.sun.mail.smtp.SMTPTransport,Oracle], javax.mail.Provider[TRANSPORT,smtps,com.sun.mail.smtp.SMTPSSLTransport,Oracle], javax.mail.Provider[STORE,pop3,com.sun.mail.pop3.POP3Store,Oracle], javax.mail.Provider[STORE,pop3s,com.sun.mail.pop3.POP3SSLStore,Oracle]]]
Session addressMap: [{rfc822=smtp}]
DEBUG: getProvider() returning javax.mail.Provider[STORE,imaps,com.sun.mail.imap.IMAPSSLStore,Oracle]
DEBUG IMAPS: mail.imap.fetchsize: 16384
DEBUG IMAPS: mail.imap.ignorebodystructuresize: false
DEBUG IMAPS: mail.imap.statuscachetimeout: 1000
DEBUG IMAPS: mail.imap.appendbuffersize: -1
DEBUG IMAPS: mail.imap.minidletime: 10
DEBUG IMAPS: closeFoldersOnStoreFailure
DEBUG IMAPS: trying to connect to host "XXXXX", port 993, isSSL true
* OK The Microsoft Exchange IMAP4 service is ready.
A0 CAPABILITY
* CAPABILITY IMAP4 IMAP4rev1 AUTH=PLAIN AUTH=NTLM AUTH=GSSAPI UIDPLUS MOVE ID CHILDREN IDLE NAMESPACE LITERAL+
A0 OK CAPABILITY completed.
DEBUG IMAPS: AUTH: PLAIN
DEBUG IMAPS: AUTH: NTLM
DEBUG IMAPS: AUTH: GSSAPI
DEBUG IMAPS: protocolConnect login, host=XXXXX, user=XXXXX, password=<non-null>
DEBUG IMAPS: AUTHENTICATE PLAIN command trace suppressed
DEBUG IMAPS: IMAPStore non-store connection dead
DEBUG IMAPS: AUTHENTICATE PLAIN command result: * BYE JavaMail Exception: java.net.SocketTimeoutException: Read timed out
Unfortunately no connection was possible. Review the errors below and rectify:
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
A timeout means that Jira is not handing over anything the IMAP server can work with.
It now looks like you've got all the settings right and consistent (both ends are now talking IMAP), but the mail server is not letting your Jira system in.
You now need to talk to the Exchange admins, as everything is right on the Jira side. They need to work out what is missing and tell you how to fix it.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.