We currently have an incoming email handler that is working just fine. However, we recently updated the Catch Email Address in this handler to a new address we just introduced into our Exchange environment, and the handler no longer works. We revert back to the older Catch address, and all is fine.
We've also tried introducing several new incoming handers with new catch addresses over the past week and none are working, while older handlers are processing just fine.
Like the working catch address, the new address is a distribution list; both of which point to the Default Cloud Mail Server and address - email@example.com. So JIRA should be getting the email, just not sure why it's dropping the message on the floor.
Any insights appreciated.
diagnosis options for incoming mail handlers (in opposite to the Service Management mail channels) are rarely present in Jira Cloud - however, the first step I'd suggest is to review the logs in the Exchange environment.
If nothing suspicious shows there it makes probably most sense to raise a request with Atlassian support - best to be done by a site administrator of your Cloud instance.
This is a more individual concern, tailored to your mail setup. I'd be happy if somebody else replies here but I suspect this to need more in-depth looking at all the involved machine's configuration (especially Exchange, then Jira Cloud).
We are excited to announce the open beta program for self-hosted runners. Bitbucket Pipelines Runners is available to everyone. Please try it and let us know your feedback. If you have any issue...
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