Here is a summary of this week’s conference call. A few brief reminders:
- Conference calls are every Tuesday and open to all using either the FreeConferenceCall.com VoIP app or via a dial-in number: https://www.freeconferencecall.com/wall/zetalliance
- Each week’s call agenda can be found at: https://docs.google.com/document/d/1uUUDJpwp2CAylU6lxtbEdVcUX_qSbciyes6gLTWw2fY/edit
- Constructive feedback on these call summaries is always welcome.
July 7, 2020 Conference Call Summary
Persona Email Sending Bugs In 8.8.15 Patch 11
Noah P. reported encountering three bugs after installing 8.8.15 Patch 11 related to sending email from Personas in the Zimbra Web Client:
Bug # 1.) From the Web Client, sending an email from a Persona account results in the email being sent to the recipient, however the email remains in the Drafts folder and does not appear in the Sent folder. This occurs when the Persona address is the primary address of another mailbox account, but does not occur when the Persona address used belongs to a distribution list or alias address.
Bug # 2.) From the Web Client, if sending an email from a Persona account that is the primary address of another mailbox account and which also has a status of Lockout, the message will not send and returns an error of “account.ACCOUNT_INACTIVE”. Manually changing the status of the account from Lockout to Active works around this bug.
Bug # 3.) From the Web Client, if sending an email from a Persona with an inline image in the signature, the message will not send and returns an error of “service.PERM_DENIED”. If the inline image is deleted, bug # 1 described above may still occur. This bug does not occur if the signature image is attached, instead of inline, and likewise does not occur if the inline image is included as part of a reply message.
Noah said that he has opened Zimbra support case # 01026494 for these bugs. Mark S. commented that he saw a mention on the Zimbra Forums where others encountered an email sending issue after installing 8.8.15 P11 and wondered if it was the same issue that Noah was experiencing. Noah said that he did not believe so, since the earlier email sending issue reported on the Zimbra Forums was fixed in a revised version of 8.8.15 Patch 11 that was re-released on July 3rd. Noah said he continues to experience the bugs listed above, even after having installed the revised Patch 11 version.
Finding Deleted Mailboxes in the Zimbra Backups
David M. said a client recently asked if a deleted mailbox was still in his Zimbra NG backups, even though at least 90 days had passed, and the mailboxes are normally set to be purged after 90 days. He asked for the best way to check his backups. Cine suggested using the command line option of: “zxsuite backup getAvailableAccounts firstname.lastname@example.org” where email@example.com is replaced with the address of the desired mailbox. This will indicate if the mailbox is still available for restoration in the backups. If the mailbox is not found in the backups, it will return a message of: “Can’t find the backup folder for the account”. Cine also said that if examining the file system on the backup server, mailboxes are named after their Zimbra mailbox ID, which is located in the “accounts” sub-directory.
Migrating Zimbra Mailbox Backups Between Servers
Noah P. said he is moving his Zimbra installation from one set of servers to another set of servers. He asked if rsync is the best way to move Zimbra NG backup data. He also asked if it should take more time to move the backup data than is available in a maintenance window, would it be ok to temporarily disable the real-time NG backups on the source servers, finish moving the data with rsync, then do another Smart Scan to bring the rsync’ed data on the destination servers up-to-date. Cine said Noah’s plan should work fine, but cautioned that if Noah was rolling out new Zimbra servers, instead of migrating his existing Zimbra servers, that the backup data from the old Zimbra servers cannot simply be rsync’ed in to the new Zimbra installation’s backup data location. In that instance, a Smart Scan on the new Zimbra servers (with an empty backup data location) would need to be run to create new backups from scratch. Cine also explained that while the real-time NG backup scanner is disabled, during which time the rsync of the backup data between servers runs, that should a mailbox receive a new message, and the message is deleted, then the deleted message will not be included in the Zimbra backups once the real-time NG backup feature is re-enabled with a Smart Scan from the Zimbra servers new location, since the message would no longer exist in Zimbra’s storage. Noah asked what happens if a message is moved from one mailbox folder to another folder while the real-time NG backup scanner is disabled. Cine said that in that case, the moved message will have its metadata updated in the backups to reflect the new folder location. Mark S. suggested using these rsync options:
On Source Server:
(as root user): usermod -a -G zimbra ubuntu
On Target Server:
rsync -avHpog --delete ubuntu@<source_server_ip>:/opt/zimbra/backup/zextras /import/zextras
If doing the rsync on Amazon Web Services, use the following to also get the private key:
rsync -avHpog -e 'ssh -i ~/zzkeys/zimbra-rsync-ssh' --delete