SA Bugzilla – Bug 187
ASCII_FORM_ENTRY strangeness.
Last modified: 2002-04-12 14:10:21 UTC
Submitted for your approval... A spam that should trigger ASCII_FORM_ENTRY, but doesn't, and a non-spam that shouldn't, but does. From my reading of ASCII_FORM_ENTRY, it looks fine, but for some reason, it's not tripping properly on these. Dan.
Created attachment 46 [details] Spam that should trip
Created attachment 47 [details] Non-spam that shouldn't
*** This bug has been marked as a duplicate of 180 ***
Actually, this doesn't seem to be the same as bug 180. I fixed that, and this still happens... Dan.
Can't reproduce this with the two messages you attached. They seem to behave correctly to me. Are you using the CVS rules which include Matt Sergeant's change of March 5th? Check that you have rawbody ASCII_FORM_ENTRY /[^<][A-Za-z][A-Za-z]+.{1,15}?[\x09\x20]*_{30,}/ and not rawbody ASCII_FORM_ENTRY /[^<][A-Za-z][A-Za-z]+.{1,15}?\s+_{30,}/
Confirmed that it works with latest CVS, in both cases, thanks. Dan.