what's the filesystem? (df -T)
That 1884374605 26 /tmp/zmlogger.out (deleted) is 1.7GB which immediately reminded me...
There was a problem with logger in 4.5.5, there was a patch, which was mostly rolled into 4.5.6 but unfortunately the debug mode got left on in a couple of the scripts so those files continued to be large.
4.5.7 lowered the logging level back to the normal level & with that release /tmp/zmlogger.out /tmp/logswatch.out moved from /tmp to /opt/zimbra/log
At the same time, logswatch.out became zmlogswatch.out and I believe stuff either rotated or combined into other logs.
Also zmmtaconfig.log becomes huge:
[SOLVED] running a version 4.5.6 or prior? Prevent Large Log File
If you stay on that version I would temporarily edit /opt/zimbra/libexec/zmmtaconfig and change the default loglevel (on line 55ish) to something lower -change it from 5 to 3
One step further, this should be in the next 5.0 build:
Bug 10398 - clean up logging for swatch, zmmtaconfig
Oh, and also on 4.5.6 the clamav build that was included turned out to be bad:
[SOLVED] Clamd.pid - no such file
Not like I'm suggesting you upgrade or anything...
