Skip to main content

Blocklists

Spamhaus PBL: Why Your IP Is on the Policy Block List

By Tom Sather•Updated October 11, 2026•7 min read

The Spamhaus PBL lists IP ranges that shouldn't send mail directly, like home broadband. It isn't a spam accusation; the fix is usually authenticated SMTP.

On this page

Your IP is on the Spamhaus PBL (Policy Block List) because the network that owns it, or Spamhaus, has marked it as an address that shouldn't send email directly to other mail servers. It's mostly home and small-business broadband space. It isn't an accusation of spam. The usual fix is to send through an authenticated mail server (your ISP's, your email provider's, or an ESP) instead of straight from that IP.

Removal is possible only if the IP is a static, properly configured mail server that's assigned to you, and only if the network allows it.

What a PBL rejection looks like

Most receivers check Spamhaus ZEN, which includes the PBL, so the bounce usually names ZEN rather than the PBL:

554 5.7.1 Service unavailable; Client host [203.0.113.7] blocked
using zen.spamhaus.org; https://check.spamhaus.org/query/ip/203.0.113.7

To tell it's the PBL specifically, look up the IP at check.spamhaus.org, or check the ZEN return code:

Return codeMeaning
127.0.0.10PBL entry maintained by the ISP
127.0.0.11PBL entry maintained by Spamhaus

If the code starts with 127.255.255, it's not a listing at all. It's an error caused by how the lookup was made. See why blocklist checks give wrong answers.

What the PBL is (and isn't)

Spamhaus describes the PBL as end-user IP ranges "from which email should never be sent directly to the final destination." Two kinds of entries:

  • ISP-maintained. Network operators with a PBL account list their own customer ranges and set the policy, including whether customers may request removal.
  • Spamhaus-maintained. Spamhaus lists end-user space it believes shouldn't be sending direct-to-MX, including ranges with heavy concentrations of infected machines.

Nobody else can nominate an IP, and nothing you did put it there. The PBL FAQ says plainly that listings aren't the result of end-user action. It's a statement about what kind of address this is, not about your behavior.

It also doesn't stop you sending email. It stops you sending email directly from that IP to a receiver's mail server on port 25. Spamhaus designed the PBL to be checked only against the IP making the SMTP connection, and says mail should not be blocked just because a PBL-listed IP appears earlier in the Received headers. So if your laptop on home broadband sends through Gmail or Microsoft 365, the receiver sees Google's or Microsoft's IP, and your home IP's PBL listing never matters.

Common causes, most likely first

  1. A device or app sending direct-to-MX. A website contact form, a scanner, a backup tool or a script on an office or home connection, configured with a recipient's MX as its server instead of a proper relay.
  2. A mail client that isn't authenticating. Spamhaus's FAQ says the PBL usually bites when an email program isn't authenticating correctly with the outgoing server. Typical culprit: still using port 25 without SMTP authentication.
  3. Self-hosted mail on a dynamic IP. Running your own mail server on residential broadband. Spamhaus's advice for this setup is to "be prepared to face a lot of challenges."
  4. A new server on a range that was never cleaned up. A static IP that's now a real mail server but sits in a range the ISP or Spamhaus listed as end-user space.

If you send through an ESP, Google Workspace or Microsoft 365 and still see a PBL rejection, look closely at which IP the bounce names. It's probably not the PBL, or not your mail stream. Reading the bounce is the place to start.

How to fix it

If it's a mail client, device or app

  1. Point it at an authenticated submission server: your ISP's outgoing server, your mailbox provider's SMTP server, or a transactional email service.
  2. Turn on SMTP authentication (username and password, or an app password).
  3. Use port 587 or 465, not 25. Spamhaus notes SMTP authentication should run on those ports, and many ISPs block port 25 for residential customers anyway.

Spamhaus's FAQ says enabling authentication usually corrects the problem immediately. No removal request is needed, because the listed IP is no longer connecting to receivers.

If it's your own mail server

On a dynamic IP, don't fight the listing. Configure the server to relay outbound mail through a smarthost (your ISP's relay or a commercial relay service). Spamhaus calls this the best solution for dynamic IPs.

On a static IP, you may qualify for removal. Spamhaus's criteria are that the IP:

  • is static,
  • is an outbound mail server,
  • has matching forward (A) and reverse (PTR) DNS, for example 203.0.113.7 with a PTR of mail.example.com and mail.example.com resolving back to 203.0.113.7,
  • is assigned to you, and
  • has port 25 closed to other devices on the network.

If all of that is true, request the exclusion at check.spamhaus.org. Spamhaus says PBL removals are handled only there. A few things to know:

  • The network's policy decides whether end-user removal is allowed at all. If it isn't, ask your ISP for a business or static IP with mail use permitted, or relay through a smarthost.
  • Spamhaus says the change takes about 15 minutes to propagate.
  • End-user exclusions expire after one year (ISPs can set shorter periods) and are reversed immediately if spam is seen from the IP.
  • Requests from freemail addresses aren't accepted, and removing many IPs can get your removal access revoked. Large blocks are the ISP's job.

Before you request removal, check your PTR record. The 550 5.7.25 page explains why missing reverse DNS causes problems beyond Spamhaus.

How to confirm it's fixed

  • For the relay fix: send a test to an outside address, open the headers with the header analyzer, and confirm the first external hop is your provider's server, not your own IP.
  • For an exclusion: re-check the IP at check.spamhaus.org, then watch for the zen.spamhaus.org rejections to stop in your logs.

Keeping it from coming back

  • Make authenticated submission on port 587 or 465 the standard for every device and app that sends mail.
  • Block outbound port 25 on your network for everything except your real mail server, so a misconfigured app (or an infected machine) can't send direct-to-MX.
  • Put a reminder in your calendar if you rely on an exclusion. It expires after a year, and the IP can be listed again when it does.
  • If an exclusion is reversed because spam was detected, treat it as a compromise. That's XBL or CSS territory, not a PBL quirk.

When to get help

If you run your own outbound mail and keep hitting Spamhaus listings, or you can't tell whether a rejection is the PBL or something more serious, it's worth having someone look at your setup. Get in touch.

FAQ

Does a PBL listing mean I'm a spammer?

No. The PBL says an IP range shouldn't send mail directly, usually because it's consumer broadband. Spamhaus says listings aren't caused by anything the end user did.

Can I remove my IP from the PBL?

Only if it's a static, properly configured outbound mail server assigned to you, and the network's policy allows end-user removal. Otherwise, send through an authenticated relay instead.

I use Gmail or Microsoft 365 from home. Will the PBL affect me?

No. The receiver checks the IP that connects to it, which is Google's or Microsoft's server, not your home IP.

How long does a PBL removal last?

Spamhaus says end-user exclusions expire after one year, or sooner if the ISP sets a shorter period, and are reversed immediately if spam is detected.

Sources

Related guides

Still stuck?

Some deliverability problems take an experienced eye to untangle. Tell me what you're seeing and I'll tell you what I'd check first. The first 30-minute call is free.