Being listed on a blocklist like SORBS can be concerning, especially when facing requests for payment to remove your listing. Our research indicates that paying for delisting from SORBS is generally not necessary or recommended. Many in the deliverability community advise against it, emphasizing that legitimate delisting processes typically do not involve fees.
Key findings
No payment needed: The consensus is to avoid paying for SORBS delisting, as requests for payment often come from automated or questionable sources.
Automated responses: Initial rejection emails, especially from 'payments' addresses, are often automated and a human response can be triggered by replying.
Information request: Requesting the specific headers or reasons for the listing is a common and effective step to begin the delisting process.
Fixing root causes: Addressing the underlying issues that led to the listing, such as spam traps or compromised accounts, is crucial for long-term resolution.
Key considerations
Assess true impact: Before expending significant effort, determine if the SORBS listing is genuinely affecting your email delivery or if it's a minor issue.
Engage directly: If you choose to pursue delisting, persist in communicating with SORBS to get a human response and specific details.
Avoid perfectionism: Not every blocklist listing warrants immediate or extensive intervention, particularly those with low impact.
Prioritize efforts: Focus on major blocklists that have a more significant influence on your deliverability, and use a blocklist checker to keep an eye on them.
Clean practices: Ensure your sending practices, such as using double opt-in for mailing lists, prevent future listings.
Email marketers often find themselves in a predicament when listed on blocklists like SORBS, especially when the path to delisting seems unclear or involves a payment request. The community generally advises against paying, suggesting that persistent communication and understanding the actual impact on deliverability are more effective strategies. Many share experiences where SORBS listings had minimal effect on their overall email success.
Key opinions
Don't pay: Many marketers unequivocally state that paying for SORBS or similar blocklist delisting is not necessary.
Reply to automated emails: A common strategy is to reply to automated rejection emails to prompt a human response and obtain crucial listing details.
Low impact: Many marketers report that SORBS listings have a very limited impact on their deliverability, with some estimating bounces around 5% or less when active.
B2B relevance: For B2B senders, addressing a SORBS listing might be slightly more beneficial, but it's still often seen as low effort for minimal gain.
Compulsion vs. necessity: Some marketers are driven by perfectionism to delist, even when the impact is negligible, highlighting the psychological aspect of blocklist management.
Clean practices: Implementing double opt-in for email lists is a proactive measure to avoid future blocklist issues.
Key considerations
Verify listing impact: Always confirm if a SORBS listing is truly causing deliverability problems before investing time in delisting efforts.
Persistent communication: If delisting is desired, be prepared to follow up to ensure a human reviews your request.
An Email Geeks marketer inquired about the necessity of paying SORBS for delisting after their initial request was rejected from a payments email address, questioning if payment was the only way out.
15 Aug 2019 - Email Geeks
Marketer view
A Marketer from Email Geeks advised replying to the automated SORBS message to engage a human, suggesting this approach usually leads to getting listing headers and a delisting within 48 hours.
15 Aug 2019 - Email Geeks
What the experts say
Email deliverability experts highlight that while a SORBS blocklist listing can be a nuisance, its real-world impact on email delivery is often less severe than perceived. They caution against perfectionism in managing every single blocklist, especially those with limited reach, and stress the importance of understanding the root causes of listings over resorting to payment for delisting. Their insights reinforce the idea that strategic focus on major blocklists and maintaining good sending hygiene are more impactful.
Key opinions
Limited impact: Many experts confirm that SORBS has a relatively minor effect on overall deliverability for most senders.
Avoid payment: Payment for blocklist removal is widely discouraged by experts as it's not a standard or advisable practice.
Realistic expectations: It's unrealistic to expect to be off every single blocklist; focus should be on the most influential ones.
Root cause analysis: Identifying and resolving the underlying reason for a listing, like a spam trap hit, is crucial for lasting resolution.
Proactive monitoring: Regular monitoring of your sending infrastructure can help prevent future blocklist issues.
Key considerations
Focus efforts: Direct resources towards managing listings on more impactful blocklists such as Spamhaus, which can significantly affect your email deliverability. For more on this, read about dealing with Spamhaus and other blacklists.
Understand policies: Be aware that some blocklists have convoluted or even contradictory listing and delisting policies.
Strategic communication: When engaging with blocklist operators, be prepared to provide specific information like message headers to facilitate the process.
Implement authentication: Strengthen your sender reputation by properly configuring email authentication protocols like DMARC, SPF, and DKIM. This can reduce future listing incidents.
Monitor bounce logs: Regularly review your bounce logs to precisely identify which blocklists are impacting your deliverability, as seen on MailMonitor.
Expert view
An Expert from Email Geeks shared a unique experience where an entire ESP was listed on SORBS because an employee published data showing SORBS didn't block much mail, inadvertently reducing its usage.
15 Aug 2019 - Email Geeks
Expert view
An Expert from Email Geeks advised that one cannot be a perfectionist with blocklists due to their sheer number, confusing policies, and operators who might arbitrarily list senders.
16 Aug 2019 - Email Geeks
What the documentation says
Official documentation and support resources from major email service providers and hosting companies consistently advise against paying for blacklist removal. They emphasize that the focus should be on identifying and rectifying the root cause of the listing, such as malware or poor sending practices. These sources generally guide users towards submitting legitimate delisting requests after ensuring their systems are clean and compliant with email best practices.
Key findings
No fee-based delisting: Authoritative documentation typically states that legitimate delisting processes do not involve payment.
Address root causes: The primary advice is always to clean up any issues (e.g., malware, spam traps) that led to the listing.
Direct requests: Manual delisting requests to the blocklist operator are the standard procedure after rectifying issues.
Good sending practices: Preventive measures like using double opt-in lists are crucial for avoiding future blocklist appearances.
Key considerations
Avoid suspicious services: Do not engage with services that claim to offer paid delisting or do not accept standard removal requests.
Clean your environment: Thoroughly check for and remove any malware or unauthorized access that could be causing spam transmissions before requesting delisting.
Maintain compliance: Adhere to best practices for email sending, ensuring your lists are legitimate and properly managed, as detailed in guides like why your emails are going to spam.
SendGrid support documentation recommends against engaging with services that charge fees for delisting, advising that legitimate delisting processes typically do not require payment.
15 Jan 2020 - SendGrid
Technical article
InMotion Hosting's support guide advises users to first clean their site of any malware or hacks before submitting a delisting request to a blocklist provider.