Header name field inside a compliance policy on a Symantec Messaging Gateway is not RFC2822 compliant and may throw an error 587: Cannot parse
Last Updated March 27, 2012
The "header name" field inside a compliance policy on a Control Center appliance of a Symantec Messaging Gateway (SMG) is not RFC2822 compliant, and when SMG encounters a header name it cannot understand, it can throw an error in a log file and a compliance policy associated with that header name may not fire.
Inside the "bmserver_log" log file, this error is displayed:
Header fields are lines composed of a field name, followed by a colon (":"), followed by a field body, and terminated by CRLF. A field name MUST be composed of printable US-ASCII characters (i.e., characters that have values between 33 and 126, inclusive), except colon. So, because the ASCII value for "1" is "49", it should be allowed in the "header name" field.
Note: the : is not allowed by RFC in the "header name" field, but in tests with the setup mentioned above, the illegal header names such as "X-Spam:Ed", "X-SpamEd:" and "X-Spam:" were acceptable via the GUI and there were no errors in bmserver_log file.
Imported Document ID: TECH184983
Subscribing will provide email updates when this Article is updated. Login is required to Subscribe