Re: [Declude.JunkMail] another new "encoding" trick
The header of the message says that the body encoding is base64, but it was **actually** just plain ascii text. Are you *sure* the body was really just plain text? Note that some ways of viewing the contents of the E-mail (such as a "View Source" option in a mail client) may not show the base64-encoded data, but will actually show the plain text (human readable) version. If the body really was plain text, then it should have triggered the filter. -Scott --- [This E-mail was scanned for viruses by Declude Virus (http://www.declude.com)] --- This E-mail came from the Declude.JunkMail mailing list. To unsubscribe, just send an E-mail to [EMAIL PROTECTED], and type "unsubscribe Declude.JunkMail". The archives can be found at http://www.mail-archive.com.
RE: [Declude.JunkMail] another new "encoding" trick
> The header of the message says that the body encoding is > base64, but it was > **actually** just plain ascii text. Bastards! But if it's possible to send such a message and it's correct visualized on the client side how the client can distinguish between real base64 and faked encoding? What about an official plain-text encoding but base64 content? In your mail it seems like there are missing the 2 lines beginning with "--=_NextPart_"... just before the "Content-Transfer-Encoding=base64" : For example: --=_NextPart_0228031437 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: base64 Markus --- [This E-mail was scanned for viruses by Declude Virus (http://www.declude.com)] --- This E-mail came from the Declude.JunkMail mailing list. To unsubscribe, just send an E-mail to [EMAIL PROTECTED], and type "unsubscribe Declude.JunkMail". The archives can be found at http://www.mail-archive.com.
