Back to Community Threads
SORBS is gone
Idea shared by Eric Tykwinski - 6/5/2024 at 6:05 AM
Proposed
For all using the SORBS RBLs, I got an email yesterday that the Lists are ending rather quickly and being decommissioned.  Hopefully that means just giving out NX responses, but I wouldn't chance it.  Proofpoint the parent company is calling the shots though.

MailOp.org has the orginal posting from Michelle Sullivan.
Tim Uzzanti Replied
6/5/2024 at 7:36 AM
Employee Post
Can you provide the email, don't see anything posted online about it.  
Tim Uzzanti CEO SmarterTools Inc. www.smartertools.com
Tim,

I forgot you need to subscribe to view the archives.

Quote:
________________________________________________________

For those that haven't heard.  Proofpoint is retiring SORBS effective immediately(ish).

 

Zones will be emptied shortly and within a few weeks the SORBS domain will be parked on dedicated "decommissioning" servers.

 

I am being made redundant as part of the shutdown and my last day will be 30th June 2024.  I will be looking for new positions following that.

 

I would like to thank all the SORBS supporters over the years and Proofpoint for keeping it going for the community for the last 13 years.

 

Best regards,

 

Michelle Sullivan

SORBS.

 

--

Michelle Sullivan

http://www.mhix.org/

________________________________________________________

Michelle also posted it to her LinkedIn page: https://au.linkedin.com/in/sorbs
Tim Uzzanti Replied
6/5/2024 at 9:38 AM
Employee Post
Appreciate the heads up on this.  We will start making plans to remove from SmarterMail.
Tim Uzzanti CEO SmarterTools Inc. www.smartertools.com
I am not sure that firing Michelle Sullivan implies closing SORBS, strange that there is no reference on Google, because this news is very important for the antispam sector.
Tim Uzzanti Replied
6/5/2024 at 12:13 PM
Employee Post
"Plans", doesn't mean we are doing it now!
Tim Uzzanti CEO SmarterTools Inc. www.smartertools.com
Seriously, if you suspect the list is down, I would just run a dig +trace.
It should respond back on most of the lists:
2.0.0.127.dnsbl.sorbs.net. 3600 IN      A       127.0.0.10
2.0.0.127.dnsbl.sorbs.net. 3600 IN      A       127.0.0.5
2.0.0.127.dnsbl.sorbs.net. 3600 IN      A       127.0.0.7
2.0.0.127.dnsbl.sorbs.net. 3600 IN      A       127.0.0.2
2.0.0.127.dnsbl.sorbs.net. 3600 IN      A       127.0.0.3
2.0.0.127.dnsbl.sorbs.net. 3600 IN      A       127.0.0.15
2.0.0.127.dnsbl.sorbs.net. 3600 IN      A       127.0.0.9
2.0.0.127.dnsbl.sorbs.net. 3600 IN      A       127.0.0.14
2.0.0.127.dnsbl.sorbs.net. 3600 IN      A       127.0.0.4
2.0.0.127.dnsbl.sorbs.net. 3600 IN      A       127.0.0.6
2.0.0.127.dnsbl.sorbs.net. 3600 IN      A       127.0.0.8
The Register (https://www.theregister.com/2024/06/07/sorbs_closed/) seems to have got an official response from proofpoint regards the shutdown:

"The decision to sunset a product is never an easy one and was made after thorough consideration of various factors impacting the service's sustainability. We can confirm that SORBS was decommissioned on June 5, 2024, and the service no longer contains reputation data. Given the wide range of potential replacement solutions in the market, Proofpoint cannot make recommendations nor endorse any specific replacement product; this is dependent on an organization's needs."

Additionally one of our ips that was listed for years got delisted yesterday what seems to confirm that they did remove the reputation data. 
This is a good example of where having a status page or report for RBLs would be beneficial. You could see which RBLs are still working and effective.
Back to Community Threads

Reply to Thread

Enter the verification text
Related Knowledge Base Articles
Deploying Rspamd For Use With SmarterMailSmarterMail > Server Configuration and Management
554 Error - MTA Poor Reputation FixesSmarterMail > Troubleshooting
Remote Server returned: '602' errorSmarterMail > Troubleshooting
Recommended SPAM SettingsSmarterMail > Antispam and Antivirus
Cannot Send Email MessagesSmarterMail > Troubleshooting