[Users] March 24, 2020 Zeta Alliance Conference Call Summary

[Randy Leiker]

Hello Zeta Alliance Community, 

Here is a summary of last week’s conference call (sorry it is a week late). 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 | https://www.freeconferencecall.com/wall/zetalliance ] 
    * Each week’s call agenda can be found at: [ https://docs.google.com/document/d/1uUUDJpwp2CAylU6lxtbEdVcUX_qSbciyes6gLTWw2fY/edit | https://docs.google.com/document/d/1uUUDJpwp2CAylU6lxtbEdVcUX_qSbciyes6gLTWw2fY/edit ] 
    * A copy of each week’s summary is also posted to the Zimbra Forum: 
        * January 2020: [ https://forums.zimbra.org/viewtopic.php?f=9&t=67572 | https://forums.zimbra.org/viewtopic.php?f=9&t=67572 ] 
        * February 2020: [ https://forums.zimbra.org/viewtopic.php?f=9&t=67726 | https://forums.zimbra.org/viewtopic.php?f=9&t=67726 ] 
        * March 2020: [ http://forums.zimbra.com/viewtopic.php?f=9&t=67855 | http://forums.zimbra.com/viewtopic.php?f=9&t=67855 ] 
    * Constructive feedback on these call summaries is always welcome. 

March 24, 2020 Conference Call Summary 

Zimbra Connect Bugs 
Randy L. reported discovering 4 bugs affecting Zimbra Connect in Zimbra 8.8.15 Patch 8. A brief summary of each bug follows. 

Bug # 1: 
>From the Zimbra Web Client, click the Connect tab, then start a new instant meeting. Invite at least 2 attendees, one should be an internal user on the same Zimbra system, and the other attendee should be on an external mail server. The external attendee correctly receives an email invite with a link to join the meeting, while the internal Zimbra user does not receive an emailed invite. 

Bug # 2: 
>From the Zimbra Web Client, click the Connect tab, then start a new instant meeting. Invite an attendee on an external mail server. When the attendee receives the emailed invite, they click on the link to join the meeting, enter their name, but enter a different email address than the meeting organizer entered for the attendee. The attendee sees a mostly blank white page with no indication of what they did wrong, while the meeting organizer and other meeting attendees see the attendee’s name appear in the list of active participants in the meeting. 

Bug # 3: 
The Zimbra Connect documentation (https://zimbra.github.io/adminguide/latest/#_browser_compatibility) indicates that the Quick Access sidebar in the Zimbra Web Client, where instant messages appear for a user, is compatible with Microsoft Edge. If a mailbox user receives a notification that they have a new instant message and clicks on it from the Quick Access bar, the entire page header, including the Web Client navigation tabs and search bar disappear, leaving just the body of the page. The only way for the user to recover is to click the Refresh or Back buttons in their browser. Cine said that this is likely a documentation error, as this is expected to work in the most recent versions of Edge, which were changed by Microsoft from the EdgeHTML engine to a Chromium engine (https://en.wikipedia.org/wiki/Microsoft_Edge#Release_history). 

Bug # 4: 
>From the Zimbra Web Client, click the Connect tab, invite attendees, then start a new instant meeting. After the meeting has started, click the “i” (information icon) appearing at the top of the instant messaging window to display the meeting’s properties. Next, click the “Add participants” link to invite others to the meeting. Add the email address of a user on an external mail server. When the user receives the email invite, clicks the Join link, then enters their name and correct email address, the user sees a mostly blank white page, while the meeting organizer and other meeting attendees see the new attendee’s name appear in the list of active meeting attendees. 

Randy L. reported that he could also confirm encountering a 5th bug in Zimbra Connect that Mark S. reported during an earlier call where attaching a file to send to participants in an Instant Meeting (video call) or an instant messaging conversation does not make the file available for the participants in the meeting or conversation. When a file is shared during a meeting/conversation, it is expected to appear in the “Connect sent files” within the Drive tab of the Zimbra Web Client (https://zimbra.github.io/adminguide/latest/#_file_sharing). Cine said that this feature requires the Zimbra Drive Zimlet to be enabled for a Zimbra Connect user. Mark and Randy both confirmed that they were able to produce this bug with the Zimbra Drive Zimlet enabled. 

Troubleshooting Failed Mailbox Moves 
Mark S. reported that he has a few mailbox moves between Zimbra mailbox servers failing for an unknown reason when using the “zxsuite doMailboxMove” command and asked everyone on the call for suggestions. He also asked if the deprecated zmmailboxmove command could be used as a temporary workaround. Cine suggested first performing a clean-up of the failed mailbox moves using the “doRemove” feature of the zxsuite command line tool, followed by splitting the “doMailboxMove” command in to 3 separate stages (move blobs, move backups, move mailbox) to determine which of the 3 stages is failing for the affected mailboxes. Cine also suggested running an integrity scan on the Zimbra MariaDB database, in addition to a scan for orphaned/unexpected blobs on the mailbox disk volumes. 

New Zimbra Wiki Article For Setting Up a STUN/TURN Server 
John H. provided a link to a draft version of a new Zimbra Wiki article pertaining to setting up a STUN/TURN server for use with Zimbra Connect and requested suggestions from those on the call for additions/revisions to the article due to numerous recent requests for this information by Zimbra customers. The new Wiki article is now published at: [ https://wiki.zimbra.com/wiki/TURN_STUN_Guide | https://wiki.zimbra.com/wiki/TURN_STUN_Guide ] 


Randy Leiker ( randy at skywaynetworks.com ) 
Skyway Networks, LLC 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.zetalliance.org/pipermail/users_lists.zetalliance.org/attachments/20200331/fcee38d9/attachment.html>