Release Notes for SafeSend - 2026 Nov 05

Written By Marissa Fegan (Super Administrator)

Updated at November 16th, 2026

Product release information for SafeSend manifest version 6.0.9.

This release applies to both SafeSend Cloud and SafeSend Self-Hosted.

 

What's New

Select which version of SafeSend your organization uses.  

Cloud

This release of SafeSend is the culmination of several iterations of stability and performance improvements. To get the client changes, deploy the latest manifest (see Special Instructions below).

Reliability and Stability

  • More reliable add-in loading: SafeSend loads faster and recovers on its own from brief network problems, so it no longer gets stuck on “loading” or “couldn’t connect”
  • Consistent task pane after updates: The task pane now displays correctly after an update
  • Fewer delays when sending: Emails are less likely to be held up when sending
  • Less typing lag on large replies (Outlook Classic): Typing is smoother on very large email threads

Scanning and Attachments

  • Faster DLP attachment scanning: Attachment scanning is significantly faster and more dependable under heavy load, including with large Excel files

Fixed in this Release

  •  Policies with many DLP rules: Fixed an issue where large policies could exceed a storage limit and stop the add-in from working
  • Scheduled send: Emails with a scheduled delivery time are no longer sent immediately after review
  • Scanning multiple files at once: Fixed a crash that could occur when several files of the same type were scanned at the same time
  • Danish translations: Improved Danish text, including the “Remove” tooltip in the task pane

Special Instructions

Updates to the SafeSend Cloud service are applied automatically for you. To receive the client changes, deploy the latest manifest:

  1. Download the latest manifest from Settings in the portal
  2. Deploy it through the Microsoft 365 admin center (Integrated apps)
  3. Assign it to individual users or top-level groups; Microsoft does not deliver add-ins to users in nested groups

Deployment through Integrated Apps can take up to 72 hours. If a user doesn’t see the update after 72 hours, restart Outlook (Classic) or refresh the page (Outlook on the web).

 
 

Self-Hosted

This release of SafeSend is the culmination of several iterations of stability and performance improvements. 

VIPRE Recommends

Staying on the latest version gives you the newest features, fixes, and performance improvements, and makes sure you’re on a fully supported release. We recommend 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.

 

 

Reliability and Stability

  • More reliable add-in loading: The add-in now fetches policy and session data in a single request and retries automatically if the connection drops; it loads faster, stays in sync, and no longer gets stuck on “loading” or “couldn’t connect” after a brief network problem
  • Support for large policies: Fixed an issue where policies with many DLP rules could exceed a storage limit and stop the add-in from working
  • No more blank task pane after updates: The add-in now loads from one file instead of several, and a caching issue has been fixed; the task pane no longer shows up blank or uses mismatched cached files after an update
  • Fewer delays when sending: Log reporting now has a timeout, so slow reporting is less likely to hold up a send
  • Less typing lag on large replies (Outlook Classic): On very large email threads, the add-in scans less often, which cuts down on delay while you type

Scanning and Attachments

  • Faster DLP attachment scanning: Attachment scanning is significantly faster and more dependable under heavy load, including with large Excel files

Fixed in this Release

  • Scheduled send: Emails with a scheduled delivery time are no longer sent immediately after review
  • Scanning multiple files at once: Fixed a crash that could occur when several files of the same type were scanned at the same time
  • Danish translations: Improved Danish text, including the “Remove” tooltip in the task pane
  • Diagnostics: Troubleshooting now uses the browser console; the log download in the task pane has been removed

Special Instructions

Upgrading

Update the container image and the package URL to the build for your version:

If your organization uses SafeSend Self-Hosted version…

Then you should deploy…

6.0.5

The 6.0.9 build

6.0.6

The 6.0.8 build

Anything older

A side-by-side deployment: deploy the new manifest alongside the old one, move users across, then remove the old one

Once the server is updated, update the manifest so that the client changes take effect. If you already use the 6.0.7 manifest, you do not need a new one.

 
 

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.

If you need more information on a specific issue, please share the ticket number (if applicable) when contacting our Technical Support team.

Issue Your Experience Workaround
SafeSend Cloud/Self-Hosted [Web Add-in]: SafeSend doesn’t load in Outlook Classic after a network delay If Outlook Classic starts before the network connection is fully established, or gets into a state where it blocks add-in web requests, SafeSend may not load.  There is currently no workaround. This is Microsoft platform behavior. We’re investigating, but there’s no complete fix yet.