Introduction

This document describes the changes introduced in Zivver Office Plugin release v5.7.9.

Release highlights

This release contains two key bug fixes relating to issues when installing the latest version of the Zivver Office Plugin

New or improved functionality

• There are no new features as part of this release. v5.7.9 contains bug fixes only.

Bug fixes

• IM-349 - Fixed the issue where the Zivver Office Plugin was not available in Outlook after installation, when a previous version was updated.
• IM-146 - MSI installer now checks for correct version of .NET framework (v4.8) on installation.

Known issues

Note: Known issues list has not changed since the previous official version (v5.7.5)

Below is a list of known issues that exist within this version. Where available, workarounds are described.

1. Issue: IM-302 - When sending a message to an internal recipient that doesn’t have a Zivver account, sometimes the message is not send after hitting the Send button.
   
   This situation might occur during a pilot test when internal recipients do not always have a Zivver account yet.
   Workaround: Clicking ‘send’ twice will successfully send the message.
2. Issue: IM-117 - Logging in and out of a Zivver account multiple times in a row, might cause a Single Sign-On (SSO) login to hang.
   Workaround: Restart Microsoft Outlook.
3. Issue: ENG-912 - Users may intermittently become stuck on the “checking message” screen in the Zivver Office Plugin after sending a message.
   Workaround: Restart Microsoft Outlook then re-send the message.
4. Issue: IM-92 - Users see the error unable to move the items. An unknown error has occurred when they try to move messages to and from a functional-account folder.
   Workaround: Deactivate ‘Save Zivver Messages Unencrypted’ to prevent the error from happening.
5. Issue: IM-103 - The Zivver Office Plugin may not be visible, but active according to Outlook for some customers which use Plugin Assisted Mail Submission (PAMS).
6. Issue: IM-104 - Customers using functional accounts in Online mode may find Zivver messages are no longer visible after being moved to a sub-folder.
   Workaround: Messages can be found in and moved from the ‘Synchronization’ > ‘Conflicts’ folder to the desired folder.
7. Issue: IM-277 - When attaching a folder to a secure message via the Zivver clip and saving the message as a draft, the folder is not sent to the recipient when sending the message.
   Workaround: Add the folder to a secure message via the ‘Attach File’ option on the Outlook ribbon .
   Note: When using this workaround, you can’t send any attachment that is larger than is allowed by your mail server. As adding an attachment via the Outlook “Attach File” button is limited in size, even though Zivver is turned on for that message.
8. Issue: IM-295 - When a user manually selects a folder in the plugin settings to save sent messages, sent item copies are not saved in this folder.
   Workaround: The message can be retrieved by opening the Zivver WebApp.
9. Issue: IM-149 - When ‘SMS Code’ is set as verification method, some users may intermittently be unable to add the country code/mobile number via the Verification Methods window.
   Workaround: Restart Microsoft Outlook and retry.
10. Issue: IM-220 - When using an Outlook template for Zivver messages, font switches size from regular to large upon entering text in the template.
11. Issue: IM-404 - If the Outlook Zivver Setting ‘Activate “Secure mailing” if BR recommends it’ is turned on, ‘Activate “Secure mailing” for every message’ is set to off, and a business rule triggers a warning - users may experience a delay when composing a message.
    Workaround: Toggle the setting ‘”Activate ‘Secure Mailing’ for every message”’ on. Please note this will send ALL mail via Zivver - if needed, customers can exclude specific domains from this by using the ‘HighlyConfidentialDomains’ registry key which is explained here: https://docs.zivver.com/en/admin/officeplugin/exempt-domains-from-business-rule-checks.html
12. Issue: IM-377 - After updating the Zivver Office Plug-in, in a rare case it could ask to sign into old shared inboxes that are not present in Outlook anymore.
    Workaround: Rename the Windows folder %AppData%\Roaming\Zivver\OfficePlugin\ of the affected user so that the Plug-in will create a new one. This will refresh the account data and limit sign-in prompts to existing inboxes in Outlook.
13. Issue: IM-785 - The Zivver Office Plugin does not recognize an attachment that the user added with Simple MAPI.