Zimbra Error 450 4.7.1 Client Host Rejected: 3 Easy Fixes
Zimbra error 450 4.7.1 "Client host rejected: cannot find your hostname" means that the Zimbra MTA refused a message at the RCPT step because the sending server has no usable host name in DNS. It is a temporary (450) rejection produced by Postfix, so the mail is not lost: a proper sender keeps it in its queue and retries. This guide explains the log line, shows the two ways to fix it (on the sender side and on your Zimbra server) and what to check first. The old version of this article was mostly about SPF, blacklists and upgrades; those do not cause this particular message, so they were removed.
Contents
- The Zimbra error 450 log line
- What causes Zimbra error 450 4.7.1
- Step 1: find the cause of Zimbra error 450 in the active restrictions
- Step 2: fix the sender side (best option)
- Step 3: relax the check on your Zimbra server (only if needed)
- Step 4: rule out the policy daemon
- What does not cause Zimbra error 450
- FAQ
- Is Zimbra error 450 4.7.1 permanent?
- Why does the log show "unknown" for the client in Zimbra error 450?
- Where can I read more?
The Zimbra error 450 log line
The line appears in /var/log/zimbra.log on the MTA (the IP address is masked):
Feb 10 16:16:33 sd-15xxx postfix/smtpd[1832]: NOQUEUE: reject: RCPT from
unknown[x.x.x.x]: 450 4.7.1 Client host rejected: cannot find your hostname,
[x.x.x.x]; from=<someone@sender.com> to=<someone_email@mydomain.com>
proto=ESMTP helo=<smtp_sender.com>

Two details identify the cause. The client is shown as unknown[x.x.x.x]: Postfix could not turn the IP address into a host name. And the text says "cannot find your hostname", which is the standard reply for a failed client name check.
What causes Zimbra error 450 4.7.1
The Postfix documentation describes the restriction reject_unknown_client_hostname. It rejects the request when the client IP address has no name (reverse lookup fails), when the name has no address (forward lookup fails), or when the name does not map back to the client IP address. The reply code is set by unknown_client_reject_code and is 450 by default, and it is always 450 when the lookup failed because of a temporary DNS problem. A weaker version, reject_unknown_reverse_client_hostname, checks only the reverse lookup.
Zimbra exposes this as a DNS check of the MTA. The Administrator Guide lists "DNS checks" among the MTA protocol options: reject mail if the client's IP address is unknown, if the host name in the greeting is unknown, or if the sender's domain is unknown. The restrictions are stored in the multi-valued attribute zimbraMtaRestriction. So the Zimbra error 450 appears when this check is on and the sender's DNS is incomplete: typically a server without a PTR record, or a PTR that does not match its A record.
Step 1: find the cause of Zimbra error 450 in the active restrictions
As the zimbra user on the MTA, read the restrictions that Zimbra generated. The original post used postconf for this; it shows the Postfix settings that are actually in use:
su - zimbra
postconf | grep "smtpd_sender_restrictions"
postconf | grep "smtpd_client_restrictions"
zmprov gcf zimbraMtaRestriction
Look for reject_unknown_client_hostname (or reject_unknown_reverse_client_hostname) in the client restrictions, and for reject_unknown_sender_domain and reject_invalid_helo_hostname in the other lists. These entries decide which senders get a Zimbra error 450 and which get another message.
Step 2: fix the sender side (best option)
The clean fix is on the sending server, because the check is a normal anti-spam measure. Ask the sender, or fix it yourself if you own the server:
- Create a PTR (reverse DNS) record for the sending IP address at the provider that owns the IP.
- Make the PTR name resolve back to the same IP with an A record (forward-confirmed reverse DNS).
- Use that name in the
HELO/EHLOgreeting of the sending server.
Test it from any machine with dig -x x.x.x.x +short for the PTR and dig <name> +short for the A record; both must return the matching values. After the DNS change the next retry of the sender is accepted and the Zimbra error 450 stops for this server.
Step 3: relax the check on your Zimbra server (only if needed)
If the sender is a partner or a system you cannot change, you can remove the restriction for the whole MTA. A multi-valued attribute is changed with a minus sign in zmprov, as the Administrator Guide shows with the plus sign for +zimbraMtaRestriction:
zmprov mcf -zimbraMtaRestriction reject_unknown_client_hostname
You can also clear the matching option in the Administration Console, in the MTA settings of the Global Settings (DNS checks). The configuration daemon zmconfigd picks up the change from LDAP within two minutes, or you can run zmmtactl restart. Be aware of the price: every spammer with a hostless IP address is now accepted by this check, so your spam filter carries more load. Prefer fixing the sender, or allow only that sender network with zimbraMtaMyNetworks as in the guide for Zimbra client host rejected.
Step 4: rule out the policy daemon
The original post also suggested looking at the cbpolicyd log for a locked database, because a failing policy service can produce rejections. Follow the cbpolicyd log in /opt/zimbra/log while the error happens. If the log shows a database problem, handle it as in the article on Zimbra 451 4.3.5 server configuration problem; that case returns 451, not 450, so compare the exact reply code first.
What does not cause Zimbra error 450
- SPF, DKIM and DMARC. They are checked later, on the message; this rejection happens at
RCPTbased on the client address and name only. - Message size. The attribute
zimbraMtaMaxMessageSizeonly limits the size of a message. - Blacklists. A blacklist hit gives a different text that names the list.
FAQ
Is Zimbra error 450 4.7.1 permanent?
No. A 4xx code is temporary, so the sender retries. The mail arrives after the DNS of the sender is fixed, or it bounces after the sender gives up.
Why does the log show "unknown" for the client in Zimbra error 450?
Because the reverse DNS lookup of the client IP returned no name. This is the main clue; Postfix shows "unknown" for the same reason in the $client_name macro.
Where can I read more?
See the Postfix postconf reference for reject_unknown_client_hostname and the Zimbra Administrator Guide for the MTA DNS checks.
To fix Zimbra error 450 4.7.1: confirm the active restriction, make the sender's PTR and A records match, and relax the check on your server only as a last resort.
Comments
Post a Comment