Why listed IPs get their mail rejected
Large mail providers and corporate servers check the reputation of the sending IP before accepting a message. They query public DNS blocklists, and Spamhaus is the most influential of them. If your server's IP is listed, your mail is rejected unread or sent to spam, so invoices, password resets and order confirmations silently fail to arrive. The bounce usually contains a line such as 550 5.7.1 Service unavailable; client host blocked using zen.spamhaus.org. Keep that bounce: it tells you which IP and which list caused the rejection.
The Spamhaus lists are not the same
| List | Meaning | Typical cause |
|---|---|---|
| SBL | IP or range manually listed as a spam source | Sustained spamming, hosting spammers |
| SBL CSS | Automatically detected low-quality sending | Hacked site script, bulk mail |
| XBL | Infected device or server | Malware, botnet, compromised mailbox |
| PBL | Addresses that should not send mail directly | Residential or dynamic IP; policy, not punishment |
| DBL | Domain names, not IPs | Links in spam or phishing |
PBL is not a penalty. It simply says that consumer connections should send mail through their provider's or mail service's SMTP server rather than directly to recipients.
Checking an IP yourself
The easiest route is the official Spamhaus checker page. Administrators often prefer a DNS query: reverse the IP octets and append the list zone. The example uses the documentation address 203.0.113.25:
dig +short 25.113.0.203.zen.spamhaus.org
dig +short misol.uz.dbl.spamhaus.org
dig +short -x 203.0.113.25
An empty answer means not listed. 127.0.0.2 or 127.0.0.3 indicate SBL or CSS, 127.0.0.4 means XBL, and 127.0.0.10 or 127.0.0.11 mean PBL. Spamhaus does not answer queries that come through public resolvers such as 8.8.8.8 or 1.1.1.1, or returns an error code like 127.255.255.254, so confirm the result on the official page.
Fix the cause before you ask for removal
The most common mistake is requesting removal immediately. If the spam source is still active, the IP is relisted within hours and your next request is treated far more strictly. Find out what is leaving the server first: a hacked site script, a mailbox with a stolen password or a malicious process.
exim -bpc
grep -i 'spamhaus' /var/log/exim/main.log | tail -20
ss -tnp | grep ':25 '
A private clinic in Samarkand, for example, sent appointment reminders to patients. One day every reminder bounced with Spamhaus CSS in the error. Bots had been abusing an outdated contact form to send thousands of messages. After the form was protected, the queue cleared and several days of clean sending observed, a removal request was submitted and the IP was delisted.
Submitting the delisting request
XBL and CSS listings usually offer a self-service form on the checker page: you confirm the problem is fixed, and if no further spam is seen the IP drops off fairly quickly. SBL listings are reviewed manually and usually require the IP owner, meaning the network or hosting provider, to contact Spamhaus. On shared hosting the IP belongs to every customer on the server, so contact support instead of filing the request yourself; sayt.uz customers can open a ticket in the cabinet and attach the bounce text.
Staying off the lists
Give the IP a correct PTR record matching the server's HELO name, publish SPF, DKIM and DMARC for your domains, protect every form from bots and keep the CMS and plugins updated. Send newsletters through a dedicated mailing service or a separate IP, only to subscribers who opted in. Finally, watch outgoing volume: an account that normally sends a few dozen messages a day suddenly sending thousands is the clearest warning before a listing.