Zimbra Forums

What is the status of the Maldua downloads with regard to 10.1.8? The 'recent' releases on the advanced page just shows:
The Security Advisories mention fixes in 10.1.8.

Your nginx permissions aren't right, re-run /opt/zimbra/libexec/zmfixperms. (nginx needs `setcap CAP_NET_BIND_SERVICE=+ep` to run as zimbra user) That means that 'zimbra-nginx' will always end up with wrong permissions when installed on its own, and always needs a subsequent run of the zimbra insta...

I hadn't see version 10.1.8 was available, so I had only installed available apt updates. These: # aptitude show zimbra-clamav zimbra-clamav-lib zimbra-mta-components zimbra-nginx zimbra-proxy-components | grep -Fi State State: installed (1.0.6-1zimbra8.8b4.22.04), upgrade available (1.0.8-1zimbra8....

That does indeed 'fix' it. When I add disable_mime_output_conversion = yes to '/opt/zimbra/common/conf/main.cf' and do 'killall -SIGHUP master', the mail is no longer converted to quoted printable and DKIM is intact. But that's a generated configuration file, so this is not a permanent change. Plus...

Since the upgrade to Zimbra 10.1.7 (from 10.1.4) the DKIM breakage has gotten worse. My above hack to bypass Amavis doesn't work anymore. In fact, I also tried disabling Amavis altogether: zmprov ms `zmhostname` -zimbraServiceEnabled antispam # and reboot But that didn't fix it. You can tell Amavis ...

We just upgraded:

• From: zcs-10.1.4_GA_4200000.UBUNTU22_64.20241224171952.tgz
• To: zcs-10.1.7_GA_4200000.UBUNTU22_64.20250425163635.tgz

Went fine, no deviations from earlier installations.

No abnormalities detected in use so far.

hi my name is rio, i have a problem with mail zimbra foss builds 10.1.4.GA.4200000.UBUNTU20.64 UBUNTU20_64 FOSS edition when i get new mail from noreply@mxtoolbox.com; with spam DMARC_FAIL_REJECT=9 for mxtoolbox.com and expiry@letsencrypt.org By now i noticed mxtoolbox.com and letsencrypt.org mails...

I've just had another report of DKIM breakage. This time, the body is not in quoted printable. Plus, it's another case than my test mail, as the body does not contain non-ascii. I don't understand this one. What I can do still, is completely disable Amavis and see if that prevents it. With my hack, ...

It was for only one user. He since then avoids the use of time components in filters, so we're not affected by it any more.

Hmm, I had not fully realized spam filtering would be disabled completely then too. By disabling the filter on port 10032 that is still intact, going by the X-Spam* headers. So, I simply wrote this hack script to comment-out the offending filter from the config: # cat zimbra-remove-amavis-from-maste...