> By chosing the 'B' encoding it is causing every character to be encoded > using BASE64 encoding. Normally if you send mostly ASCII characters you > would choose type Q where the 8-bit characters are converted into =XX > format (eg '=' becomes '=3D', SPACE becomes '=20').
That is known as "Quoted Printable" it is more common because it is friendlier for those luddites ;-) who use ascii terminals to read their mail. >From the POV of spam it would be most sensible to decode headers and content first, >that way you'll match your patterns no matter what encoding is used. I'm a massive fan of Base64 because it lets you safely transfer any payload through every torture known to mail, and would hate for it to become blackballed just because, through lazyness, it allows spammers to obfuscate content. d. > > see here for more info http://www.faqs.org/rfcs/rfc2047 > > Vinny wrote: > > >Sorry if this sounds stupid, but how do you interpret that crazy > string of > >characters? Is that sound king of screwed up MD5 sum or something? > > > > > > > >>=?iso-8859-1?B?>UGF5IFBlbm5pZXMgb24gdGhlIERvbGxhciBmb3IgeW91ciBQ > cmVzY3JpcCh > >> > >> > >0a > > > > > >>W9uIQ==?= > >> > >> > > > > > >-Vinny > > > > > >--------------------------------------------------------------------- > >To unsubscribe, e-mail: [EMAIL PROTECTED] > >For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > > > -- > Jason Lea > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
