Nothing sacred - basically the same thing you've seen in this thread and in other posts - I've modified it slightly since my version is in OpenVZ - instead of the zmcontrol stop/start, I'm actually...

This question has been answered in this thread -- read back a few pages. I understand your frustration - I was thinking the EXACT same thing about FOSS/Enterprise and this "feature" that seemed to...

Basic strategy, regardless of virtual or bare metal:

1) rsync /opt/zimbra to another machine while Zimbra is running

2) stop zimbra

3) back up ldap

4) rsync /opt/zimbra again with Zimbra...

Yes, sorry! I'll fix my post....hadn't had enough coffee....also, let me restate about stopping Zimbra.....I run a virtualized setup with OpenVZ. I actually stop the virtual server and back it up...

I woke up in a panic this morning because it occurred to me that I hadn't restarted my backup script since upgrading to 8.x -- After watching the backup take WAY longer than normal, I found the large...

How right you are. Sorry, I didn't see the note about the patch on the download page.

I'm now running:

Release 7.1.4_GA_2555.RHEL5_64_20120105094627 CentOS5_64 FOSS edition, Patch 7.1.4_P1.
...

I'm having the same problem. Upgraded last night to 7.1.4_GA_2555.RHEL5_64 and have already had calls today that we couldn't support because we can no longer access our customer's email accounts.
...

Thanks for all the tips. I've successfully upgraded my Fedora 7 32-bit 5.0.18 FOSS to CentOS 5.5 64-bit 7.0.1 FOSS in an OpenVZ container.

That's correct. We actually just do a restart of Zimbra, not the entire server, which is a bit quicker, but either way -- restarting fixes the problem.

Just wondering if anyone saw this and had any comments. Sorry to bump, but we're needing to manually restart Zimbra every time we make a change to the attachment settings, which is a bit of a...

I'm having the same problem. We needed to allow a normally-blocked attachment from being blocked yesterday, then again this morning, and both times, Zimbra stopped relaying mail. I tracked down...

I came here also to ask this exact question. I'm happy to see that it's a clean cut answer. Not the answer I was hoping to see, but, nonetheless, thanks for making it clear.

Well while my previous post does fix the problem, it's only temporary. When Zimbra restarts, something rewrites the main.cf file with the hash config for transport.db again.

So, digging back to...

Well while my previous post does fix the problem, it's only temporary. When Zimbra restarts, something rewrites the main.cf file with the hash config for transport.db again.

So, digging back to...

I'm not sure this is the correct fix, but I was having the same problem with transport.db not existing. I did just upgrade from 5.x and couldn't send mail due to this error.

What I did was modify...

I'm not sure this is the correct fix, but I was having the same problem with transport.db not existing. I did just upgrade from 5.x and couldn't send mail due to this error.

What I did was modify...