Product release information for SafeSend v5.3, released on August 31, 2023.
What's New
Choose your add-in type below to learn more about the most recent version of SafeSend.
Download the latest version of SafeSend
PC Add-in
We have found that our SafeSend users want more control over what events trigger the SafeSend confirmation dialog box in order to limit popups to more genuinely risky situations. To that end, we have added the following new settings:
- PopupForExternalRecipients - This is the current default behavior
- PopupForExternalAttachments - Enable the confirmation prompt when sending attachments to anyone
- PopupForMultipleDomains - Enable the confirmation prompt when sending internally and externally simultaneously
- PopupForMultipleExternalDomains - Enable the confirmation prompt when sending to multiple external domains
- PopupForMatchingRecipientsRegex - Enabled when a valid regex search string is entered; displays the SafeSend popup when a recipient email is matched
-
StringNotifyMatchingRecipientsRegexMatched - Additional text to display when PopupForMatchingRecipientsRegex matches, this string accept html tags
- For example: This is formatted text<br>new line<br><b><i><a href="Home ">Hyperlink</a> </i></b> <color=128,50,50><b>Color</b></color>
- PopupForReplyToRecipients - Enable this setting to display non-default ReplyTo recipients in the SafeSend confirmation box
Important
The following existing settings will be gradually deprecated in favor of the new settings listed above:
- SS_OnlyPopupForAttachments
- SS_OnlyPopupForAttachmentsOrDLPMatch
- SS_OnlyPopupForDLPMatch
- SS_OnlyPopupForMultipleExternalDomains
It's important to note that for now, SafeSend will continue to read these settings when none of the new settings above have been defined and will eventually use them to set the new settings in an equivalent manner. We recommend going through the new settings above and setting them as desired to ensure SafeSend continues working appropriately for your organization's needs.
For additional details on SafeSend PC Add-in settings, visit the PC Add-in Settings Reference guide.
Other changes in the SafeSend PC Add-in include:
- The ability to perform DLP (data loss prevention) scans of Citrix ShareFile™ attachments
- The option to have the Select All option remain at the top of the Recipients/Attachments list or move to the bottom of the list; this new setting is “SelectAllPositionOnBottom”
Web Add-in
We have found that our SafeSend Web Add-in users want more control over what events trigger the SafeSend confirmation dialog box in order to limit popups to more genuinely risky situations. To that end, we have added the following new settings:
- PopupForExternalRecipients - This is the current default behavior
- PopupForExternalAttachments - Enable the confirmation prompt when sending attachments to anyone
- PopupForMultipleDomains - Enable the confirmation prompt when sending internally and externally simultaneously
- PopupForMultipleExternalDomains - Enable the confirmation prompt when sending to multiple external domains
- PopupForMatchingRecipientsRegex - Enabled when a valid regex search string is entered; displays the SafeSend popup when a recipient email is matched
-
StringNotifyMatchingRecipientsRegexMatched - Additional text to display when PopupForMatchingRecipientsRegex matches, this string accept html tags
- For example: This is formatted text<br>new line<br><b><i><a href="Home ">Hyperlink</a> </i></b> <color=128,50,50><b>Color</b></color>
Important
The following existing settings will be gradually deprecated in favor of the new settings listed above:
- SS_OnlyPopupForAttachments
- SS_OnlyPopupForAttachmentsOrDLPMatch
- SS_OnlyPopupForDLPMatch
- SS_OnlyPopupForMultipleExternalDomains
It's important to note that for now, SafeSend will continue to read these settings when none of the new settings above have been defined and will eventually use them to set the new settings in an equivalent manner. We recommend going through the new settings above and setting them as desired to ensure SafeSend continues working appropriately for your organization's needs.
For additional details on SafeSend Web Add-in settings, visit the Web Add-in Settings Reference guide.
Other changes in the SafeSend Web Add-in include:
- The added ability to download client-side logs from within Microsoft Outlook for Windows
- Refer to Web Add-in: Debug Mode for details
- Support for using certificates when configuring the SafeSend Web Add-in with the Microsoft Graph API
- Refer to Microsoft Graph API Setup for SafeSend for details on setting up Graph API
- The user interface was updated and now allows the option to move Select All to the bottom of the list of recipients and attachments; this new setting is “SelectAllPositionOnBottom”
VIPRE Recommends
It's critical to keep all software in your environment as up-to-date as possible. New software releases often fix issues with older product versions that, unless addressed, could leave you vulnerable. As such, VIPRE recommends updating to the most recent version as soon as possible.
Check the current status of older product versions on the VIPRE Product Lifecycle Matrix to learn when support for specific product versions may end.
Special Instructions
Updating SafeSend
Use these instructions to help you update to the latest version of SafeSend.
Download the latest version of SafeSend
PC Add-in
Important
When upgrading from version 4.4, your admin password and customized logo will need to be reset.
- Download the latest version of the SafeSend PC add-in above
- Customize as desired and store settings by creating a custom MSI installer
- Refer to Related Articles for direct links to other processes pertinent to the one detailed in this article.
- Choose the desired existing endpoints and run the installer or deploy via GPO over your existing, older version of SafeSend
- Existing licenses and settings will be carried over automatically
The latest version of SafeSend PC add-in is now deployed.
Web Add-in
The instructions below were written as a general guide for the .NET CORE 6.0 capable web server of your choice.
- Create a new server with the latest version of SafeSend in the host of your choice
- Copy settings to the new version:
- If using Azure:
- On the source/old SafeSend App Service, click Configuration->Application Settings->Advanced Edit
- Select all json text and copy
- On the destination/new SafeSend App Service, click Configuration->Application Settings->Advanced Edit
- Select all json text and paste the previously copied text in its place
- Click OK
- Click Save
- If you've configured using settings.json:
- Open your existing settings.json file and open the newest version of the settings.json file for comparison
- You can open both in any text editor, placing the two documents side-by-side, or...
- You can open both files in a text compare tool, which will highlight the differences
- Copy your existing configuration over to the new settings.json, setting by setting
- This may seem tedious, but it allows you to keep your existing configuration without losing all of the new settings/features within the updated settings.json file
- Open your existing settings.json file and open the newest version of the settings.json file for comparison
- If using Azure:
- Side load or deploy to your test users, then verify the latest version of SafeSend is working by navigating to <yourWebURLhere>/manifest
- Make sure that you remove the old manifest for the test users first, otherwise, you could get double-prompted
- To enable debug mode within your web client, you'll need to use /manifestlog instead; visit Web Add-in: Debug Mode for full details
- Once you're satisfied with your test deployment, remove the previous version of Safesend for everyone else
- If you’re using Exchange Server, deploy the latest version as desired
-
If you’re using Exchange Online, update your existing web add-in manifest.xml with the manifest file you tested with above in Step 4
- Please note, if you get an ID mismatch error, update the ID tag in the manifest.xml file before attempting to upgrade SafeSend again
- Once SafeSend is updated in Exchange Online, it could take up to 12 hours to propagate; the logs of the old version should be checked before shutting down the server to verify that there are no clients still using the old version
The SafeSend Web add-in has successfully been updated.
System Requirements
Visit the VIPRE SafeSend System Requirements page for the latest system requirements for both the Web and PC add-ins.
Bugs Fixed in this Release
- SAFE-1293 (PC Add-in): When sending an email, clicking Send caused the Confirm External Recipients window to close and go back to the email editor window
- SAFE-1304 (Web Add-in): Email header was not included in the email when the TriggerEncryptionXHeader setting was configured
Known Issues and Workarounds
This section lists issues that are known at the time of release. In some cases, these are bugs that we are working to resolve with a subsequent release. Other items may be due to causes outside of our control, such as bugs with other vendors' software. In all cases, we have tried to provide a workaround for you to consider should you experience an issue.
If you have questions about a specific issue, please provide the ticket number (if applicable) when contacting our Technical Support team.
| Ticket | Description |
|---|---|
| SAFE-1408 (Web Add-in) | Embedded images are not displayed in Outlook for Windows when the SS_MarkEmbeddedImagesAsAttachments setting is enabled |
Known Issues from Previous Versions
| Ticket Number | Description |
|---|---|
| SAFE-1287 (Web Add-in) | When replying to an email from the side reading pane in Outlook, the text of a nested message will not be scanned by the DLP add-on Workaround: Open the email and reply in a maximized/expanded window; this will allow it to be scanned |
| SAFE-1147 (PC and Web Add-in) | Confirmation window positioned incorrectly Workaround: Ensure all of your monitors are set to the same scale |
| SAFE-808 (Web Add-in) | When StringMainMessage in Exchange/OWA is too long, it can take up the whole SafeSend confirmation dialog box and sometimes cause the page to be unresponsive Workaround: Keep your string as short as possible; it’s recommended to not use more than 140 characters (including spaces); it’s also important to ensure your browser window is maximized. |
| SAFE-757 (Web Add-in) | An event is created on the organizer's calendar when clicking Send on the Outlook event in Microsoft365, then clicking Cancel from the SafeSend confirmation dialog box. Workaround: Manually cancel the Outlook event. |
| SAFE-929 |
Adding a new embedded image when using Reply, Reply All, or Forward causes any previously embedded image to disappear from the confirmation dialog box Workaround: Confirm that your Drafted email is what you want to send and ignore the list in the confirmation dialog box |