Replies to messages delivered with Content Encryption fail Bounce Attack Validation
Last Updated June 15, 2016
When using both Content Encryption (CE) and Bounce Attack Validation (BATV), replies to encrypted messages sent from the content encryption web portal are flagged as invalid bounce messages and rejected.
If using the default BATV policy, rejected messages will appear in the maillog as follows:
2011 Nov 18 13:03:22 CST (info) ecelerity:  ML-HOST_CONNECTED: 126.96.36.199:42447 connected. (ID: 90300590)
2011 Nov 18 13:03:23 CST (info) ecelerity:  sieve: ML-CONNECT-INFO: connect from pc01.z118.zixworks.com[188.8.131.52]
2011 Nov 18 13:03:24 CST (info) ecelerity:  [info]: smsbatv.cc-01409: Message information: BATV action is reject at rcpt to time. Message will be rejected now.. source:external, mail_from:MAIL FROM:<>\\x0D\\x0A, rcpt_to:firstname.lastname@example.org
2011 Nov 18 13:03:24 CST (info) ecelerity:  ML-REJECT: Rejection on: 100.111.122.133:25,200, sent to host: 184.108.40.206:42447, Audit ID cead8ee2-b7fe16d0000005ec-03-4ec6abfb0e32, 550 5.7.1 Bounce attack signature verification failed.
2011 Nov 18 13:03:24 CST (info) ecelerity:  [info]: SMS_AUDITLOGGER-01168: Message in progress aborted by SMTP command.
2011 Nov 18 13:03:24 CST (info) ecelerity:  ML-HOST_DISCONNECTED: 220.127.116.11:42447 disconnected. (ID 90300590)
If audit logging is enabled, the rejected messages will also be logged in the Message Audit Logs as having failed Bounce Attack Validation
Replies from the Content Encryption web portal are delivered using the same special envelope sender used for bounce messages ("<>") but are not delivered to the modifed envelope recipient address used to identify valid a valid bounce message. Instead they are delivered to the original unmodified recipient address.
The Bounce Attack Validation feature and replies to Content Encryption messages are incompatible when using legacy Content Encryption vendors.
This issue will not be addressed for legacy Content Encryption vendors and does not affect Bounce Attack Validation when using Symantec Cloud Content Encryption.
Symantec Messaging Gateway using both Bounce Attack Validation and Content Encryption.
Imported Document ID: TECH174807
Subscribing will provide email updates when this Article is updated. Login is required to Subscribe