How to configure Exchange Online account to JIRA OnDemand Service Desk 2.0?

JIRA (OnDemand) Service Desk 2.0 has setting to allow customers to contact service desk via email. Customers can create a request by sending an email, and respond to comments from agents via email as well.

However, when adding my exchange online email account with following settings

email protocol: SECURE IMAP
mail server:
port number: 993

i get following notification:

BYE JavaMail Exception: Read timed out

Is exchange online supported, and if not, when can we expect this feature to be updated to JIRA OnDemand?

2 answers

Hi Timo Pitkäranta,

What did you use to setup the email channel to office365? I tried to create the same thing using trial account of office365 and it works as expected. Please find in the screenshot information of the setting that I used.


Screen Shot 2014-09-13 at 7.08.12 PM.png

Hi Duc,

Thanks for the reply.

We set up a test account, and used it to login to
Office365 asked to change the password on initial login, so we changed it.
I tried to access to Outlook Web App in Office365, and it worked ok.

Now when we tried to configure this same account to JIRA Service Desk email settings
the same way you did, we still got the same read timeout error message. The only
difference to your settings is that we have our company's domain-name in the email address

Does this email have to exist in JIRA as a user account as well?
This is not public service desk, but that shouldn't matter?

Hi timo pitkäranta, There's no precondition with setting up the email channel. That said, you setup things properly already. The actual problem is, somehow takes longer time than expected to process our request. As it's out of our expected time window, the exception was raised. We are working on increasing the duration of the time window in order to increase the compatibility with email services.

Thanks Duc, I appreciate it

Thanks Duc. As users of Office 365 for Education and using ADFS for clients to authenticate against our internal active directory I can confirm that we are experiencing the same issue as Timo and look forward to seeing a resolution.

Thanks timo pitkäranta] and [~andrewe, we addressed the problem and will ship the fix with the upcoming Ondemand release. Please be updated via this issue

Thanks for this Duc

Hi Duc, are you able to tell us when this fix will be released? Thank you.

Hi @Jaime Vogel, the fix was implemented. It should be landed on OD in the next few weeks

Hi, We self-host and are experiencing the same issue. Can we fix this ourselves?

@Duc Anh Dao I am seeing the same thing on the stand alone version and we are running 6.4.8. Was the timeout fix incorporated to that as well? Any other thoughts on how we can deal with the socket timeout issue? Thanks

Suggest an answer

Log in or Sign up to answer
Community showcase
Asked Dec 06, 2018 in Jira Service Desk

Looking for teams who switched from email to Jira Service Desk

The Jira Service Desk marketing team is working on a guide to help new Atlassian customers switch from email to JSD and we'd love to hear from you! Please share: - What made you realize that i...

1,185 views 10 13
View question

Atlassian User Groups

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

Find a group

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

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you