[NBLUG/talk] code: PGh0bWw+PGhlYWQ+PC9oZWFkPjxmb250IGNvbG9yPSJ3aGl0ZSI+DQo0M1BS

[Micxz Love (lovedialup.com)]

Thanks guys! That perl command worked great, I don't seem to have 
munpack on my system anywhere.

Do these messages display correctly under windows or certain 
applications or is it just "dumb"?

I promise not to post encoded spam to the list anymore!!! LOL!!

Micxz

 > ME wrote:
> Micxz Love (lovedialup.com) said:
> 
>>I was looking at an email that in the body looked like so:
> 
> [chopped binhex encoded SPAM]
> 
>>"Why would someone do that?" (sic)
> 
> 
> Using my very weak Perl Fu, I was able to copy out the Binhex encoded
> stuff and put it into a file (decodeme.txt), and then issue this:
> 
> $ perl -MMIME::Base64 -0777 -ne 'print decode_base64($_)' < decodeme.txt
> 
> What I saw was *SPAM!* (Something about a web cam and asking if you want
> to see someone in a web cam. You want the text, I can get it to you, or
> ytou can "do it yourself" and read the spam in all of it's glory.
> 
> Why would someone do this? To try to get the SPAM passed the SPAM filters.
> Many can't decode base64 to scan for spam. Also, if the spam is of
> sufficient size, the bas64 encoding can make the size of the message big
> enough to not be scanned due to size limits. (Yeah, I know, it is dumb.)
> 
> Anyway...
> 
> (No more spam to the list! ;-)  (heh heh)
> (In case it is not obvious, the above line is a joke. You did not know
> what you were sending, and I was trying to be funny. ;-)
> 
> -ME
> 
> _______________________________________________
> talk mailing list
> talk at nblug.org
> http://nblug.org/mailman/listinfo/talk