http://issues.apache.org/SpamAssassin/show_bug.cgi?id=5780
Summary: URI processing turns uuencoded strings into http URI's
which then causes FPs
Product: Spamassassin
Version: SVN Trunk (Latest Devel Version)
Platform: Other
OS/Version: other
Status: NEW
Severity: normal
Priority: P5
Component: Rules
AssignedTo: [email protected]
ReportedBy: [EMAIL PROTECTED]
This is pretty much the same as bug 504, but a specific case has shown up that
was not fixed by bug 504's fix. Since it has been so long, I'm opening this as a
new bug instead of reopening bug 504.
I have a ham email that includes a uuencoded file. Aside from the issue
(discussed in bug 504 comments) that SpamAssassin does not parse uuencodings,
the following line of uuecoding:
MOD_M))%X"M0"-AE/9Y.KN:_0D2F:95^H*:I,8<W6PO;#18AZ-QV9/:K>J..Q
caused the URI code in PerMsgStatus.pm to find the following:
dbg: rules: ran uri rule WEIRD_PORT ======> got hit: "http://9Y.KN:_0D2F:95";
There was some discussion about this in bug 504, but I think that this result
shows that what we have settled on is still too liberal. No reasonable MUA would
turn plain text like "9Y.KN:_0D2F:95" into a hot link, so neither should
SpamAssassin.
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
