I'm not sure yet, I have a system now where I can reproduce the various issues. There is more than one problem in play for sure. postconf behavior changed between postfix 2.6 and postfix 2.7 is part of the issue.

There are two issues involved, but the primary one people are hitting is that zmconfigd fails when postconf is called with a long enough argument list. See the previously mentioned bug. There is also a minor issue with how main.cf gets created when it doesn't exist, but that's a rare occurence. If you hit the issue with postfix, do *not* delete main.cf. Instead, I suggest examining the zmconfigd.log file and running the postconf command it logs from the command line as a workaround.

FYI: Had the same problem after upgrading from 6.0.10 to 7.0.0 GA an Ubuntu 10.04 64-Bit LTS (empty main.cf). After copying main.cf from 6.0.10, postfix is working again!

Hello! This problem will be on Ubuntu 8.04 Zimbra 7? If yes, simply copy main.cf from backup is universal solution, Or it is better to wait bugfixes and version 7.0.1? Can I update production server now?

Hello! This problem will be on Ubuntu 8.04 Zimbra 7? If yes, simply copy main.cf from backup is universal solution, Or it is better to wait bugfixes and version 7.0.1?

The solution is listed above.

Originally Posted by GlooM

Can I update production server now?

That's a decision to do that is yours to make. Try it and see if you want to live dangerously, try it on a test server or wait for the bug to be closed and a fix issued. Whatever you decide make sure you take adequate backups of your server.