VIPRE Security Knowledge

Release Notes for SafeSend - Dec 14, 2020

Super Administrator

Written By Marissa Fegan (Super Administrator)

Updated at August 15th, 2022

Table of Contents

What's NewSpecial InstructionsSystem RequirementsKnown Issues and Workarounds

Product release information for SafeSend v4.6 on December 14, 2020.

What's New

SafeSend v4.6 now includes a web add-in solution under the same license you've been using for your Windows Installer-based deployments. The new web add-in has basic send confirmation and supports OWA (Outlook Web Access), Outlook for Windows with Microsoft 365 or Exchange Server, and Outlook for Mac with Microsoft 365. The web add-in .zip file provided to you is a ready-made website that you can host in IIS (Internet Information Services) on any .NET 3.1 Core capable server, including Linux! And if that's not convenient enough, there's no installation required on end-user devices. See Microsoft's .NET Core Documentation for full details. 

VIPRE Recommends

While SafeSend v4.6 will work with any .NET CORE 3.1 capable web server, we recommend using IIS (Internet Information Services).

Please note, DLP (Data Loss Prevention) is not currently available with the Web Add-in but is scheduled for a future release.

We've also simplified domain-based licensing. Those who frequently change 'Safe' domains no longer need to update their license to accommodate! One important thing to consider is that the license is now tied to the sending domain so you may still need to license multiple domains if you have multiple domains that you send email from.

Special Instructions

 Click the arrow below for details on how to upgrade to the latest version of SafeSend.

Upgrade from SafeSend v4.5 to v4.6


When using the PC add-in:

  1. Create a custom MSI installer 
    • If you require assistance, visit our Onboarding guide for details on how to customize SafeSend
  2. Choose a few of your existing endpoints and run the installer
    • Existing license and settings will be carried over automatically

When using the Web add-in:

  1. Deploy a new instance of your chosen web server using your existing license
  2. Choose a few of your users and enable the web add-in
 

System Requirements

System Component Minimum Requirement
SafeSend PC Add-in

Operating Systems

  • Windows 10, 8.1, 8, 7
  • Windows Server 2016, 2012, 2008 R2

Email Clients

  • Outlook 2019, 2016, 2013, 2010
    • Both 32-bit and 64-bit versions
.NET Framework 4.7, 4.6, 4.5, 4.0
  • Microsoft .NET 4.0 or later is required to be installed but all newer versions of Windows already have this included
  • Please note that .NET 4.0 Client Profile is not sufficient to install SafeSend and that the full version of .NET 4.0 or later is required
SafeSend Web Add-in

.NET Core 3.1 Capable Web Server

  • Hosting Bundle is required when using IIS Server (Recommended)

Microsoft 365

  • Email Clients
    • Outlook for Mac v16.30+
    • Outlook for Windows 2019, 2016, 2013
      • Both 32-bit and 64-bit versions
  • Browsers for OWA
    • Mozilla Firefox
    • Google Chrome
    • Microsoft Edge
    • Microsoft Edge Chromium
    • Internet Explorer 11
    • Safari

Exchange 2019

  • Email Clients
    • Outlook for Windows 2019, 2016, 2013
      • Both 32-bit and 64-bit versions
  • Browsers for OWA
    • Mozilla Firefox
    • Google Chrome
    • Microsoft Edge
    • Microsoft Edge Chromium
    • Internet Explorer 11


Platforms Tested

PC Add-in

Exchange 2019 cumulative update 2 15.2.397.3
  • Outlook 2019 v16.0.13029.20344
  • Outlook 2016 v16.0.13127.20408

Web Add-in

Exchange 2019 cumulative update 2 15.2.397.3
  • Email Clients
    • Outlook 2019 v16.0.13029.20344
    • Outlook 2016 v16.0.13127.20408
  • OWA Clients/Browsers
    • Google Chrome v85.0.4183.102
    • Mozilla Firefox v80.0.1
    • Microsoft Edge v44.48362.449.0
    • Microsoft Edge Chromium v85.0.564.51
    • Internet Explorer 11 v11.1082.18362.0
Microsoft 365
  • Email Clients
    • Outlook 2019 v16.0.13029.20344
    • Outlook 2016 v16.0.13127.20408
    • Outlook for Mac v16.37
  • OWA Clients/Browsers
    • Google Chrome v85.0.4183.102
    • Mozilla Firefox v80.0.1
    • Safari (macOS) v13.1.2 - 14609.3.5.1.5
    • Microsoft Edge v44.48362.449.0
    • Microsoft Edge Chromium v85.0.564.51
    • Internet Explorer 11 v11.1082.18362.0


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 issue ID (if applicable) when contacting our Technical Support team.

Bugs Fixed in this Release

  • [SAFE-222] - Duplicate draft saved to OWA calendar when creating a new event
  • [SAFE-311] - Sender address missing in some Gmail accounts


Known Bugs

Ticket Number Description Workaround
SAFE-302 When using OWA in Safari and Exchange Server, SafeSend dialog doesn't display

This is the result of a known Microsoft bug. For details, visit: https://github.com/OfficeDev/office-js/issues/1057 		You can use other browsers that work in macOS such as Firefox, Chrome, Opera, etc. With this option, it's recommended to block access to Safari to avoid the known issue. 
SAFE-314 When using Mac Outlook and Exchange Server, SafeSend dialog doesn't display

This is the result of a known Microsoft bug. For details, visit: https://github.com/OfficeDev/office-js/issues/1057 		There is no known workaround at this time.

Related Articles

Release Notes for SafeSend BETA - Sept 17, 2020

Update Table of Contents What's New Special Instructions System Requirements Know...

Release Notes for SafeSend - Jan 30, 2020

Product release information for SafeSend v4.5 released by VIPRE on January 30, 20...