Introduction

This document describes the changes introduced in this release of the Zivver Office Plugin.

Downloads

To download the Zivver Office plugin, please visit our release notes table.

Release highlights

Improvements

We have rebuilt this version of the Zivver Office Plugin from the ground up, focusing on an improved user experience and an enhanced performance.

The most noticeable improvements and changes are listed below.

• An increased performance speed when working with Outlook in Online Mode and in Cached Mode.
• Attachments are added faster when working with Outlook in Online Mode and in Cached Mode.
• The CPU load has been reduced by approximately 80% and the amount of network traffic has been reduced.
• An updated branding and an improved design.
• Support for integration with Microsoft Purview.
• Outlook 2013 is no longer supported in this version of the Zivver Office Plugin.

Bug fixes

• IM-74 / IM-317 - If an organization has disabled the verification email method, it is not possible to send an email using the Send now with lowest security level button.
• IM-149 - When ‘SMS Code’ is set as verification method, some users may intermittently be unable to add the country code and / or mobile number via the Verification Methods window.
• IM-277 - When attaching a folder to a secure message via the Zivver attachment button and saving the message as a draft, the attached folder is not sent to the recipient when sending the message.
• IM-359 - It is not possible to download just the Proof of Delivery report separately.
• IM-367 - When clicking on download all from within a Zivver message, the message itself is not downloaded.
• IM-369 - Even though the “verification method email” is disabled from the organisation’s settings, the organisation’s settings are not prioritized by the Zivver Office Plugin and it triggers an unusual behaviour when sending an email.
• IM-390 - Even though the user is logged in to Zivver, the Zivver ribbon still displays the login option.
• IM-395 - After closing one or more exported Zivver messages, Outlook needs to be restarted before exported Zivver messages can be opened again.
• IM-558 - If the user tries to correct a misspelled word, the Zivver Office Plugin will cause Outlook to crash.
• IM-619 - If the recipients:trustedDomains business rule is set to blocking, it is impossible to send messages to trusted domains both with and without Zivver.
• IM-634 - If the fully qualified file name of an attachment exceeds 259 characters or if the directory name exceeds 247 characters, the Zivver Office Plugin will not save the attachment.
• IM-686 - When switching from an inline draft message to any other message, the inline draft message is emptied.
• IM-696 - If a user’s Active Directory password has been changed, Outlook may afterwards fail to start up.
• IM-712 - If the HighlyConfidentialDomain setting is ON and Zivver is turned on manually, any attachment added through the Outlook attachment button will NOT be processed by Zivver.
• IM-781 - If Plugin Assisted Mail Submission (PAMS) is used in combination with iManage client-side filing, sent messages will not be saved in iManage.
• IM-808 - If a business rule triggers on an attachment and the option “delete attachment” is pressed, the attachment will still be processed by Zivver.
• IM-960 - After Zivver has been turned on by a business rule and then turned off manually, Zivver will continuously be turned on again.
• ENG-912 - Users may intermittently become stuck on the “checking message” screen in the Zivver Office Plugin after sending a message.
• ENG-6285 - Inline signatures are occasionally displayed as plain text when a Zivver message is forwarded or replied to.
• ENG-6439 - Flags and Categories that have been assigned to a message only become visible after switching to another message and back.
• ENG-6440 - When a message is opened and closed in pop-out mode, you are prompted to save your changes regardless of whether you made any changes or not.
• ENG-6441 - Changes to revocation settings from the admin panel are not reflected in the plugin instantly.
• ENG-6967 - The BCC business rule is not activated when adding recipients.
• ENG-7312 - Inline images are excluded from signatures in messages sent using Plugin Assisted Mail Submission (PAMS).
• ENG-7315 - Directly after sending a reply to a non-Zivver message, a new draft is opened up where the Zivver Office Plugin’s bar is not visible.
• ENG-7318 - Directly after sending a message that was previously saved as a draft, a new draft is opened up where the Zivver Office Plugin’s bar is not visible.
• ENG-7467 - It is impossible to set categories or flags on messages from certain mailboxes.
• ENG-8146 - Writing or replying to messages that contain large amounts of HTML content may be slow.
• ENG-8265 - Changes made to the subject line of a draft will be ignored when sending a message based on that draft.
• ENG-8303 - After exiting the revocation settings for a Zivver message without saving, the default revocation settings will still be overwritten.
• ENG-8317 - When using the HighlyConfidentialDomains registry key, attachments will be removed after disabling Zivver when forwarding or replying to NTA7516 compliant messages.
• ENG-8318 - When using the HighlyConfidentialDomains registry key, any attachments added through the Outlook attachment button will be removed after disabling Zivver.
• ENG-8840 - Security improvement
• ENG-8862 - The Zivver Office Plugin may fire an exception “Object reference not set to an instance of an object”
• ENG-8998 - The Zivver Office Plugin may fire an exception “Object reference not set to an instance of an object”
• ENG-9743 - The default logging level is set to Trace which could lead to increased disk space usage.

