sbl
Blocklist provider and master spam-filterer Spamhaus had a glitch overnight (Friday to Saturday, August 18-19) starting at about 8:20 pm US central time. The glitch resulted in a bunch of false positive Spamhaus blocklistings. They were accidental and the listings have since been removed. Because of the sheer volume of support tickets received, it sounds as though Spamhaus may not be responding to all of them. Best to watch Linkedin, if possible, for updates.Here’s what Spamhaus posted about this:NOTIFICATION | CSS Listing Errors | Today, between 1:20 am UTC & 2:20 am UTC, a significant number of listings were incorrectly added to the CSS DNSBL. These listings were purged at approx. 8:30 am UTC. Our engineers are currently investigating the root cause of the issue. We sincerely apologize for any inconvenience this may have caused.CSS REMOVAL TICKETS | Further to the issue regarding CSS listings this morning, between 01:20 UTC
Timely! I just blogged recently talking about what you should do if you get blocklisted by Spamhaus, and now Spamhaus just posted this: Poor sending practices trigger a tidal wave of informational listings. What does it all mean and should you be concerned? Let me explain.What Spamhaus is referring to is a recent uptick in SBL entries (blocklistings) for ESP/CRM senders — informational listings — that were almost like a big ole bomb dropped out of nowhere. ESPs were waking up to a dozen or more listings for their clients, seemingly out of nowhere, wondering what changed.To make this a little bit easier to handle, these new listings are “informational” in nature. “Informational listings” are something that Spamhaus has done for a while now, where they will warn you of an SBL listing, but not actually configure the listing to cause mail to block. It means the client or company sending