Zimbra Forums

Upgrade to at least 5.0.5 and this is no longer a problem.
In 5.0.4, the error should only occur when in a message or calendar view that contains the event referencing the attachment with the malformed header, and reloading the web client will get things going again.

If "NAMESPACE" is the only capability disabled: [QUOTE]>zmprov mcf zimbraImapDisabledCapability NAMESPACE >zmprov mcf zimbraImapSSLDisabledCapability NAMESPACE [/QUOTE] Just unset those attributes: $ zmprov mcf zimbraImapDisabledCapability "" $ zmprov mcf zimbraImapSSLDisabledCap...

Can you post a screenshot of the account setup screen from Zimbra Desktop?

please post the stacktrace(s) from /opt/zimbra/log/mailbox.log for any errors that occurred during the backup

Is it the mailbox mysqld or the logger mysqld that is consuming the cpu?

It looks like the problem was always with the logger mysql password. I think the mailbox mysql migration is done. Let's check the database: # su - zimbra $ mysql zimbra > select * from config; > describe scheduled_task; I think you could make a copy of zmsetup.pl, comment out everything in the apply...

what does zmcontrol status show? Is there anything in the /opt/zimbra/log/mailbox.log when the mta is trying to deliver a message to your mailbox?

what vps are you using? the problem is that the vps only provides a virtual server with a total amount of memory; applications won't necessarily see that as a monolithic contiguous segment of memory, which is what the jvm in particular needs
this vps article may or may not help

have you done any troubleshooting when the server is in this state? does zmcontrol status show everything running? does the server not respond over any mailbox interfaces (http, pop, imap)? is there any change in system resource utilization (cpu, memory, disk) during this time? if you run zmcontrol ...

do the processes 15410 15542 15530 still exist?