Any ideas why when you reply to jira@company.atlassian.net we get a bounce back saying
"This message could not be delivered."
from bounce@atlassian.net
Hi @Jonathan Robles and welcome to the community,
This kind of email, most likely is used to send notifications and not to reply to it. I don't think there is a handler behind it. What exactly you want to achieve by replying to this email?
Correct. We migrated to Jira Cloud instance. And we get notification emails from jira@company.atlassian.net with no problems. But when the service desk team replies to a notification, we get the bounce back message.
I am just using company.atlassian.net on this article for privacy purposes.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
A JSM project has a dedicated email when you create (and if you have enable the email requests). Can you please confirm that in your JSM project this is the dedicated email? You may see that by going to project settings > email requests. There you should be able to see a screen like the following one:
This will be your incoming mail handler for all your JSM email request. Do not confuse this email with the email that all Jira users are receiving notifications. Totally different thing. Hope I make myself clear.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Understood. I just want clarification that users need to reply to the email handler in order to update a ticket. Correct?
I will need to change this in the Project Settings > Summary > Notifications > Update the email to the email handler mailbox instead of the default one.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Changing the Notifications email from will only change the sender email from which notifications will be sent. (Jira) users can't reply to these emails as they are used only for notifications.
Instead, if you want your customers and Jira users to reply to an email and to update tickets, then you must see the email I said in my previous comment. This is the handler you are after.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Alex,
Thank you for your update.
But the default email notifications come from jira@company.atlassian.net
The Project Setting email account is to pull emails and create tickets from them. Not to send emails from that address.
I just want to make sure that Jira does not automatically append the REPLY-TO header to that of your project email pull address.
Which is why I uploaded the picture above for confirmation.
This link to another ticket says that the work around is as I describe it;
Please note that if you’re using a custom email handler to process Jira Service Desk tickets, you’ll have to follow this documentation in order to use your domain to send Jira notifications.
Go to your Jira Service Desk Project and click on Project settings.
On the left panel, look for Summary.
Scroll down until you see the Notifications section.
Click on the pencil icon and edit the email address, replacing it with the one by the email handler (find it on the Email requests section)
That should be all. I hope this helps you!
Cheers
Paulo Junior - Atlassian Cloud Support
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Is this still valid as i can't see a pencil icon as shown on the picture above and thus i can't change that address to the collecting email address. i always get a bounce email from bounce@atlassian.net which says "This message could not be delivered." but the commented finally is added to the ticket...
thx for help...
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.