Some content filtering policies fail to match long, non-ascii message headers
Last Updated May 30, 2013
Content filtering rules that do regular expression matching against message headers sometimes fail to match long headers that are encoded non-ascii data which are wrapped across multiple lines.
When performing the regular expression match, the header content is supposed to be unwrapped and any end of line characters replaced with a space. SMG, however, includes the extra space in a decoded UTF-8 string against which the regular expression is tested. Encoded headers that are split between multiple lines are not detected unless the Content Filtering policy regular expression has embedded whitespace that matches the line break.
This issue has been addressed with the SMG v10.0.2 release.
Intermediate strings consisting only of whitespace will be skipped when doing content filtering regular expression matching.
Imported Document ID: TECH205755
Subscribing will provide email updates when this Article is updated. Login is required to Subscribe