[SpamCop.net - protecting the internet through technology]

[SpamCop-List] Re: Nasty bit of "tracking" not munged by spamcop!

D.Diaz gospamming at yourdomain.invalid
Tue May 11 00:22:19 EDT 2004


"Ellen" <nobody at spamcop.net> wrote in
news:c7ovb0$su3$1 at news.spamcop.net: 

> 
> "David Butler" <ob1db at spamcop.net> wrote in message
> news:c7otn2$rjg$1 at news.spamcop.net...
>> happened to preview the reports on this one (same guys who hide the
>> URL in the title and text to avoid detection, oddly enough...) and
>> saw the 
> Bayesian
>> or tracking garbage at the end was not munged at all!
>>
>>
> <wild><Ob1db><budapest><Ned><stock><deputy><element><pitney><revere><Hi
> nso= 
>> n><skeletal><vorticity
> 
> snipped just in case you are not Ned Hinson who now has his email
> address plastered all over ... the parser picks up the email address
> if it can 'see' it, I think it has to match the 'to' but I could be
> wrong about that, Mike probably can answer that question -- where *is*
> Mike anyway? ... is this what you are referring to? ob1db at broadviewnet
[snip]

I've been receiving a bunch of these last week.  Fortunately, I am 
"ubermunging", as Mike says, so I run everithing through a small Perl 
script to munge and then I do two grep passes, one for checking Base64 
encodings and the other one to check for any instance of our company addy 
which could have been left unmunged.
The Spamcop parser would only munge the complete instances of your addy, 
but not the incomplete ones.  As you can note, there are instances of the 
user part, instances of the domain part and instances of the complete 
addy broken by an quoted-printable end of line terminator.  None of these 
are detected by the Spamcop parser.


-- 
Daniel Diaz
My Personal email: ddiazxn @ telefonica . net


More information about the SpamCop-List mailing list