JDunphy wrote:This was reported and is being tracked as ZBUG-1998

Did you get any feedback on this bug so far?

you might use the mdb_copy command: https://wiki.zimbra.com/wiki/OpenLDAP_Performance_Tuning_8.0 That document says "Note: The copied MDB file will *not* be a sparse file. It will be the actual size of the database." so I don't think it will help So it *will* help, mdb_copy will create a ...

You don't actually need 80 GB of filesystem space to host this file, it is just a max addressable size. You can see the actual size with `du`.

If you want a non-sparse copy eg. for backup purposes, use /opt/zimbra/common/bin/mdb_copy (optionally with -c to skip free pages).

Thanks.
We've been running and testing these in our lab for quite some time now (while they were still work in progress on github), and they have been working fine.

Is there any indication when the updated OpenSSL and nginx packages will be formally released? (ie. out of beta) Together with an upcoming patch, or independently?

JDunphy wrote: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.)

Actually the original fix was ZCS-8165 in P13: https://github.com/Zimbra/zm-web-client ... b9ee08ba6b
Not ZBUG-1656 from P14.

This was partially reverted in a later commit: https://github.com/Zimbra/zm-web-client ... 4b31093d80

Confirmed; you can fix it on P16 by restoring /opt/zimbra/jetty/webapps/zimbra/js/MailCore_all.js{,.zgz} from P15.

Looks very much like ZCS-8165, this issue was originally fixed in P13 with: https://github.com/Zimbra/zm-web-client ... b9ee08ba6b
But partially reverted again in P16 by ZBUG-1885: https://github.com/Zimbra/zm-web-client ... 4b31093d80

You are right;
P10: incorrect display (long horizontal scroll bar)
P15: correct display (no scroll bar)
P16: incorrect display again (same as P10)

Those are all versions I can verify right away.

So this issue was fixed somewhere in P11 through P15, but re-introduced in P16.