The receiving server runs Postfix and requires the sending server to have reverse DNS that checks out: a PTR record for its address, naming a host whose own address record points back to it.
450 4.7.25 Client host rejected: cannot find your hostname, [203.0.113.5]
2 other wordings of the same rejection
No PTR record at all:
450 4.7.1 Client host rejected: cannot find your reverse hostname, [203.0.113.5]
Older Postfix versions:
450 4.7.1 Client host rejected: cannot find your hostname, [203.0.113.5]
Your bounce names your own domain and sending address where this one says example.com and 203.0.113.5.
| Code | 450 4.7.25 |
| Sent by | Any mail server |
| Type | Temporary — retried |
| Cause | Reverse DNS |
See what receivers see
Send one email to our test address and get back the sending server’s reverse DNS, TLS, authentication and blocklist results — the things this bounce is about.
What it means
“cannot find your reverse hostname” means there is no PTR record at all. “cannot find your hostname” is stricter: the PTR record exists, but the name it gives does not resolve back to the same address (forward-confirmed reverse DNS fails).
Postfix sends 450 by default, a temporary rejection, so the sending server retries — but it will keep failing until the DNS is fixed. It also answers 450 when a DNS lookup simply times out.
Why it happens
- No reverse DNS set for the server’s IP address.
- Reverse DNS set to a name with no A record, or an A record pointing somewhere else.
- Sending over IPv6 without IPv6 reverse DNS.
How to fix it
- Set the reverse DNS of the sending address in your hosting or cloud control panel (or ask the provider) to a name such as mail.yourdomain.com.
- Give that name an A record (AAAA for IPv6) pointing to the same address.
- Send a test email to see the reverse DNS receivers see.
Sources
Message text and meaning checked on 25 September 2026 against these official sources:
- Postfix Configuration Parameters — postfix.org