Send & Receive Issues

How to Fix SMTP Relay Public IP Blocked by Spamhaus

Algirdas JasaitisAlgirdas Jasaitis Nov 2, 2026 871 views

Question details

The user's SMTP relay with a static public IP is continuously being blocklisted by Spamhaus despite having a correct SPF record and no obvious spam sources.

How to Fix SMTP Relay Public IP Blocked by Spamhaus
Product
SMTP Relay
Device & OS
not provided
Scenario
Operating an SMTP relay using a static public IP for email transmission.
Observed behavior
The IP is repeatedly listed by Spamhaus, disrupting email delivery, even though SPF records are configured properly.
Before you start

Before requesting a delisting from Spamhaus, ensure you have administrative access to your email server, firewall logs, and network monitoring tools. Requesting removal before fixing the root cause will result in immediate re-listing.

Solution 1Recommended

Investigate Network and Fix the Root Cause

Identify the underlying issue causing the spam blocklist before requesting removal from Spamhaus.

SPF authorization alone does not prevent an IP from being listed if spam is actively originating from your network. You must thoroughly audit your systems to find the source of the unauthorized emails.

1
Review SMTP and Firewall Logs

Analyze outgoing SMTP traffic (port 25) in your firewall logs to identify which internal IP addresses are sending high volumes of mail.

2
Inspect Devices and Applications

Check IoT devices, networked printers, and legacy applications that might be compromised or misconfigured to send unauthenticated emails.

3
Verify Reverse DNS (PTR) and Relay Settings

Ensure your public IP has a valid Reverse DNS record matching your hostname and that your SMTP server is not acting as an open relay.

4
Scan Connected Devices

Run comprehensive antivirus and malware scans on all servers and workstations connected to your network to rule out botnet infections.

Investigate Network and Fix the Root Cause
Important: Only submit a delisting request to Spamhaus after you have definitively identified and blocked the source of the spam.
Free Microsoft Office alternative

Experience a Lightweight Office Suite with WPS Office

While troubleshooting complex server and SMTP relay issues requires specialized IT tools, your day-to-day IT documentation and report management doesn't have to be complicated. WPS Office provides a powerful, free alternative to Microsoft Office for creating and editing documents, spreadsheets, and presentations.

  1. 1. Download the Installer: Visit the official WPS website and download the free installer for your operating system.
  2. 2. Install WPS Office: Run the downloaded file and follow the straightforward on-screen instructions to complete the setup.
  3. 3. Open and Edit Documents: Launch WPS Office to instantly start viewing, creating, or editing your Word, Excel, and PowerPoint files.
Easily draft email server configurations, network reports, and IT documentation.Seamless compatibility with Microsoft Office formats like .docx and .xlsx for analyzing exported firewall logs.Lightweight installation with fast startup times for busy system administrators.Familiar user interface requiring no steep learning curve.
QA img-9

Frequently Asked Questions

Why does Spamhaus block my IP even with a valid SPF record?

SPF records only authorize which servers can send emails on behalf of your domain. If a device on your network is compromised and sends spam, Spamhaus will still block the IP regardless of your SPF configuration, as their systems detect actual spam behavior, not just authentication.

How do I know if my SMTP server is an open relay?

An open relay allows anyone on the internet to route emails through your server without authentication. You can use free online SMTP testing tools (like MXToolbox) to run an open relay test against your public IP address to verify your security settings.

What should I do if a network printer is sending spam?

Immediately isolate the printer from the internet by blocking its outbound access on port 25 at the firewall level. Next, update its firmware, change all default administrator passwords, and reconfigure it to use secure, authenticated SMTP on port 587 instead of direct send.