About this article: This article is reviewed against the cited sources. This is source research, not lab validation. Check the stated versions and your own requirements before making changes.
A bounce reading 554 5.7.1 ... Client host ... blocked using zen.spamhaus.org comes from the receiving mail server, not from Spamhaus. It means the receiver looked up your sending IP address in Spamhaus's combined ZEN list and got a "listed" answer. ZEN is four lists in one (SBL, CSS, XBL and PBL), and which one listed you decides what to fix.
Look up your sending IP, read the return code, then follow the route for that list. A listing is a symptom: Spamhaus says the cause must be corrected before a removal request is worth making, because the address is re-listed if the problem continues.
What the error means
The wording here is the default of a receiver running Postfix. Postfix's default_rbl_reply template is $rbl_code Service unavailable; $rbl_class [$rbl_what] blocked using $rbl_domain${rbl_reason?; $rbl_reason}, and the reject code maps_rbl_reject_code defaults to 554. For a connecting client, the class is "Client host", the "what" is the address in brackets, and the domain is zen.spamhaus.org. Receivers on other software word it differently, but the DNS test behind it is the same.
A DNS blocklist (DNSBL) works through DNS. The receiver reverses the IP address, adds the list's name, and asks for an A record. Spamhaus describes ZEN as "the combination of all Spamhaus' free IP-based DNSBLs into one single powerful and comprehensive blocklist", and says a query "generally results in several distinct answers within the same DNS response packet, one for each dataset where the IP is listed." Each answer has its own return code.
Spamhaus publishes the return codes for its public IP zones:
| Return code | List | Meaning |
|---|---|---|
| 127.0.0.2 | SBL | Spamhaus SBL data |
| 127.0.0.3 | SBL | Spamhaus CSS data |
| 127.0.0.4 | XBL | CBL data |
| 127.0.0.9 | SBL | Spamhaus DROP data (in addition to 127.0.0.2) |
| 127.0.0.10 | PBL | ISP maintained |
| 127.0.0.11 | PBL | Spamhaus maintained |
Three further codes are not listings: 127.255.255.252 (typing error in the DNSBL name), 127.255.255.254 (query via public or open resolver) and 127.255.255.255 (excessive number of queries). Spamhaus says these "must not be taken to imply that the object of the query is 'listed'".
What each list means, in Spamhaus's own words:
- SBL lists IP addresses "identified as malicious", seen in "adversarial activity, e.g. sending spam, snowshoe spamming, hosting malicious content". Single IPs and ranges are listed.
- CSS is "dedicated to SMTP traffic, only listing port-25 based detections". It is delivered in the SBL zone.
- XBL contains "IPv4 and IPv6 addresses exhibiting signs of compromise i.e. IPs that are legitimate but have been hijacked to use by third-party exploits".
- PBL is "end-user IP address ranges from which email should never be sent directly to the final destination". The IPs "are not necessarily 'bad' - simply, they should never be sending email."
Likely causes
| Cause | Return code | What you see |
|---|---|---|
| Sending directly from a dynamic or end-user IP range | 127.0.0.10 or 127.0.0.11 (PBL) | A new or small server on a broadband or similar range; nothing wrong with the mail itself |
| A website, plugin or application on the server sending spam | 127.0.0.3 (CSS) | Listing appears and expires within days; recent change to a site or mailer |
| A compromised machine behind the IP, or malware | 127.0.0.4 (XBL) | Listed again soon after removal, because the problem persists |
| Your network or hosting provider is itself listed | 127.0.0.2 or 127.0.0.9 (SBL) | Many customers of the same provider blocked together; a range is listed |
| A newly assigned IP that carries someone else's history | Any, for example XBL or CSS | The server is new and has sent nothing |
| A bad reading from the receiver's side | 127.255.255.254 | The receiving server queried through a public resolver |
On the fifth row, the XBL FAQ says: "a user may be assigned an IP address from their provider that is listed in the XBL because of the situation of a previous user of that IP address."
Prove the cause before changing anything
All of these read only.
1. Find the exact address that connected. Use the IP shown in the bounce or in your mail server's log. If a firewall translates your address, the public address is the one that matters.
2. Query ZEN from your own resolver. Spamhaus's DNSBL FAQ shows the method with a test address: reverse the octets and add the zone. For the documentation address 203.0.113.25, reversed, this is:
dig +short 25.113.0.203.zen.spamhaus.org
No answer (an NXDOMAIN response) means "not listed" from this resolver. One or more 127.0.0.x answers means listed, and the last digits identify the lists. Spamhaus's own check shows the pattern: "A query for a 'listed' object must answer with a correct return code ... Queries for 'not_listed' objects must always return NXDOMAIN".
Run the test from your own DNS resolver. Spamhaus says its public DNSBLs are free "if ... queries are not being made from a public resolver or an IP with generic rDNS", and that a 127.255.255.254 answer means the query came through an open public resolver and is not a listing.
3. Check the individual list pages. The SBL, CSS, XBL and PBL pages each say how a listing arises and expires, and each says to begin removal at the Spamhaus IP and Domain Reputation Checker. The PBL FAQ says to "look up the IP in the IP and Domain Reputation Checker, and click 'show details' then follow the steps for removal".
Example (illustrative): web01 (203.0.113.25) sends order confirmations. Bounces from mx.example.net say 554 5.7.1 ... Client host [203.0.113.25] blocked using zen.spamhaus.org. dig +short 25.113.0.203.zen.spamhaus.org from web01's own resolver returns 127.0.0.3, the CSS code. A contact form plugin on the site was recently updated, and the mail log shows hundreds of messages to unrelated recipients overnight. The likely cause is spam sent through the website, so removing the IP before closing that hole would be futile.
Fix
The fix depends on the list. Take a record of the return code and the time before you start.
PBL (127.0.0.10 or 127.0.0.11)
PBL does not say you misbehaved; it says this address should not deliver mail directly to other people's mail servers. Spamhaus's policy: "All the email originated by an IP listed in PBL is expected to be submitted - using authentication - to a SMTP server which delivers it to destination. The SMTP server can be either supplied by the ISP connecting the IP or by an external mail service."
- If the machine is an ordinary user or application server, send through an authenticated relay on port 587 or 465 instead of delivering directly. Spamhaus encourages "end-user mail submission via encrypted and authenticated connections on port 465 and/or 587." See "Outbound mail times out after a move: the new host cannot reach port 25" for the relay approach.
- If the machine really is a mail server on a static IP, the PBL FAQ allows a single-IP exclusion when all of these hold: the IP is static, it is an outbound mail server, it has appropriate forward and reverse DNS, and it is assigned to the person requesting. It also asks that "port 25 outbound is closed for use by any device other than that mail server." Spamhaus says to "allow approximately 15 minutes for DNS propagation". Exclusions made by end users "expire after one year, and will be immediately reversed if spam is detected from them."
CSS (127.0.0.3)
CSS listings "expire quickly: normally, three days after last spam detection", and Spamhaus warns that "whatever caused the problem MUST be identified and corrected before removing an IP from CSS", because the IP "will also [be] re-list[ed] immediately if a problem continues to be detected." Self-removals are limited. Look for compromised accounts, vulnerable websites or CMS plugins, and misconfigured mail software.
XBL (127.0.0.4)
Spamhaus lists an IP on the XBL when it has strong grounds to think a machine using it "is insecure, compromised, or infected", and does not disclose every behaviour. Its examples include malware, "free VPN" applications using the device as a proxy, brute-force participation, and "attempts to relay mail using illegitimately obtained credentials". Listings "automatically expire after a period of time once the malicious behavior is no longer detected". On Linux and Unix machines, the FAQ says, "more often than not ... the problem is not malware as in 'virus,' it is security: systems that are deployed and forgotten will get compromised." Find and fix the compromise, then request removal at the Reputation Checker, the only place XBL removals are handled. A repeat listing means "the detected problem has not been corrected."
SBL (127.0.0.2 or 127.0.0.9)
"Only these companies [the network or hosting companies responsible for that IP] can deal with SBL removals. If you are a general user, speak with your Internet Service Provider (ISP) to seek remediation." The SBL page says listing details can be viewed at the Reputation Checker by IP, range or SBL ticket number. Contact your hosting provider with the IP, the time, the return code and the bounce text, and ask them to resolve it with Spamhaus.
When you run the receiving server and see this for good mail
Postfix lets you restrict the codes that count as a listing, so error codes such as 127.255.255.254 cannot reject mail. The reject_rbl_client restriction accepts an =d.d.d.d suffix with ranges, and the postconf(5) manual's own example uses 127.0.0.[2..11]:
smtpd_client_restrictions = permit_mynetworks, reject_rbl_client zen.spamhaus.org=127.0.0.[2..11]
Do not paste that line over your own. Setting smtpd_client_restrictions replaces the whole list. First save a copy (cp /etc/postfix/main.cf /etc/postfix/main.cf.bak-20261119), then print the current value with postconf smtpd_client_restrictions and add only the reject_rbl_client item to what is already there, in the position you intend. After editing, read it back with postconf -n and run postfix check (postfix(1): it warns about bad directory and file ownership or permissions, so it is not a full test of the new line).
Disruptive step: changing smtpd_client_restrictions changes which inbound connections are refused on the whole server, and postfix reload applies it ("Re-read configuration files"). To back out, copy the saved main.cf back, run postfix check and reload again. Then send a test message from an unlisted address and read the log. Spamhaus warns that "some mail servers mistakenly reject all mail due to that 127.255.255.* return code" and that this "can be resolved by changing how your mail server queries Spamhaus DNSBLs."
Confirm the fix
- Repeat the
digquery for your IP from your own resolver. A removed or expired listing returns NXDOMAIN. - Wait for propagation. The PBL FAQ says to allow approximately 15 minutes. For XBL, "not all networks sync updates from us at the same speed. Please allow 24 hours to pass before opening a new ticket."
- Send a test message to a recipient at the server that rejected you and read the response.
- Confirm the cause is closed: the account locked, the plugin patched, or mail routed through the authenticated relay.
What to watch afterwards
- Repeat the ZEN check on a schedule for every address that sends mail for you.
- Spamhaus's best-practice list for a clean reputation includes: slowly ramping up the volume on a new IP; configuring a new IP properly "at least 30 days before the first send" (CSS page) and restricting outbound port 25 to the mail server.
Read next
Related articles you may want next.
- HostingApplication Email Rejected or Junked After a Server Move: SPF, DKIM, DMARC and PTRApplication mail bouncing or junked after a migration? Read Authentication-Results, then fix SPF, DKIM, DMARC alignment, PTR and Microsoft 365 relay settings for the new path.Read article
- TroubleshootingOutlook.com rejects mail: 550 5.7.1 part of their network is on our block list (S3150)Outlook.com bounce 550 5.7.1 S3150: the bounce text says your provider's network is on a block list. Check the IP, the requirements, then delisting.Read article
- TroubleshootingOutbound mail times out after a move: the new host cannot reach port 25Mail queued and port 25 times out after moving to Azure, AWS or Google Cloud? Prove the block with a TCP test and switch to an authenticated relay.Read article
Risks and limits
- These commands have not been run or lab-tested. They are taken from the Spamhaus and Postfix pages listed below.
- The Spamhaus IP and Domain Reputation Checker is the tool the Spamhaus pages direct you to for removal. Its steps are not described here; follow the instructions it gives, and do not use it as a substitute for fixing the cause.
- The wording of the rejection depends on the receiving mail server software. The Postfix default is quoted here.
- A ZEN listing is one receiver's input. Other receivers may block you for other reasons, and delisting does not guarantee delivery.
- Spamhaus's free DNSBL use has conditions (non-commercial, low volume, not from a public resolver).
Sources
- Spamhaus: ZEN Blocklist — Spamhaus, no date shown, accessed 18 November 2026
- Spamhaus: Spamhaus Blocklist (SBL) — Spamhaus, no date shown, accessed 18 November 2026
- Spamhaus: Combined Spam Sources (CSS) — Spamhaus, no date shown, accessed 18 November 2026
- Spamhaus: Exploits Blocklist (XBL) — Spamhaus, no date shown, accessed 18 November 2026
- Spamhaus: Policy Blocklist (PBL) — Spamhaus, no date shown, accessed 18 November 2026
- Spamhaus: DNSBL usage FAQ — Spamhaus, no date shown, accessed 18 November 2026
- Spamhaus: XBL FAQ and PBL FAQ — Spamhaus, no date shown, accessed 18 November 2026
- Postfix: postconf(5), configuration parameters — Postfix documentation, no date shown, accessed 18 November 2026
- Postfix: postfix(1) and postconf(1) — Postfix documentation, no date shown, accessed 19 November 2026
- Postfix 3.11.0 source: mail_params.h — Postfix project, tag v3.11.0, accessed 18 November 2026
This article was originally published on .