I am using JIRA Service Desk in Cloud. I have a set up to create tickets in response to emails. The email service request address is part of my office 365 group and when someone sends email to my Office 365 mailbox, email is also copied to JIRA mailbox and a ticket is created (not yet though.)
The email log rejects all emails with message "The message was rejected because it is auto-reply mail."
If I do not use Office 365 Group and use a distribution list, there is no issue with email processing. It is almost like my emails copy sent from Office 365 group is adding something in message header. I cannot see email headers in JIRA to confirm that.
Anyone has faced this issue? There are couple of solutions I found but none are applicable to Cloud.
Thanks for reaching out to Community!
The emails are rejected due to JIRA mail handlers reading the header of the email and if the line Auto-Submitted: auto-generated is found, the system will automatically reject the email.
You can find more details here:
The Global Processor scheduler job runs every minute and processes all unprocessed mail items saved in the database by the Global Puller. This scheduler job runs independently to the Global Puller. JEPP currently has the following default filters to be reused:
AutoReplyMailFilter - This filter rejects auto-replied emails. If Auto-Submitted header in an email has a value different from "no", that email will be considered as auto-replied emails. Ref: http://www.iana.org/assignments/auto-submitted-keywords/auto-submitted-keywords.xhtml
We have a feature request to set up a "whitelist" to allow certain senders access to bypass this check, which you can check here: JSDCLOUD-1924.
Hope this clarifies!
Hi @Priyendu Bhardwaj ,
Could you tell me more about your workaround ? I can't get it to work.
My last try :
In an Office 365 shared mailbox, I have set up Mail > Forwarding > Enable forwarding my email to my JSD email address. But email still are rejected by SD auto reply filter.
I also tried to add rules to forward the email, or to forward the message as an attachment, but JIRA reject all of this as well.
Thanks for the link @Angélica Luz - that link did help. The route as mentioned on that Closed ticket is to add to the whitelist as per https://support.atlassian.com/jira-service-management-cloud/docs/how-are-domains-added-to-the-permitted-list/
I added the domain I was sending the request as and it worked.
A key problem with forwarding is that the FROM address is used as REPORTER and can end up as the TO address.
e.g. customer (email@example.com) sends to firstname.lastname@example.org this via mail rules ends up as email@example.com
With forwarding, the ticket ends up being FROM: firstname.lastname@example.org with the "email@example.com" information lost.
With redirect, JSM notices something fishy, trips the whitelist, and rejects the email altogether. Whitelisting won't work as customers send from any domain but does not accept wildcards.
@Martin Cleaver Hi Martin
I'm new to JIRA -using it for a month.
We got problems quite similar to your scenario. Does it caused by forwarding?
Customer send email to Servicedesk
|from:||'Customer' via Servicedesk <firstname.lastname@example.org>|
How can we solve it, any suggestions?
This also create another issue.
From above snr. the reporter of JIRA ticket = Servicedesk <email@example.com>
Announcing safe customer notifications in Jira Service Management as a building block for compliance and privacy needs At Atlassian, we understand the increasing need to be assured that your data i...
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