Bug 187 - ASCII_FORM_ENTRY strangeness.
Summary: ASCII_FORM_ENTRY strangeness.
Status: RESOLVED WORKSFORME
Alias: None
Product: Spamassassin
Classification: Unclassified
Component: Rules (show other bugs)
Version: 2.11
Hardware: Other other
: P2 normal
Target Milestone: ---
Assignee: SpamAssassin Developer Mailing List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2002-04-04 15:27 UTC by Daniel Rogers
Modified: 2002-04-12 14:10 UTC (History)
0 users



Attachment Type Modified Status Actions Submitter/CLA Status
Spam that should trip text/plain None Daniel Rogers [NoCLA]
Non-spam that shouldn't text/plain None Daniel Rogers [NoCLA]

Note You need to log in before you can comment on or make changes to this bug.
Description Daniel Rogers 2002-04-04 15:27:30 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.
Comment 1 Daniel Rogers 2002-04-04 15:28:05 UTC
Created attachment 46 [details]
Spam that should trip
Comment 2 Daniel Rogers 2002-04-04 15:28:54 UTC
Created attachment 47 [details]
Non-spam that shouldn't
Comment 3 Daniel Rogers 2002-04-05 09:52:24 UTC

*** This bug has been marked as a duplicate of 180 ***
Comment 4 Daniel Rogers 2002-04-05 12:14:36 UTC
Actually, this doesn't seem to be the same as bug 180.  I fixed that, and this
still happens...

Dan.
Comment 5 Craig Hughes 2002-04-11 18:30:29 UTC
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,}/
Comment 6 Daniel Rogers 2002-04-12 22:10:21 UTC
Confirmed that it works with latest CVS, in both cases, thanks.

Dan.