Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage Connection reset when configuring Office365 IMAP Server for Jira Edited



We're currently running into an issue when setting up an IMAP configuration for incoming emails on our JIRA Server.  We have an account hosted at, and we can see the following options for connecting via POP or IMAP



Server name:
Port: 995
Encryption method: TLS



Server name:
Port: 993
Encryption method: TLS


We've used the these parameters to set up an IMAP server on our AWS Jira instance:


Host Name:

IMAP Port: 993

Timeout 20000

Username: username@<domain>.com


When trying to test the connection, we receive this message: 

Unfortunately no connection was possible. Review the errors below and rectify:

  • SocketException: Connection reset


We've tried the following to troubleshoot:

  • change the password/unlock the account.  This allows us to log in through office365's web UI, but we still get the connection reset error.
  • look at the logs.  After turning on DEBUG, we still only see the following in atlassian-jira.log (we're not seeing any useful stack traces in atlasian-jira.log or atlasian-jira-incoming-mail.log):

[c.a.j.p.mail.webwork.VerifyMailServer] Unable to connect to the server at due to the following exception: Connection reset

  • Test connectivity using openssl s_client
    • we used the following command to test the connection: 
    • openssl s_client -connect -crlf -servername
    • I'm able to connect to the server on my laptop:
    • subject=/C=US/ST=Washington/L=Redmond/O=Microsoft Corporation/
      issuer=/C=US/O=DigiCert Inc/CN=DigiCert Cloud Services CA-1
      No client certificate CA names sent
      Peer signing digest: SHA1
      Server Temp Key: ECDH, P-256, 256 bits
      SSL handshake has read 3863 bytes and written 461 bytes
      New, TLSv1/SSLv3, Cipher is ECDHE-RSA-AES256-GCM-SHA384
      Server public key is 2048 bit
      Secure Renegotiation IS supported
      Compression: NONE
      Expansion: NONE
      No ALPN negotiated


    • However, running the same command from my EC2 instance in AWS does not result in a connection
    • CONNECTED(00000003)
      no peer certificate available
      No client certificate CA names sent
      SSL handshake has read 0 bytes and written 319 bytes
      New, (NONE), Cipher is (NONE)
      Secure Renegotiation IS NOT supported
      Compression: NONE
      Expansion: NONE
      No ALPN negotiated
      Protocol : TLSv1.2
      Cipher : 0000
      Key-Arg : None
      Krb5 Principal: None
      PSK identity: None
      PSK identity hint: None
      Start Time: 1546003282
      Timeout : 300 (sec)
      Verify return code: 0 (ok)

Has anyone run into similar issues? 



After doing a little bit of testing, it looks like I can connect to IMAP from an instance in a public subnet.  However, our Jira instance is located in a private subnet.  Has anyone tried configuring an IMAP server for a Jira instance hosted in a private subnet?  Thanks again!


1 answer

We're having a similar issue.   I think it's due to the firewall blocking on the server.

But I suspect that another cause might be that we're running our test JIRA inside our network using http, not https.  In the past we connected to Incoming email servers using IMAP, not Secure_IMAP.   But office365 requires https, and I'm guessing that it's not allowed from an http page.    

Suggest an answer

Log in or Sign up to answer

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you