Help for owners
My new server's IP address is on a spam blocklist and my email is rejected
Short answer
A new server address can arrive already listed, because someone else used it before you or it belongs to a range that mail systems distrust. Spamhaus, for example, lists compromised addresses and ranges not meant to send mail. Do not send more mail from it. Find which list, then fix the cause or send through a mail service.
Does this sound like your situation?
- Mail from my server bounces with a message about a block list or poor reputation.
- A checker shows the new IP address as listed.
- It started right after the move to the new host.
- Mail to some providers works and to others fails.
- The old host's address never had this problem.
Why does this happen?
The address had a previous owner
Addresses are reused. If an earlier customer sent spam or was compromised from it, the listing can still be there when it is handed to you.
The address range is not meant for sending mail
Spamhaus describes a policy list covering addresses that are not meant to send mail directly, even though they may be legitimate, such as some residential or dynamic ranges.
Confirmed by spamhaus.org
The new server is sending something it should not
A compromised site, an open mail relay or a form abused by bots can send spam. Spamhaus lists exploited and compromised addresses.
Confirmed by spamhaus.org
Mail setup was not rebuilt
A reverse DNS name, SPF and DKIM that matched the old host do not automatically match the new one, which makes mail look untrustworthy.
What can I do about it today?
- Stop sending bulk or marketing mail from the serverMore sending while listed makes it worse.
- Note which list and what the bounce saysThe bounce text or checker names the list and often a link explaining it.
- Run a free blocklist checker on the IP addressShare the result with your host or developer.
- Do not pay for removal from unofficial sitesRemoval is requested through the list operator's own process.
- Tell your host the address was listed on arrivalHosts can sometimes assign a different address.
- Send important mail through your mail provider meanwhileFor example your normal mailbox service, not the web server.
When should I bring someone in?
- Customers cannot receive invoices or password resets.
- You find the site or server sending mail you did not write.
- The listing returns after removal.
How do I handle it?
- Identify the list and the reasonI read the list operator's own entry, which says why the address is listed.
- Check the server for abuseScripts, plugins, forms and mail logs, since a compromise is the first thing to rule out.
- Fix mail authenticationReverse DNS, SPF, DKIM and DMARC aligned to the new address.
- Request delisting, or change the addressDelisting only after the cause is gone, or ask the host for a clean address.
- Move transactional mail to a sending serviceMail from the application goes through a provider that manages reputation.
The price depends on what I find, so I quote in writing after a short discovery call. Tell me what is happening and I reply within 24 hours.
What do owners ask about this?
Is this the same as my domain being blacklisted?
No. A domain listing follows your domain name. An IP listing follows the address of the server. See the page on a blocked domain for that case.
Can I just request removal?
You can, but if the cause remains it returns. Find the cause first.
Will changing host solve it?
It may avoid a bad address, but the same sending habits would list the next one.
Sources
How was this page made?
I drafted this page with AI assistance from the official documents listed under Sources. Found a mistake? Tell me.