Try setting zimbraCBPolicydCheckSPFEnabled to TRUE

zmprov mcf zimbraCBPolicydCheckSPFEnabled TRUE

OR

zmprov ms mta.example.com zimbraCBPolicydCheckSPFEnabled TRUE

zmconfigdctl restart

zmcbpolicydctl restart

Try updating zimbraMtaMaximalQueueLifetime.

zmprov mcf zimbraMtaMaximalQueueLifetime 1d

or

zmprov ms mta.example.com zimbraMtaMaximalQueueLifetime 1d

zmmtactl restart

If you set zimbraCBPolicydAccessControlEnabled to TRUE at the serverConfig, chances are cbpolicydAccessControl is enabled. When you test cbpolicydAccessControl, check the /opt/zimbra/log/cbpolicyd.log file to see if the access control rules are working (...or not working). When you make changes to t...

This can be easily done using Zimbra's cbpolicyd service.

Cert should be updated now.

e.g.

zmprov md example.com amavisSpamLover TRUE

zmamavisdctl restart

Other options...

amavisVirusLover
amavisBannedFilesLover
amavisBadHeaderLover
amavisUncheckedLover

>>How to disable the ldap service in zimbra.

How many Zimbra nodes in your setup, and what services are they running?

>>And how to add another ldap details in zimbra.

Like what?

Thanks for the article Mark! Very useful!

We actually have a few cases on this issue. Right now, we have an internal escalation to have the developers look into this issue; still un-resolved at this time.

This is just a mere suggestion, when you get a chance, can you check for the "FixCRLF" line in the /opt/zimbra/conf/opendkim.conf.in file? grep FixCRLF opendkim.conf.in FixCRLF no If FixCRLF is set to no, can you change it to yes in the /opt/zimbra/conf/opendkim.conf.in file? Just make sur...