Spamhaus has been quietly listing misconfigured mail servers for years. What changed in November 2026 is that they announced it in advance.
Late October, Spamhaus published its first consolidated Sender Guidelines — previously these requirements were scattered across FAQs, blog posts, and support tickets. The document also carries a note that matters right now: “Starting in November 2026, we are gradually rolling out a requirement for every sending IP to have a valid HELO, a reverse DNS (PTR) record, and a matching A record.”
The rollout is gradual and Spamhaus has not published a phase-by-phase schedule. That is their polite way of saying it has already started.
What Forward-Confirmed Reverse DNS Actually Means
Forward-confirmed reverse DNS (FCrDNS) is a three-way check:
- Your sending IP has a PTR record pointing to a hostname — say,
mail.example.com. - That hostname has an A record pointing back to the same IP.
- Your SMTP server announces
mail.example.comin its EHLO greeting.
All three must agree. If your PTR resolves to 203.0.113.25.static.yourhost.com — the auto-generated reverse your hosting provider assigns — that is not acceptable for a dedicated sending IP. Spamhaus explicitly flags generic provider rDNS as a problem, not a pass.
Configurations That Will Get You Listed
The Sender Guidelines are direct about what causes a listing on the CSS (Email Spam IPs) or XBL (Compromised IPs) zones:
- Announcing
EHLO localhost,EHLO SERVER01, or any placeholder name that does not resolve to the sending IP. - Having no PTR record — common on fresh VPS instances or after a server migration to a new IP.
- Presenting different HELO values from the same IP. The guidelines state that multiple HELO values from one IP “may indicate residential proxy and/or malware behaviour.”
- A PTR that resolves to a hostname whose A record points somewhere else entirely (for example, an old retired IP).
The XBL listing is the worse outcome: ZEN, Spamhaus’s combined blocklist queried by most receiving mail servers, includes XBL. Getting listed there means outright rejection, not just a bump in the spam score.
How to Check Your Setup
Verify three things for each sending IP:
# 1. What PTR record does your sending IP have?
dig -x YOUR.SENDING.IP +short
# 2. Does that hostname resolve back to your IP?
dig A the-hostname-from-step-1 +short
# 3. What HELO does your server actually announce?
# Postfix: check the effective value with:
postconf myhostname
For a live test, send a blank message to helocheck@abuseat.org — it replies with the HELO name your server presented from its perspective. The Sender Guidelines page also includes a DNS checker tool. Use the Spamhaus IP and Domain Reputation Checker to see whether your IPs are already listed.
Postfix: The SMTP HELO name defaults to the value of myhostname in main.cf. Make sure it matches the PTR hostname on your sending IP. If you override it with smtp_helo_name, that name must also resolve back to the sending IP.
Exim: Control the HELO name via helo_data in the smtp transport block. Same rule applies: it must match the PTR.
Remember that PTR records are typically managed by whoever owns the IP block — usually your hosting provider or ISP, not your DNS zone. If your provider assigns you a generic reverse, you will need to request a custom PTR through their control panel or support.
The Five Minimum Requirements
The Sender Guidelines page lists five requirements all senders must meet “to avoid being listed”:
- Confirmed opt-in for every mailing list subscriber. No sending to addresses that did not explicitly confirm.
- Forward-confirmed reverse DNS on every sending IP — PTR to FQDN, A record back to the same IP.
- A HELO/EHLO hostname that resolves to the sending IP and stays consistent across all connections from that IP.
- IPv6 senders: a sending address within an allocation of /64 or larger, with valid reverse DNS on that address.
- SPF, DKIM, and DMARC on all sending domains; DKIM’s
d=domain must match the RFC 5322 From address.
The guidelines also set a bounce rate limit of 5% and require unsubscribe requests to be actioned within two days.
What This Means for kalfaoglu.net Customers
If your domain is hosted with us and you send email directly from your own server — not through our shared mail relay — now is a good time to check your PTR record. The command dig -x <your-server-IP> +short will show you what Spamhaus sees when it looks up your IP.
If you are on a shared hosting plan, your outbound mail travels through our MTA infrastructure, which has correct forward-confirmed rDNS configured. You do not need to take any action.
If you manage a VPS with its own mail stack (Postfix, Exim, or similar), run the checks above now. Getting listed on the Spamhaus CSS or XBL will cause delivery failures at any mail provider that queries Spamhaus data — which covers the overwhelming majority of receiving mail servers worldwide.
Questions? Open a support ticket.
Sources: Spamhaus Sender Guidelines · Spam Resource, Oct 28 2026 · MDaemon Blog · SMTPedia