Upgrade to Zimbra 5.0.8 caused external MTA relay host to be lost

[greenrenault]

We upgraded a few Zimbra servers from 5.0.2 and 5.0.6 to 5.0.8 a few weeks back. Just noticed that the upgrade caused the external MTA relay host configuration to be lost. Has anyone else seen this?

[Whitney]

I just tried to upgrade from 5.0.2 to 5.0.8. I lost the external MTA relay host config too. When I tried to add it back, I could not get it to work. Any email that I tried to send was put into the "deferred" queue. Have you been able to get things working again after the upgrade?

[greenrenault]

Yes, I know how to fix this. Unfortunately, there also seems to be a bug in the Zimbra Admninistration UI which is preventing the MTA relay to be set. Possibly, another one for bugzilla?

Anyway, to fix using the Zimbra CLI:
SSH to the server and su to the Zimbra user and issue the following command:

zmprov -z ms your.zimbra.server.host zimbraMtaRelayHost the.relay.host:25

Where:
1. your.zimbra.server.host is the Zimbra server
2. the.relay.host is the MTA relay host to send email too

You should not need to restart Zimbra (but I do anyway zmcontrol stop && zmcontrol start)

Send some external email and watch the zimbra.log, you should see the email routed externally now via the relay host.

All email should now be sent via the external relay host