Known issues

• IM-220 - When using an Outlook template for Zivver messages, the font switches size from regular to large upon entering text in the template.
• IM-785 - The Zivver Office Plugin does not recognize an attachment that the user added with Simple MAPI.
  Workaround: Use the Outlook attachment button to add an attachment, or use the Zivver attachment button for large attachments.
• IM-898 - The Zivver Office Plugin’s bar does not scale up, making the text difficult to read.
• IM-933 - Outlook crashes after having created any of the registry keys below. In the registry, under ‘HKEY_CURRENT_USER\SOFTWARE\Zivver\OfficePlugin\Settings’ , the ‘REG_SZ’ entry was created with the name ‘RemoteLoggingLevel’ and the value ‘info’. In the registry, under ‘HKEY_CURRENT_USER\SOFTWARE\Zivver\OfficePlugin\Settings’ , the ‘REG_SZ’ entry was created with the name ‘FileLoggingLevel’ and the value ‘info’.
  Workaround: For any of the registry keys that was created, change the value ‘info’ to ‘information’.
  Workaround: Deleting any of the registry keys above will have the Zivver Office Plugin default to the value “information”.
• IM-939 - When using an MSG file to send Zivver messages, any attachments that are added to the MSG file are not added to the sent Zivver message.
  Workaround: Add any attachments manually to the Zivver message.
• ENG-5515 - Sending an attachment by right-clicking and selecting the Send to Mail Recipient option does not work when Outlook has not been started already.
  Workaround: Make sure Outlook has already been started.
  Workaround: Use the Outlook attachment button to add an attachment, or use the Zivver attachment button for large attachments.
• ENG-6373 - Updating earlier versions of the Zivver Office Plugin to v6.x of the Zivver Office Plugin “for everyone” is impossible due to an error “The installer has insufficient privileges to modify this file: C:\Program Files (x86)\Zivver B.V\Zivver Office Plugin\adxloader.dll.manifest.”
  Workaround: In the registry, under ‘HKEY_CURRENT_USER\SOFTWARE\Zivver B.V.\Zivver Office Plugin’ , create the ‘REG_SZ’ entry with the name ‘InstallScope’ and the value ‘1’.
  Workaround: Uninstall and reinstall the Zivver Office Plugin.
• ENG-7271 - Zivver attachments that have been added to an existing draft message are not removed when discarding the changes to that draft message.
  Workaround: Manually remove the Zivver attachment before closing the draft.
• ENG-7848 - The formatting of HTML signatures may be incorrect for Zivver messages that are sent using Plugin Assisted Mail Submission (PAMS) and that are received by Zivver users as BCC.
• ENG-8047 - Any human error business rules can only be closed after editing the subject or the body of the message.
• ENG-8065 - When the Zivver message is already in the process of being sent, clicking on the “Change” button will not prevent the Zivver message from being sent.
  Workaround: Clicking on either the “Cancel” button or the close window button will prevent the Zivver message from being sent.
• ENG-8158 - Logging out of Zivver while writing a Zivver message and then logging back in after having clicked on the send button will result in the message being sent insecurely.
  Workaround - Do not log out of Zivver while writing a Zivver message.
• ENG-8274 - When using Outlook with Google Workspace, Zivver messages sent to a shared mailbox may not be readable in Outlook.
  Workaround - Use the Chrome Extension or the WebApp.
• ENG-9304 - When using v6.1.x of the Zivver Office Plugin, starting Outlook may take longer than when using earlier versions of the Zivver Office Plugin.
• ENG-9844 - It is impossible to send a Zivver message with an attachment that contains  brackets in the file name if the attachment was added using the Outlook attachment button.
• ENG-10425 - When using v6.1.x / v6.2.x of the Zivver Office Plugin, closing Outlook may take longer than when using earlier versions of the Zivver Office Plugin.