ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.

Out of Office notification failing DMARC authentication

book

Article ID: 172242

calendar_today

Updated On:

Products

Email Security.cloud

Issue/Introduction

Out of Office notification may fail DMARC authentication when you have sent it through the Symantec Email Security.cloud service; DKIM signature is not in the mail header. The mails may be delivered to the recipient's Junk folder when action in DMARC record set as q=none, or q=quarantine but recipients do not have quarantine environment.

 

Cause

Out of Office notification is commonly sent from a null sender as the Env Sender (RFC5321.MailFrom) and the users mail address as a Body sender (RFC5322.From). When Symantec delivers mails to recipients, HELO/EHLO identity is Symantecs host name, which is used as the Env Sender in SPF/DMARC authentication instead of a null sender.

 

Example:

Env Sender (RFC5321.MailFrom)

<> 

Body sender (RFC5322.From)

[email protected]

HELO/EHLO identity

mailx.bemtann.messagelabs.com

 

The reason for DMARC failure is SPF alignment check; The Env Sender (null) and the Body Sender (yourdomain.com) do not match.  The DKIM signature, which is an alternative way to verify the authenticity of the message, is not in the mail header.

 

Resolution

Enabling DKIM signing in Email Security.cloud service can solve this issue.

Services > Email Services > Outbound DKIM Signing Settings

 

For more details about how to enable the feature on your account, please kindly refer the following link.

https://support.symantec.com/en_US/article.TECH249633.html

 

 

If you are experiencing an error with 553-you are trying use me as a relay when sending Out of Office notification from Hosted Mail Services (e.g.  Office365, G-Suite), please kindly refer the following link.

https://support.symantec.com/en_US/article.TECH228546.html