The Spam and Open Relay Blocking System (SORBS) was once a notable anti-spam blocklist (or blacklist), specifically designed to identify and list mail servers known for acting as open relays or being otherwise abused by spammers. Its importance for email deliverability has fluctuated over time, with many mail providers and Internet Service Providers (ISPs) adopting a more nuanced approach to blocklist data. Crucially, as of June 2024, SORBS has ceased operations, rendering its direct impact on current deliverability null. However, understanding its historical role offers insight into how various blocklists contribute to sender reputation and filtering mechanisms.
Key findings
Past relevance: While hosting companies sometimes downplayed its importance, SORBS was historically used by some business-to-business (B2B) systems for email filtering.
Limited B2C impact: Major Business-to-Consumer (B2C) email providers like Gmail, Hotmail, and Yahoo typically did not show significant deliverability changes due to SORBS listings, although they might have used it as one of many data inputs.
Operational focus: SORBS primarily listed IP addresses and domains associated with open relays or those that generated spam trap hits, indicating compromised or misconfigured mail servers.
Proofpoint connection: SORBS operated as a non-profit division of Proofpoint, sharing some spam trap feeds, though Proofpoint's main reputation service used different, often more stringent, listing criteria.
Current status: As of June 2024, SORBS has shut down, meaning it is no longer an active blocklist impacting email deliverability.
Key considerations
No current impact: Since its shutdown, a SORBS listing no longer directly impacts your email deliverability or sender reputation. Any tools showing a current SORBS listing are outdated.
Underlying issues: If you faced a SORBS listing in the past, the underlying cause, such as an open relay or spam trap hits, indicates deeper email hygiene issues that still need addressing. These issues can lead to listings on other active blocklists.
Proactive hygiene: Maintaining good sender practices, including proper email authentication (SPF, DKIM, DMARC) and list hygiene, is key to avoiding current blocklists and ensuring healthy domain reputation.
Email marketers and professionals (not necessarily deliverability experts) often found themselves concerned when their IP addresses or domains appeared on the SORBS blocklist, particularly in shared hosting environments. Their perspectives frequently highlighted the immediate anxiety caused by such listings, even if the actual impact on their specific email campaigns was sometimes unclear or minimal. The perceived importance often stemmed from seeing the listing itself rather than direct evidence of widespread delivery failures.
Key opinions
Initial concern: Marketers frequently experienced anxiety and confusion when their IP or domain appeared on SORBS, especially if they were not dedicated email marketers but rather ordinary businesses.
Hosting company reassurances: Many marketers received assurances from their hosting providers that SORBS was not widely used by ISPs for filtering, though this often contradicted their own perception of the blacklist's importance.
Shared IP challenges: A common scenario involved shared IP addresses on hosting platforms, where a SORBS listing for one user could impact others on the same IP.
Desire for correctness: Despite potentially low direct impact, businesses often wished to ensure their email infrastructure was properly configured and off all blocklists, including SORBS.
Key considerations
Understand bounce messages: If you experienced issues related to SORBS in the past, checking bounce messages was a key way to determine its actual impact on specific recipients, as only directly rejected emails indicate a problem.
Focus on major blocklists: Now that SORBS is defunct, prioritize monitoring and maintaining a clean status on the most impactful blocklists that directly affect the majority of recipient mailboxes, such as Spamhaus.
Shared IP management: If using shared IP infrastructure, regular communication with your hosting provider about IP reputation and proactive measures remains important, irrespective of SORBS.
Email authentication: Ensure your sending domains have proper SPF, DKIM, and DMARC records configured, as these are far more critical for modern email deliverability than legacy blocklist concerns.
Deliverability impact: While a minor blocklist might not severely impact deliverability, a listing on any blocklist for legitimate senders means an underlying problem. Always investigate and resolve these issues to protect your sender reputation.
Marketer view
Marketer from Email Geeks expressed concern after their hosting company described SORBS as a "mostly unused blocklist provider" despite its appearance on tools like MX Toolbox, questioning the accuracy of this assessment.
17 Nov 2018 - Email Geeks
Marketer view
Marketer from Email Geeks noted that their client, a plumbing firm, sent ordinary business emails to diverse addresses, not for email marketing, making a SORBS listing on their shared IP particularly concerning for them.
17 Nov 2018 - Email Geeks
What the experts say
Email deliverability experts held a more nuanced view of SORBS, often distinguishing its impact based on recipient type (B2B vs. B2C) and its relationship with larger email security vendors like Proofpoint. While acknowledging its historical use by some systems, experts generally regarded its influence as less pervasive than major blocklists like Spamhaus. They also emphasized that delisting was typically straightforward, especially for those familiar with the process.
Key opinions
Variable impact: Experts noted that SORBS's impact varied, causing only a few percentage points' rise in bounces for business-to-business (B2B) clients but almost no change for major Business-to-Consumer (B2C) providers like Gmail, Hotmail, or Yahoo.
Input, not primary filter: While large providers like Google might have consumed SORBS data, it was typically just one of many inputs into their complex filtering systems, not a primary blocking factor.
Ownership and criteria: SORBS was a non-profit division of Proofpoint, sharing some spam trap feeds. However, Proofpoint's own appliances used a separate reputation service with different, more robust, listing criteria.
Causes of listing: Experts primarily dealt with SORBS listings due to spam trap hits, rather than solely open relays, requiring submission of tickets and analysis of redacted headers for resolution.
Key considerations
Delisting feasibility: Despite a listing's perceived importance, delisting from SORBS was generally considered a low-effort process, often achievable even for shared IP addresses, by engaging with the SORBS team directly.
Prioritize major blocklists: Deliverability experts consistently point to Spamhaus and URIBL as the most significant blocklists to avoid, as they carry far more weight with major ISPs.
Focus on root causes: Any historical SORBS listing, whether due to open relays or spam traps, signifies a need to address underlying mail server configurations and list hygiene to prevent future deliverability issues on other active blocklists. Tools like DNSBL checks can help identify these.
Continuous monitoring: Regularly monitoring your IP and domain reputation on active, influential blocklists is far more beneficial than dwelling on historical (or defunct) ones like SORBS. Spamresource.com offers excellent resources on this.
Expert view
Expert from Email Geeks mentioned that some business systems historically relied on SORBS for email filtering, suggesting its relevance was contingent on the specific recipient base.
17 Nov 2018 - Email Geeks
Expert view
Expert from Email Geeks confirmed that while Gmail might consume SORBS data as an input, it was one of many, and they did not observe significant changes in deliverability at Gmail due to SORBS listings.
17 Nov 2018 - Email Geeks
What the documentation says
Technical documentation and historical overviews of email security systems provide a factual basis for understanding SORBS's function and eventual dissolution. They generally confirm that SORBS was conceived to identify and block open relays and compromised servers. The ultimate shutdown of SORBS signifies a shift in the email ecosystem, where other, more dynamic, and integrated reputation services have become dominant in combating spam and ensuring legitimate email delivery.
Key findings
Original purpose: SORBS (Spam and Open Relay Blocking System) was designed as an anti-spam project to identify servers sending email via proxy and open-relay servers through real-time checks.
Listing criteria: It listed IP addresses and domains known for spamming or having open relays, acting as a database for email servers with problematic histories.
Long operational history: SORBS operated for over two decades, signifying its long-standing presence in the anti-spam landscape.
Historical context: Understanding SORBS's historical function highlights the evolving nature of email security and the continuous effort to combat spam, as detailed in guides like A brief history of email blacklists.
Focus on active threats: With SORBS no longer active, email senders should now prioritize adherence to best practices and monitoring their standing on currently active and influential email blocklists.
Importance of reputation: Regardless of specific blocklists, maintaining a strong sender reputation is crucial. Blocklists for both IP addresses and domains can still severely impact reputation and deliverability, as noted by platforms like Klaviyo.
Beyond blocklists: Modern email deliverability relies heavily on factors beyond just blocklist presence, including engagement rates, proper email authentication, and content quality. These factors determine whether emails successfully reach the inbox.
Technical article
Documentation from CSO Online reports that SORBS, a long-standing list of email servers known for distributing spam, officially shut down operations in June 2024, after over two decades of activity. This marked a significant change in the blocklist landscape.
21 Jun 2024 - CSO Online
Technical article
Documentation from Klaviyo Help Center states that blocklists, also known as blacklists, exist for both IP addresses and domains. They can severely impact sender reputation and email deliverability, meaning messages may not reach their intended recipients.