Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Next challenges

Recent achievements

  • Global
  • Personal


  • Give kudos
  • Received
  • Given


  • Global

Trophy case

Kudos (beta program)

Kudos logo

You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.

View group

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Error / rejected when we receieve an email from alias.

Hello Jira Service Desk community,

Emails being sent from non company (private) emails are being rejected. We receive the following message: 

Reporting-MTA: dns;
Arrival-Date: Wed, 24 Mar 21 11:29:16 UTC

Diagnostic-Code: smtp; 550 5.6.1 Message content rejected.
Status: 5.6.1

Do you know why this is happening? It wasn't an issue before. 

Hope to hear from you. 

Thanks a lot in advance!



1 answer

0 votes

Hello @Danny Hess,

Welcome to Atlassian Community!

In the past, Jira would reject emails only if they've failed *both* SPF and DKIM checks, but due to a security change we've implemented, this behavior was changed to also reject emails that fail SPF checks only, and this can cause forwarded emails to fail to create tickets.

You can check our Community post regarding this change at the following link:

What do I need to do?

The sender will need to update their SPF settings on their DNS (Domain Name System) SPF record. SPF record settings can be tested using tools like MxToolBox. Alternatively, the sender can change the IP addresses or domain that their emails are sent from.

How it works:

Bob ( sends an email to your email address ( This email passes SPF validation as it was sent from a server of listed in's SPF record.

Then, forwards the email without rewriting the "from" address to your mail handler ( This email does not pass SPF for us as the email from was sent from a email server. "We are looking at this SPF check."

The easiest way to avoid this is to have Jira accessing a mailbox on your domain instead of forwarding email to the default project handler. It can use either POP3 or IMAP to access that mailbox and it should avoid this issue, as Jira is only checking the emails, and is not doing any SPF checks as the emails are on your server, not on Jira's.

If you have any other questions regarding this matter, please let us know.

Kind regards,

Suggest an answer

Log in or Sign up to answer
Community showcase
Published in Jira Service Management

Announcing Mindville Insight is now part of Jira Service Management!

Hello Community! We’re excited to announce that Mindville Insight’s asset and configuration management capabilities will now be integrated into Jira Service Management Premium and Enterprise plan...

686 views 10 15
Read article

Community Events

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

Events near you