Reverse DNS / PTR error: Rejected because reverse DNS is missing or doesn't match
The receiver looked up the sending IP's PTR record and found none, or found a hostname that doesn't resolve back to that IP.
How to fix Reverse DNS / PTR
- Have the IP's owner set a PTR record to a hostname you control, and point that hostname's A record back at the IP.
- Use the same hostname in the SMTP HELO/EHLO greeting.
Why this happens
Something in the server or DNS setup doesn't meet the basic rules of the SMTP conversation: how the server identifies itself, whether it has reverse DNS, whether it uses TLS, or whether it is allowed to relay at all.
How to keep it from coming back
Set a real hostname with matching forward and reverse DNS, enable TLS, authenticate before relaying, and re-test the setup after any change to your mail server or provider.
Should I retry a Reverse DNS / PTR error?
Not as it stands. A permanent error means the same message will be refused again until the cause is fixed on your side. Fix the cause first, then send a fresh message; if it keeps failing after that, check the full text of the bounce for the exact reason.
Got the full bounce message?
The text after the code names the exact reason, and the same code can mean different things at different receivers. Paste the whole message into the decoder - it runs in your browser and nothing is sent.
Open the bounce decoderRelated error codes
Seeing this again and again? That's usually a reputation or authentication problem we can trace and fix at the source.
How we help: Consulting · Private infrastructure · Managed mailboxes · Monthly support