http://bugzilla.spamassassin.org/show_bug.cgi?id=3278
------- Additional Comments From [EMAIL PROTECTED] 2004-04-17 15:18 ------- Subject: Re: SA doesn't ignore UUEncoded attachments in message body On Sat, Apr 17, 2004 at 02:24:02PM -0700, [EMAIL PROTECTED] wrote: > UUEncoding is easily recognizable as such. Virtually all MTAs in existance > are > capable of recognizing it and showing it as an attachment. Well, MTAs won't, MUAs might. But most don't. > I'm sure you will claim that if you strip UUE that a spammer could use it to > hide a message. This is so. It is also true that a spammer can hide a > message > in a base-64 encoded gif file, and yet you strip those out rather than > applying > the body rules to the base-64 encoded gif image. Well, we don't scan graphics at all, so there's nothing lost there. There are tons of spam graphics that we don't scan. I'm more worried about spammers hiding in the text uuencode than I am in the binary graphic -- they have to make the graphic viewed somehow, which we catch since it's text/html... > If you don't want to either strip out or decode UUE parts of a message, then > you should apply the same rules to other binary attachments, and run the body > rules on them too without decoding. Otherwise you are being inconsistant and > saying that body rules should be applied to some encoded non-text message > parts > but not others, even though a typical MTA would not handle the message that > way > for presentation. No... uuencode is non-encoded text (as far as the message is concerned). base64 is encoded binary (in the case of a graphic anyway). mime attachments can specify type, uuencoded inserts can not. we don't ignore base64 encoded text parts, how would we do that with uuencoded sections? do we add in an attachment node for uuencode stuff? if so, what type of attachment is it? do we have to decode it first, then attempt to figure out what kind of file is enclosed? To reverse your argument: those MUAs which may see uuencoded as an attachment can't send as uuencoded, they'll send as MIME attachments. uuencoded files are deprecated by MIME at this point. ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.
