The receiver permanently rejects the connection or message because the sending IP is on a DNS blocklist (DNSBL) or the content was classified as spam.
Common causes
- A compromised mailbox or web form sent spam through your server.
- The IP is in a dynamic range (Spamhaus PBL) and is not supposed to deliver directly.
- Shared IP: another customer on the same IP caused the listing.
- On your own server: DNSBL lookups go through public resolvers (8.8.8.8), Spamhaus returns error codes and every mail gets rejected.
How to check it
Check the IP at Spamhaus (octets reversed)
dig +short 10.113.0.203.zen.spamhaus.org
Find blocklist rejections in the log
journalctl -u postfix --since today | grep -i 'blocked using'
Find accounts with suspiciously many logins/mails
journalctl -u postfix --since today | grep -o 'sasl_username=[^ ,]*' | sort | uniq -c | sort -rn | head
What actually helps
- Stop the source first: lock the account, change the password, secure the form, delete spam from the queue.
- Only then request delisting from the list operator – otherwise the next listing follows.
- For a PBL listing, relay through a smarthost with a clean IP or use a static IP with a proper PTR.
FAQ
What does a 127.255.255.254 answer from Spamhaus mean?
It is not a listing but an error: the query came through a public or open resolver that Spamhaus does not answer.
How long does delisting take?
For Spamhaus SBL/XBL usually minutes to hours after the request, as long as the spam has stopped. Some lists also expire automatically after a few days.
Full page with every command and the German/Italian version: daniele-michelin.com/en/errors/smtp-554-5-7-1/
First published at daniele-michelin.com. The error lexicon covers HTTP, DNS, TLS, mail, database, PHP, nginx, systemd and Nextcloud, in German, English and Italian.
Top comments (0)