[SOLVED] zimbra breaks after bad MT trusted network entry

[cicide]

I used the admin console to add some networks to my MTA trusted network list, and incorrectly added 127.0.0.1/8 instead of 127.0.0.0/8. Upon restarting zimbra (using service zimbra restart on fedora), Zimbra failed to fully restart (some things started, some didn't).

I tried using zmprov to fix the error, but I get an error:

[zimbra@photon ~]$ zmprov modifyServer photon.netgeeks.net zimbraMtaMyNetworks '127.0.0.0/8 192.168.0.0/16 208.106.27.96/28 76.191.187.112/28'

ERROR: zclient.IO_ERROR (invoke Connection refused, server: localhost) (cause: java.net.ConnectException Connection refused)

[zimbra@photon ~]$

I see alot of these in my zimbra.log when another mail server tries to connect to deliver mail to the zimbra server.

May 16 13:21:01 photon postfix/smtpd[21974]: connect from unknown[85.99.95.75]

May 16 13:21:01 photon postfix/smtpd[21974]: fatal: non-null host address bits in "127.0.0.1/8", perhaps you should use "127.0.0.0/8" instead

May 16 13:21:02 photon postfix/master[11681]: warning: process /opt/zimbra/postfix-2.4.3.3/libexec/smtpd pid 21971 exit status 1

May 16 13:21:02 photon postfix/master[11681]: warning: /opt/zimbra/postfix-2.4.3.3/libexec/smtpd: bad command startup -- throttling

May 16 13:21:02 photon postfix/master[11681]: warning: process /opt/zimbra/postfix-2.4.3.3/libexec/smtpd pid 21969 exit status 1


What can I do to restore the system back to functional operations?

Thanks,
Chris

[cicide]

I took this as the time to do an upgrade to 5.0.5. The upgrade resolved the problem.