FREE SHIRT - Did you upgrade to 4.0.3?

[Klug]

Originally Posted by gmsmith

Sleep is for the weak

Like backup

[KevinH]

Originally Posted by pacsteel

To be fair, most of the problems I had with the previous version and this upgrade appear to have been related to running on Ubuntu, which the release notes do say is "alpha-level support".

Please put any changes you needed into bugzilla. We want to get Ubuntu fully supported and the quickest way to get there are experience's like yours. Bugs are good, patches are even better.

[KevinH]

Originally Posted by LMStone

P.S. Would be nice to get the amavis tmp directory back on a ram disk though...

You can make this change yourself, but our experience shows that it hurts many more people with the ram disk gets backed up. A few big attachments can fill this up quick so it's better to be on the safe side and have plenty of disk for this.

[dgamez]

Release 4.0.3_GA_406.SuSE10_20061016134245 SuSE10 FOSS edition

Zimbra rules!

[scalper]

geez... misses the shirt

[zimbra@venus ~]$ zmcontrol -v


Release 4.0.3_GA_406.RHEL4_20061016143637 CentOS4 NETWORK edition

[zimbra@pluto ~]$ zmcontrol -v


Release 4.0.3_GA_406.RHEL4_20061016143637 RHEL4 NETWORK edition

cheers!!

[area]

Release 4.0.3_GA_406.RHEL4_20061016134107 CentOS4 FOSS edition

I look after four zimbra servers and have done lots of upgrades and this was the simplest upgrade I have done!

The only issue I have is with the format of the /etc/hosts file in which the install script looks for an IP address with a FQDN as the last entry in the file.

Thanks again for a great product!

[Rick Baker]

Upgrade from 4.02 to 4.03 network edition was perfect.

[LMStone]

Originally Posted by KevinH

You can make this change yourself, but our experience shows that it hurts many more people with the ram disk gets backed up. A few big attachments can fill this up quick so it's better to be on the safe side and have plenty of disk for this.

Kevin,

I asked for bug 8081 to be reopened on this. Between increasing the intial size of the ramdisk, limiting the number of Postfix smtp processes; and running a cron job to stop amavis, clean out the tmp directory, and restart amavis, we haven't seen any problems on our non-Zimbra production Postfix systems.

In the meantime, it's nice to know it's OK for us to configure this manually.

Thanks,
Mark