In 4.1.2, we were able to use aliases in exchange to differentiate incoming mail by setting up services where the catch email looked like this:
Now, in 5.x we can no longer create incoming mail servers using alias of this type. Is there a way around this issue?
Well as our company is moving away from exchange and into Gmail, I have found that the catchemail setting works as expected with it. So we now have one listener pointed at one email box in Gmail, but it have MANY aliases and the catchemail works as expected to pull the correct emails to the appropriate projects.
In JIRA 5.x it will not allow the catchmail address above to be saved in either format:
#39;email@example.com' or "firstname.lastname@example.org"
However, it will save without the quotes but it fails to collect the correct emails from the Exchange server because the To: address is actually "email@example.com" (the alias).
In the end, we ended up splitting out all the aliases into their own separate email addresses, i.e. we took the alias "firstname.lastname@example.org" for the account Jira@exchange.my and made an actual account email@example.com on exchange. Then we set up servers for each account.
This is less efficient than in JIRA 4.2 where I was able to have one server for the single exchange account and then change the catch email for each Mail handler to an alias and use the one server to pull out the different emails into different projects.
In the past, Portfolio for Jira required a high degree of detail–foresight that was unrealistic for many businesses to have–in order to produce a reliable long-term roadmap. We're tur...
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