Release Notes for SafeSend - 2025 Feb 26

Written By Marissa Fegan (Super Administrator)

Updated at March 1st, 2025

Table of Contents

What's New VIPRE Recommends Fixed in this Release Special Instructions - Upgrading to SafeSend 5.5 Known Issues and Workarounds The following SafeSend Web Add-in issues are due to Microsoft Outlook's inherent behaviors and are not considered SafeSend bugs. There are no workarounds for these issues. Known Issues in previous versions of the SafeSend Web Add-in: Related Documentation:

Product release information for SafeSend version 5.5, released on 2025 February 26.

What's New

Download the latest version of SafeSend

SafeSend Web Add-in has been updated with several key improvements:

Web Add-in

Enhanced Security: Addition of the Strict-Transport-Security header (HSTS) to enforce SSL in your browser
Functionality: SafeSend now works in private browsing mode
Compatibility: SafeSend now supports .NET 8.0, ‘New’ Outlook, and Government Community Cloud (GCC) 365
- SafeSend no longer supports .NET 6.0
Performance: Client-side processing has been improved by shifting business logic to the client and optimizing callbacks. This results in faster actions, better responsiveness, and a more reliable experience, especially in poor network conditions.
Support for single-tenant application registration
Logging: Log files are now enabled by default
Authentication: SafeSend's authentication has been updated to align with the latest Microsoft security requirements, including automatic, silent refresh of authentication tokens

PC Add-in

Support for font size customization in messages and policy strings has been added
Authentication: SafeSend's authentication has been updated to align with the latest Microsoft security requirements, including automatic, silent refresh of authentication tokens
Logging: Log files are now enabled by default

VIPRE Recommends

Keeping all software in your environment as up-to-date as possible is critical. 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.

You can check the current status of older product versions on the VIPRE Product Lifecycle Matrix to learn when support for specific product versions may end.

SafeSend Web Add-in Deployment Guide

Fixed in this Release

Data Loss Prevention (DLP): Resolved an issue with DLP detection when using word boundaries within spreadsheet cells
PC Add-in: Fixed a problem where store settings were not correctly saving values that began with the "#" character
Web Add-in: Corrected an issue that could cause Outlook to become stuck while sending a message

Special Instructions - Upgrading to SafeSend 5.5

We strongly recommend a parallel upgrade process to ensure a smooth transition and minimize potential disruptions. This parallel upgrade method avoids the complications associated with upgrading a .NET 6.0 deployment directly. Our recommended approach involves setting up a brand new .NET 8.0 server (or Azure Web App) with SafeSend 5.5. This new server should be thoroughly tested via side loading or a limited pilot deployment. Once testing is complete, update your existing deployment with a new manifest. After approximately 24 hours, all clients should have applied the new manifest, allowing you to decommission the old server.

VIPRE SafeSend System Requirements

Known Issues and Workarounds

This section highlights issues identified at the time of release. Some are bugs that we are actively addressing in future updates, while others may be related to third-party software. We've provided workarounds to help you manage these situations effectively wherever possible.

The following SafeSend Web Add-in issues are due to Microsoft Outlook's inherent behaviors and are not considered SafeSend bugs. There are no workarounds for these issues.

Attachment Size Discrepancy:
- When an attachment's size is displayed in bytes within Microsoft Outlook, the SafeSend confirmation dialog box may not accurately reflect this size. This is due to how Microsoft Outlook handles byte-sized attachments.
Distribution Lists in Calendar Events:
- When editing a calendar event or using "Reply All" on a calendar event in Microsoft Outlook, distribution lists are not displayed in the SafeSend confirmation dialog box. This is due to how Microsoft Outlook handles distribution lists in calendar events.
Embedded Images in Outlook for Windows:
- When the "SS_MarkEmbeddedImagesAsAttachments" setting is enabled, embedded images are not displayed in Outlook for Windows. This is due to how Microsoft Outlook handles embedded images with this setting.
Nested Message Scanning:
- When replying to an email from the Outlook side reading pane, the text of a nested message is not scanned by the DLP add-on. This is due to the way Outlook presents nested messages in the reading pane.

Known Issues in previous versions of the SafeSend Web Add-in:

Calendar Event Creation on Cancel:
- When sending an Outlook event in Microsoft 365 and then canceling from the SafeSend confirmation dialog box, an event is created on the organizer's calendar.
- Workaround: Manually cancel the Outlook event.
Embedded Image Disappearance:
- Adding a new embedded image when using "Reply," "Reply All," or "Forward" causes previously embedded images to disappear from the SafeSend confirmation dialog box.
- Workaround: Confirm that the drafted email is correct and disregard the list in the confirmation dialog box.

VIPRE Security Knowledge