Product release information for SafeSend v4.6 BETA on September 17, 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! See Microsoft's .NET Core Documentation for full details.
Please note: 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
If you are using the SafeSend web add-in with IIS Server, the latest version of SafeSend v4.6 requires .NET Core 3.1 Hosting Bundle to be downloaded and installed. See full details on our beta test welcome page.
If your intent is to use both the COM add-in for Outlook for Windows and the Web add-in, set the PC platform to False from within Settings.json to avoid double prompts.
System Requirements
System Component | Minimum Requirement |
---|---|
SafeSend for Windows (COM add-in) |
Operating Systems
Email Clients
|
SafeSend for Web (Web add-in) |
.NET Core 3.1 Capable Web Server
Microsoft 365
Exchange 2019
|
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. |
SAFE-315 | Notifications from SafeSend are not consistent across platforms. For example: In Microsoft 365, it will show up as informational but Exchange will show the same notification as an error with different verbiage. Please see the attached screenshot. Error messages may include the following:
|
There is no known workaround at this time. This is a Microsoft bug. |