4.5.6 Changes to Zimbra's handling of postfix main.cf

[DVan]

I just thought I'd post this information, since it was a show stopper for me last night when I updgraded to the latest release of zimbra.

First off we have a slightly custom Postfix configuration for use with RT, or Request Tracker. In order to get this working you have to define your mydestinations = $mydomain rather than zimbra's default of localhost in the main.cf. After the upgrade I would add this entry and then after restarting postfix services it would always revert back to localhost no matter what I did.

Long Story short, it appears some changes were made and now the zmscripts that start postfix parse more values than before. The values are parsed out of the following file:

/opt/zimbra/conf/zmmta.cf

I'm wondering if zomeone from Zimbra can confirm for me if changes to this file will not be overwritten with future upgrades much like the .conf files.

[area]

Yes, a real show stopper for me as well.

See the thread at URGENT: /etc/alias configuration after upgrade
which includes the modifications to /opt/zimbra/conf/zmmta.cf and also a response
from Zimbra re new LDAP attributes relevant to this issues in v4.5.7.

[DVan]

Wish that was posted earlier. The issue I see here is this will now be requiring a FQDN, rather than the variable attributes that postfix allows.

Can Anyone from Zimbra confirm it will accept the Postfix variables (and multiple), such as $mydomain, $myhostname, etc., or is this new method going to break postfix features and application compatibility?

[Bill Brock]

Are you defining the variable first in the cf file before using it?