'%3e%3cpath%20d='M8%200C12.4183%200%2016%203.58172%2016%208C16%2012.4183%2012.4183%2016%208%2016C3.58172%2016%200%2012.4183%200%208C0%203.58172%203.58172%200%208%200ZM11.6162%204.38379C11.2257%203.99337%2010.5927%203.99338%2010.2021%204.38379L8%206.58594L5.79785%204.38379C5.40732%203.99334%204.77429%203.99329%204.38379%204.38379C3.99331%204.77429%203.99335%205.40733%204.38379%205.79785L6.58594%208L4.38379%2010.2021C3.99348%2010.5927%203.99341%2011.2257%204.38379%2011.6162C4.77426%2012.0066%205.40734%2012.0065%205.79785%2011.6162L8%209.41406L10.2021%2011.6162C10.5927%2012.0066%2011.2257%2012.0067%2011.6162%2011.6162C12.0067%2011.2257%2012.0066%2010.5927%2011.6162%2010.2021L9.41406%208L11.6162%205.79785C12.0066%205.40735%2012.0066%204.77429%2011.6162%204.38379Z'%20fill='%23080E17'%20fill-opacity='0.46'/%3e%3c/g%3e%3cdefs%3e%3cclipPath%20id='clip0_3761_713'%3e%3crect%20width='16'%20height='16'%20fill='white'/%3e%3c/clipPath%3e%3c/defs%3e%3c/svg%3e)
Fix Outlook 554 5.7.1 Relay Access Denied Error for Zendesk
Question details
The user is experiencing a 554 5.7.1 Relay access denied error when attempting to send emails from Outlook.com or a Microsoft 365 account to a Zendesk support address.
- Product
- Outlook, Microsoft 365, Zendesk
- Device & OS
- not provided
- Scenario
- Sending an email from a Microsoft 365 work address to a Zendesk ticketing system.
- Observed behavior
- The outgoing email fails to deliver, generating a Non-Delivery Report (NDR) with the error '554 5.7.1 Relay access denied'. Email headers may indicate that SPF, DKIM, and DMARC configurations are missing or set to 'none'.
Before troubleshooting, ensure you have access to both your Microsoft 365 admin center and your domain's DNS settings. Keep a copy of the complete Non-Delivery Report (NDR) handy for reference.
Verify and Configure Email Authentication Records
Setting up proper SPF, DKIM, and DMARC records helps authenticate your domain and prevents remote servers from denying relay access.
When email headers show SPF, DKIM, and DMARC as 'none', receiving servers like Zendesk may reject the message to prevent spam or spoofing.
Log in to your domain registrar or DNS hosting provider and navigate to the DNS management page for your custom domain.
Ensure you have a valid TXT record for SPF that includes Microsoft 365 (e.g., v=spf1 include:spf.protection.outlook.com -all) and any required Zendesk includes.
Enable DKIM in the Microsoft 365 Defender portal and publish the corresponding CNAME records. Add a DMARC TXT record to specify how unauthenticated emails should be handled by receiving servers.
Resolve Domain Routing Conflicts
If both Microsoft 365 and Zendesk use the same custom domain, incorrect routing settings can trigger the 554 relay error.
Experience a Seamless and Free Office Alternative with WPS Office
While resolving Microsoft Outlook routing issues, consider streamlining your daily document tasks with WPS Office. It provides a lightweight, highly compatible, and completely free alternative to Microsoft Office for your word processing, spreadsheet, and presentation needs.
Frequently Asked Questions
What does the '554 5.7.1 Relay access denied' error mean in Outlook?
This error occurs when the outbound email server does not recognize the sender or the recipient as an authorized user, causing it to refuse to process or 'relay' the email to its final destination.
Why am I getting this relay error specifically when emailing Zendesk?
This commonly happens if Microsoft 365 and Zendesk are configured to use the same custom domain name. The shared domain configuration can cause internal routing confusion, resulting in rejected relay attempts.
How do I find the email headers to check my SPF and DKIM status?
In Outlook, open the returned Non-Delivery Report (NDR) message. Go to File > Properties, and look at the text inside the 'Internet headers' box to review the authentication results.
