Denied — Zimbra Relay Access

| Setting | Command to Check | Desired State | | :--- | :--- | :--- | | | zmprov getServer zimbraMtaTlsAuthOnly | TRUE | | Submission Port | zmprov getServer zimbraMtaAuthEnabled | TRUE on port 587 | | Trusted Networks | zmprov getServer zimbraMtaMyNetworks | Only internal subnets | Final Thoughts "Relay access denied" is frustrating because it stops legitimate email. But remember: without this guardrail, your Zimbra server would be an open relay—and it would be blacklisted within hours.

zmprov modifyAccount [email protected] +zimbraAllowFromAddress [email protected] zmprov fc account [email protected] This is a classic "broken copier" or "buggy CRM" problem. Printers, scanners, and legacy applications often hard-code an IP address and try to send mail without logging in. zimbra relay access denied

It usually appears without warning. One minute, a user or an application is sending mail fine; the next, emails are bouncing back. Don’t panic. This error is actually Zimbra’s security system doing its job—it just needs a little adjustment. | Setting | Command to Check | Desired

Change the sending device to use port 587 (Submission) instead of port 25, and enable SMTP Authentication . Most modern email clients (Outlook, Thunderbird, Apple Mail) support this natively. Don’t panic

Add the device’s IP address to Zimbra’s “mynetworks” setting. This tells Zimbra, "Trust anything coming from this IP."