Here's my strange dilemma. I am running ZCS open source version 6.0.7. I have a backup script that does the usual rsync, then stop zimbra, rsync again, then start zimbra back up.
However, lately there is a new problem. When zimbra starts back up, postfix fails to run. Here's what's happening:
When I look at the main.cf file in /opt/zimbra/postfix/conf/ it has a line that looks like this:
smtpd_recipient_restrictions = reject_non_fqdn_recipient, permit_sasl_authenticated, permit_mynetworks, reject_unauth_destination, reject_unlisted_recipient, reject_invalid_hostname, reject_non_fqdn_sender, permit
However, when I run my backup script and stop/start services, most of the time the line blanks out like this:
Which postfix does not like. It generates errors like:
zimbra postfix/smtpd: fatal: parameter "smtpd_recipient_restrictions": specify at least one working instance of: check_relay_domains, reject_unauth_destination, reject, defer or defer_if_permit
It's doing that because the list is blank. Is there anything in Zimbra that might be resetting this value to null upon restart?
Here's how I fix it, for now, until a better solution comes along:
1. cd /opt/zimbra/postfix/conf/
2. cp main.cf.backup main.cf (I made a backup of the GOOD file)
3. cd /opt/zimbra/bin/
4. ./postfix stop && ./postfix start
That seems to correct it. That tells me that somewhere in Zimbra it's rebuilding/reconfiguring the main.cf file.
Any help would be appreciated with this very unusual problem.