- When your mail starts bouncing with rejection codes, a blacklist is the usual culprit.
- This playbook covers checking the major lists, finding the root cause, and getting delisted for good.
One morning your quotations start bouncing back with messages like 550 rejected — listed at Spamhaus. Your server IP or domain has landed on a blacklist (RBL — realtime blocklist), and until you fix it, a large slice of the internet refuses your mail. Here is the recovery playbook, in order.
Step 1: Confirm the Listing
- Read the bounce message — it usually names the blocklist and gives a lookup URL.
- Run your sending IP and domain through a multi-blacklist checker (MXToolbox blacklist check or similar covers the important lists at once).
- Note which lists you appear on. Spamhaus and a handful of others matter enormously; dozens of tiny hobby lists matter almost none.
Step 2: Find the Root Cause Before Delisting
Delisting without fixing the cause guarantees relisting, and repeat listings become sticky. Common causes we see on Nepali servers:
- A compromised mailbox pumping spam after a password leak — check mail queue and outgoing logs for abnormal volume.
- A hacked website on the same hosting account sending spam through PHP scripts.
- Shared server neighbours: on shared hosting, another customer got the shared IP listed — your provider must act.
- Genuine bad practice: purchased address lists or bulk mail from a normal mailbox.
Step 3: Clean Up
- Reset passwords on all mailboxes; enable two-factor authentication where available.
- Scan and clean the website; update CMS and plugins.
- Purge the outgoing mail queue of pending spam.
- Stop any bulk sending from the regular mail server — move newsletters to a proper sending platform.
Step 4: Request Delisting
Each list has its own process. Spamhaus and most major lists offer a self-service removal form once the abuse stops; some expire listings automatically within days of clean behaviour. Be honest in removal requests — state what happened and what you fixed. Repeatedly requesting removal without fixing anything can make listings permanent.
Step 5: Protect Your Reputation Going Forward
- Publish SPF, DKIM and DMARC so your legitimate mail is verifiable.
- Monitor your IP and domain monthly with a blacklist checker, or use a provider that monitors for you.
- Keep bulk mail on dedicated newsletter infrastructure with clean, opted-in lists.
- If shared-IP listings recur, upgrade to hosting with a dedicated IP or a managed email platform — Zoho and Google Workspace customers essentially never face IP blacklisting because the platforms guard their ranges ferociously.
Why Shared Hosting Makes This Risk Someone Else's Fault, but Still Your Problem
On shared hosting, a listing caused by a completely unrelated customer on the same server IP still bounces your legitimate mail exactly as if you had caused it — blocklists operate on the IP address itself, with no awareness of which specific account is responsible. This is the core argument for the escalation step of moving to a dedicated IP or a managed platform once shared-IP listings become a recurring pattern rather than a one-off incident: it removes your business's deliverability from being hostage to strangers' behavior on shared infrastructure you have no visibility into or control over.
Frequently Asked Questions
How long does delisting take?
Self-service removals often clear within hours; reputation-based lists may take days of clean sending. Full recovery of inbox placement can take one to two weeks.
Do blacklists affect receiving mail?
No — only your sending is refused. Incoming mail continues normally, which is why listings often go unnoticed at first.
Should I just change server IP?
Only after fixing the cause; a new IP with the same compromise relists within days and burns another address.
Tired of shared-IP problems? Move to managed business email or corporate hosting with monitored IPs — talk to our deliverability team.
