It doesn't appear we have to do anything and they have backed off Jan 11 switch and have found a novel method to continue to support old android clients. Nutshell: A new intermediate will indirectly sign the current Let’s Encrypt intermediate certificate (R3). This ensures that clients that know the...

Two ways...

1) you have a blank transport file you postmapped so no lookup matches
2) you remove the transport file location and only use the ldap entry
ie) zmprov ms `zmhostname` zimbraMtaTransportMaps 'proxy:ldap:/opt/zimbra/conf/ldap-transport.cf'

With letsencrypt signing their own certificates beginning Jan 11, here is a link to a new feature that was added for acme.sh to support the preferred chain should anyone need to revert back to IdentTrust intermediate signed (very old android clients) or test early with the ISRG Root X1 signed before...

Should be able to do this with transport maps. Not tested but it would go something like this. Note: put the transport file where you think it makes the most sense for you and call it what you want. Could be in ~zimbra/common/conf with modern versions of Zimbra since that is where main.cf and master...

I have one of our web developers looking at the js now to see if we can come up with a quick fix. The quick fix is to restore /opt/zimbra/jetty/webapps/zimbra/js/MailCore_all.js and .zgz from P15. (and either flush browser cache, or bump zimbraCacheBusterVersion and restart mailboxd.) Thanks again ...

Is OWASP enabled on this server? Yes OWASP is enabled. We don't think it's related however given that other browsers are able to display it correctly. It looks more like a bug related to browser incompatibilities when setting body style width for that iframe. I have one of our web developers lookin...

All good info. Thanks for that.

This was reported and is being tracked as ZBUG-1998

Greetings, Some emails are no longer viewable after patch 16 when viewing with firefox that were previously viewable with patch 15. Safari and Chrome work as expected with patch 16. Zimbra will "containerize" the email to display it in an iframe but are botching the width for firefox. For ...

Hi JDunphy, To answer to your questions : 1- amavis is cpu-bound 2- messages are deferred 3- I did not set any rules 4- spamassassin --version gives : SpamAssassin version 3.4.2 running on perl 5.26.1 You need to update SA to 3.4.4 ... Ref: https://spamassassin.apache.org/news.html There are a few ...

A few questions: 1) Is the amavisd cpu bound? 2) Do the messages end up in the deferred queue after tim-eout or do they complete? 3) Do you have any custom rules? 4) What version of SA are you running (spamassassin --version) ... 3.4.4 is the default for 8.8.15 A few timeouts... $active_ttl is set f...