nanog mailing list archives

Re: Re: Request Spamhaus contact


From: Jeffrey Lyon <jeffrey.lyon () blacklotus net>
Date: Mon, 17 Jan 2011 19:33:42 -0500

Raymond,

We've acted on every report that we're aware of and instead you want
to play pharmacy domain scavenger hunt. This domain at 208.64.120.197
redirects to IP space we already null routed. It's the same customer.

Just to calm your nerves we'll also null route that space (208.64.120.176/28)

Thanks, Jeff

P.S. Someone at Spamhaus PLEASE remove the /21 listing?



On Mon, Jan 17, 2011 at 7:25 PM, Raymond Dijkxhoorn
<raymond () prolocation net> wrote:
Hi!

Spam does not make me nervous, it's a practical matter that we will
address in due course. The null routes we have set are pretty recent
so you may have received some spam prior to that time but I absolutely
guarantee you that it did not come from our network, otherwise we
would have detected it and stopped it on the spot.

Thats not your IP space? Really? How come.

apothekeosterreich .at -> 208.64.120.197
vertrouwdeapotheek .nl -> 208.64.120.197

viagra-shopping .com -> 208.64.127.78
medicin-24 .com -> 208.64.127.78

apothekeohnerezept .at -> 208.64.127.66

www.medicin-24 .com -> 208.64.127.78
www.viagra-shopping .com -> 208.64.127.78

This is just like 3 minutes digging in todays spamfolders.

www.apothekeosterreich .at is still up at the mentioned ip. Instead of
telling you are soooo good on terminating stuff. Can you walk over the list
and act?

I have sended in many requests for termination. You or your network dont
respond to this at all.

Its a waste of time even telling it seems.

I will stop posting here, spam-l is a much better place for this. But please
dont act like you dont know anything whats going on. You have been warned.
You have gotten many many reports. But we dont see stuff changing.

Good luck with your listing at SpamHaus.

Bye,
Raymond.




-- 
Jeffrey Lyon, Leadership Team
jeffrey.lyon () blacklotus net | http://www.blacklotus.net
Black Lotus Communications - AS32421
First and Leading in DDoS Protection Solutions


Current thread: