@Chris Low: You can easily identify the expression causing the false positives by changing the comment text to something non-unicode (e.g., simple numbers). By the way we will address this in future versions.
As for the whitelisting, you can try the following:
1. Start the Administration Tool
2. Navigate to Configuration / Filtering - On Arrival / Keyword Whitelist
3. Click New
4. On the Filter properties tab, set the scope to "Email header (raw MIME)", add some comment
5. On the filter expression tab, insert the following expression:
.*^In-Reply-To:\s*<?[A-F0-9]*@mydomain\.com\.sg>?\s*$
and set the expression typoe to "Regular expression".
6. Click OK, press Ctrl + S to apply the changes.
As for the whitelisting, you can try the following:
1. Start the Administration Tool
2. Navigate to Configuration / Filtering - On Arrival / Keyword Whitelist
3. Click New
4. On the Filter properties tab, set the scope to "Email header (raw MIME)", add some comment
5. On the filter expression tab, insert the following expression:
.*^In-Reply-To:\s*<?[A-F0-9]*@mydomain\.com\.sg>?\s*$
and set the expression typoe to "Regular expression".
6. Click OK, press Ctrl + S to apply the changes.
Krisztian Fekete (Vamsoft)
(September 8, 2011)
in response to this post
in response to this post
how can I whitelist this header
In-Reply-To: <
On a single line.
starts with "In-Reply-To"
ends with "@mydomain.com.sg>"
with [A-F0-9] in between.
having a hard time with this