Bug 1564 - uuencoded content causes false positive
Summary: uuencoded content causes false positive
Status: RESOLVED WORKSFORME
Alias: None
Product: Spamassassin
Classification: Unclassified
Component: Libraries (show other bugs)
Version: SVN Trunk (Latest Devel Version)
Hardware: Other other
: P5 normal
Target Milestone: 2.70
Assignee: SpamAssassin Developer Mailing List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-02-26 05:47 UTC by Andrew A. Vasilyev
Modified: 2004-01-25 11:32 UTC (History)
0 users


Attachment Type Modified Status Actions Submitter/CLA Status
Could be a problem with DOS CRLFs, original text is 100% UNIX. text/plain None Andrew A. Vasilyev [NoCLA]
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Andrew A. Vasilyev 2003-02-26 05:47:14 UTC 
A message with uuencoded text included got a false spam hit.


See the attachment.
Comment 1 Andrew A. Vasilyev 2003-02-26 05:48:25 UTC 
Created attachment 687 [details]
Could be a problem with DOS CRLFs, original text is 100% UNIX.
Comment 2 Theo Van Dinter 2003-05-25 17:49:21 UTC 
not sure what to do about this.  arguably the content-type ought to specify it's
a uuencoded file, and then we could ignore it/decode it as appropriate.

but for right now, 2.70.
Comment 3 Graham Murray 2003-05-26 01:23:32 UTC 
>arguably the content-type ought to specify it's
>a uuencoded file

Don't forget that uuencode predates MIME by a long time. So uuencoding and MIME
are alternative ways of sending binary data by mail, hence mails with uuencoded
content often have no MIME headers.
Comment 4 Theo Van Dinter 2004-01-25 20:32:54 UTC 
I don't think there's much we can do about this, but 2.70 hits very little on this message.