Oddly, the documentation covers this:
You'll need to decide what to do with incoming mail as well - start at https://confluence.atlassian.com/display/JIRA/Creating+Issues+and+Comments+from+Email
I'd really like to get this to work with Exchange using MAPI. We can't enable POP or IMAP on our exchange server, because we don't administer it and are legally bound to our email provider by state law. We do exchange integration quite regularly and polling exchange for emails is straight-forward (even if it is proprietary). Do you know if it would it be possible for us to build a plugin to enable Exchange as a confluence inbox?
Also, you can't phone up a supplier and ask them to write a batch of code to avoid you needing to make that call to IT. Well, you can, but the best case is that they'd pass on the coding and licencing costs to you.
You might find it easier to run a different mail server, one that supports standard protocols and have your Exchange admins set up forwarding to that instead.
Has Atlassian been able to scrounge some change to license the MAPI protocol code?
The news alludes to their huge success; I bet enough to cover something like this for the benefit of their State sector.
We are also not able to have POP or IMAP enabled on the Exchange server.
That was a bit of a flippant answer on my part, I hope you didn't find it too annoying!
I think it's worth expanding on though. The initial thought was born of my brain going "if it costs you $50k to enable a standard, well understood, globally used function that takes 2 minutes to enable, then your mail server is probably wasting vast amounts of time and money in many other ways, and moving to another one would save you a fortune". Exchange really does fit that pattern - I've only seen one mail server with a worse ROI, and worked in several enterprises moving off Exchange to save themselves a fortune.
Then there was a second thought, which was what I've seen (and done myself) in places crippled with poor corporate email services. We set up a new service on the Jira box itself, with a simple open-source mail server that provides IMAPS mailboxes for only the Jira incoming mail, firewall it so that only your Exchange servers can talk to it, and get them to forward incoming mail to the mail on that local machine. Tell Jira to use localhost as the email server, and it'll work fine, although you may want to do a little work on stripping any "forwarded" headers the exchange servers stick on it.
Hey Atlassian community, I am a PM on the Bitbucket Cloud team and I am excited to share that we just released an improvement to the Jira Software and Bitbucket Cloud integration. With the newly im...
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!
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