JIRA 7 has landed! Are you an existing JIRA user with questions about upgrading? Visit the Migration Hub for information about upgrading to new JIRA applications

Skip to end of metadata
Go to start of metadata

This Knowledge Base article was written specifically for the Atlassian Server platform. Due to the Restricted functions in Atlassian Cloud apps, the contents of this article cannot be applied to Atlassian Cloud applications.


Outlook cannot handle outbound mail. One or more of the following appears in the atlassian-jira.log:

(info) There is a known bug tracked in  JRA-31238 - Exchange with authentication requires From address matches the authenticated user Resolved  which has been verified to affect instances where the project level From address is configured to be different from the global SMTP From address in JIRA applications.


Your Exchange mail server is not configured to relay messages. 


Exchange 2003:

Open the Exchange System Manager

  1. Go in Administrative Groups -> Administrative group name -> Server -> Server name -> Protocols -> SMTP
  2. Right click on Default SMTP Virtual Server -> properties
  3. Access tab -> Relay button
  4. Select "only the list below" and add the domain and\or IPs of your server

Exchange 2007:

For Exchange 2007, create a second receive connector for external addresses as described in How to Set Up SMTP Relay in Exchange 2007.

(info) Check Microsoft's Exchange Archive as well.

Office 365:

Take a look at Microsoft's documentation on how to set up permissions for relaying messages in Exchange.

Help us improve!

Is this article helpful?
Is it well written?
Is the content complete?


  1. Hi


    Spoke with my IT group and they informed me I have to change the SMTP port number for outgoing mail if I wish external emails. Changed the number and it worked. So I can now have external access and allow only ceratin projets to be viewed.


    Thanks for your help.


  2. The solution proposed here does not make any sense and is a big security issue. It's perfectly normal and recommended not to allow senders to impersonate emails from outside your domain.

    It seems that Atlassian Support Tools is trying to send email as coming from an address that is clearly not one inside the domains and that's why our SMTP server are rejecting it. I am wondering when this will be fixed accordingly.