4 ms·
A2B was routing CB, CB was not using A2Bs IP space. Spam was not coming from A2B. A2Bs IP space was blocked by Spamhaus to force them to drop CB. What exactly
by ryanlol 11y ago
A2B was routing CB, CB was not using A2Bs IP space. Spam was not coming from A2B. A2Bs IP space was blocked by Spamhaus to force them to drop CB.
What exactly justified blocking A2Bs IP space here?
Spamhaus is a really shady organization with a history of unethical behavior, look up the nic.at fiasco as another example... Or just ask anyone who works in hosting.
- DanBC 11y ago> Per Spamhaus policy, on October 6th, after notifying A2B several times since June without results, an SBL listing which A2B had been ignoring was escalated to the SBL's "providing a spam support service" category and increased to include one of A2B's IP ranges. The escalated SBL record SBL112638 listed 178.249.152.0/21 for providing routing "knowingly and for profit" to a rogue host known as "CB3ROB" or "Cyberbunker", an outfit which Spamhaus has long seen involved in hosting cybercrime and spam outfits. SBL listings of CB3ROB had been mounting steadily during 2011 for hosting malware, phishing and websites selling fraudulent goods advertised via spam. CB3ROB had announced that it would not terminate customers due to spam listings - an announcement which sent a golden invitation to even more spam and crime customers to the point where all of CB3ROB was placed on the Spamhaus DROP ("Don't Route Or Peer") list at the beginning of October. That's exactly what people want from something like the SBL, which is why it's used by so many people. Your reference to nic.at is weird - again they were providing services to a bunch of criminals. When complaining about false positives it'd be really helpful if you could point to people who aren't fucking scumbags who are getting blocked.