3
Issue with Antispam raw content check.
Problem reported by Steve Norton - 4/23/2019 at 8:28 AM
Submitted
In the latest versions of 16 and 17 the raw content rules check stops after matching the first rule if the rule is not set to ‘match multiple’ and has the same rule type argument (e.g. contains or wildcard) as subsequent rules. When I say “first rule” I’m referring to the order in the spamConfig file, so that is essentially the rule that was modified longest ago as rules are moved below related rules when modified. It appears that the ‘match multiple’ code is running against the rules rather than running against each individual rule.
If customers do not have ‘match multiple’ enabled then a fix for this could have unexpected matches and a very different Spam score.

9 Replies

Reply to Thread
0
Steve Norton Replied
Still an issue in 7068
0
Steve Norton Replied
Still an issue in 7082
0
Steve Norton Replied
Still an issue in 7125, I can provide more detail if anyone would like.
0
Robert Axford Replied
I'm running 16.3.6989 

Is this issue why my raw content filtering rules never seem to work? What a pain.
Rob
0
Steve Norton Replied
You can use the 'match multiple' work around until it's resolved. You can test your rules using a script that contains the text your filtering on, I use PowerShell to test which I'm happy to share if you'd like.
0
Robert Axford Replied
Thanks Steve. I'll give that a shot and see what happens.

0
Steve Norton Replied
Has using the workaround made a difference?
0
Steve Norton Replied
Still an issue in 7242.
0
Robert Axford Replied
Sorry, didn't see the earlier reply. 

I'm now using Raw Content, Regex and rules like this, and it seems to work:
(?i).*webstudio26.*

That's with Match Multiple disabled and version: 16.3.6989 

Reply to Thread