This is important; have you opened a Support Case with Zimbra to get the Release Notes updated?

I will also add that many senders attempting to delivery things like newsletters often will not retry failed deliveries at all if your mail server is down and you have no backup MX. At least here in the US, backup MX services cost as little as $25/domain per year (more if you want more maximum stora...

Zimbra does lazy writes for deleting blobs after deleting a mailbox, so it may take some time before you see an increase in free disk space. You can always use the built-in tool (zmblobchk) to find “unexpected” blobs on disk (blobs on disk that aren’t referenced in MySQL) and delete them. Hope that ...

The Zimbra account in Linux does not have a password.

The installer configures /etc/sudoers appropriately.

To become the Zimbra user, first become root, and then “su - zimbra” and you should be OK.

Hope that helps,
Mark

This is a known bug that has been fixed before but seemingly not fully squashed.

Suggest you open a Support Case with Zimbra on this.

Hope that helps,
Mark

Thanks, thats the first thing I have looked at, but... there is always but... The problem is that the /opt/zimbra was moved to a different disk, and that wasnt included in the daily backup snapshots of the cloudstack. :( so I only have the backup of data.mdb from Nov 2019 I have zextras suite on th...

Zimbra's official migration partner is Audriga.com.

I have also used Bit Titan with good success.

Hope that helps,
Mark

I would recommend restoring LDAP from a backup.

https://wiki.zimbra.com/wiki/LDAP_data_import_export

Hope that helps,
Mark

Your A, MX and PTR records appear to align OK.

You'll need to fill out the block removal request form:
https://support.microsoft.com/en-us/sup ... a03d6b8d75

Hope that helps,
Mark

If you feel that the mailboxd shutdown hang is due to MariaDB taking time to write things out to disk, you can do two things to speed this up. Both involve editing ~/conf/my.cnf. First, use a tool like mysqltuner.pl to make sure that the innodb_buffer_pool_size variable is 110% to 125% of the aggreg...