I don't doubt what you posted below at all. We've all seen this before. Its the signal/noise we have to understand.
IMHO: when your noise levels are this high, and you just ask for reports by those abused, and up to 48 hour windows for takedowns..... you aren't solving the problem at all. (Horse/barn door) Spammers have even hailed publicly how they love Namecheap's speed of new domains to live. How they can quickly role new domains. These are just my opinions. You guys run your network how you want. I've lost patience with all these smoke and mirrors over the years. --Chris (I top post because I care.) > -----Original Message----- > From: Ben Johnson [mailto:b...@indietorrent.org] > Sent: 2013-05-07 15:58 > To: users@spamassassin.apache.org > Subject: Re: dns*.registrar-servers.com as a rogue registrar? > > > I'll top-post, too, just for the sake of consistency. :) > > I've had pretty good experiences with Namecheap, actually. > I'm in no way > affiliated; I've just used them for cheap domain registrations > (apparently, I'm not the only one) and for cheap SSL > certificates in bulk. > > But, that's neither here nor there. As the company relates to this > conversation, I reported a domain that was spamming heavily and > registered with Namecheap and the company took swift action: > > > Hello, > > > > Thank you for your email. > > > > While jecon.us domain name is registered with Namecheap it > is hosted with another company. So we cannot check the logs > for a domain and confirm if it is involved in sending > unsolicited bulk emails. > > > > However, as we can see the domain name is blacklisted by > trusted organizations. Thus we opened a case regarding the > domain name. Please allow about 48 hours for our further > investigation. > > > > Thank you for letting us know about the issue. > > Five days later, the domain was shut-down: > > > Hello, > > > > This is to inform you that jecon.us domain was suspended. > It is now pointed to non-resolving nameservers and will be > nullrouted once the propagation is over. The domain is locked > for modifications in our system. > > > > Thank you for letting us know about the issue. > > So, if you are having problems with domains registered with > Namecheap, I > suggest that you open a support request for the "Domains -- Legal and > Abuse" department. From the sounds of it, you'd be doing us > all a big favor! > > -Ben > > > > On 5/7/2013 3:26 PM, Chris Santerre wrote: > > The owner is NameCheap, Inc. > > > > A quick google will bring up historical problems with > NameCheap and its > > owner and its DBAs. > > > > I dare not say anything bad about them and let you judge > for yourself on > > their history. Richard Kirkendall has a tendency to yell > "Slander!" when > > someone even mentions their name. > > > > > > --Chris > > (I top post because I care.) > > > > > >> -----Original Message----- > >> From: lcon...@go2france.com [mailto:lcon...@go2france.com] > >> Sent: 2013-05-07 14:15 > >> To: users@spamassassin.apache.org > >> Subject: dns*.registrar-servers.com as a rogue registrar? > >> > >> > >> > >> Nearly all of the .pw domains have their authoritative NS at > >> dns*.registrar-servers.com. > >> > >> that registrar and few others are always at the top of my > reports for > >> NSs of sender domains of spam we reject. > >> > >> Does anybody score a msg if its sender domain is DNS hosted by > >> registrar-servers.com or other? > >> > >> what would that rule look like? > >> > >> Len > >> > >> > > >
