Hi, actually, I just discovered the reason SA doesn't properly scan this spam. The spam body is inside a multipart/alternative section, but Content-Type: header in the first part is malformed (has a leading semicolon). Deleting the extraneous semicolon makes SA work as usual.
This does make the spam non-displayable in mutt (and probably many other mailers as well), because the multipart/alternative section won't parse. But I suspect it may work in *some* mailers, so it ought to be fixed. Suggestion to SA upstream developers: maybe have SA fall back to plain text scanning if a multipart/alternative section fails to parse? It seems risky to assume that spam always comes in well-formed multipart sections. (We all know how well spams conform to RFCs.) This would've caught this particular spam. T -- What are you when you run out of Monet? Baroque. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
