Zimbra Forums

You could turn on amavisBadHeaderLover for the domain.

zmprov md example.com amavisBadHeaderLover TRUE

Try this ...

sudo /opt/zimbra/common/sbin/postcat -qv B8C8C6019C3

zmcontrol status

Another option is if you are using the Zimbra Anti-Spam service, you can use the amavisBlacklistSender setting.

e.g.

zmprov md example.com +amavisBlacklistSender badspammer.org <<==note the use of the plus sign character

We do have an internal bug report on this issue. No ETA on when it will be resolved though.

Try this...

zmcontrol stop

sudo su - <PRESS ENTER>

As root...

mv /opt/zimbra/jetty/work/ /tmp/

mkdir /opt/zimbra/jetty/work/

chown zimbra:zimbra /opt/zimbra/jetty/work/

su - zimbra <PRESS ENTER>

zmcontrol start

Ok, lets remove a zero from the end... zmprov -l ms `zmhostname` zimbraImapActiveSessionEhcacheMaxDiskSize 10737418240 zmprov -l ms `zmhostname` zimbraImapInactiveSessionEhcacheMaxDiskSize 10737418240 zmprov -l mcf zimbraImapActiveSessionEhcacheMaxDiskSize 10737418240 zmprov -l mcf zimbraImapInactiv...

Might want to view the CacheSize settings as well.

zmprov -l gs `zmhostname` | grep -i cachesize

zmprov -l gacf | grep -i cachesize

Hmm...weird. The error is referencing 107374182400, which is 100GB. Do you have anything with that value?

zmprov -l gs `zmhostname` | grep 107374182400

zmprov -l gacf | grep 107374182400

Alright, can you lower zimbraImapActiveSessionEhcacheMaxDiskSize to 2G?

zmprov -l ms `zmhostname` zimbraImapActiveSessionEhcacheMaxDiskSize 2147483648

zmcontrol stop

zmcontrol start