This beta is no longer active.
Welcome and thank you for participating in the VIPRE SafeSend v4.6 beta program! We're excited to have you get to know our add-ins for both Windows and the web. As a beta-tester, you're helping us make sure the latest version of SafeSend works as intended.
Still trying to decide if participating in the SafeSend v4.6 beta program is right for you? Maybe we can help you decide:
- Do you require support for non-Windows-based Operating Systems like macOS?
- Do you require support for OWA?
- Do you require cross-platform support?
If you answered yes to any of these questions, then you may benefit from participating in our program.
What's New
Here is where you'll find some product information and special instructions for SafeSend v4.6. For full details including known bugs, refer to Related Articles for our BETA Release Notes.
So, what exactly is new? Let us lay it out:
- We simplified licensing to be sender-domain-based for those who frequently change their 'safe' domains
- We created a brand new Web add-in in addition to our existing COM add-in; features include:
- Supports OWA, Outlook for Windows, Outlook for Mac
- Mac is limited to Outlook in Microsoft 365
- Basic Sent confirmation
- Can be hosted on any .NET CORE 3.1 capable web server
- Supports OWA, Outlook for Windows, Outlook for Mac
VIPRE Recommends
While SafeSend v4.6 will work with any .NET CORE 3.1 capable web server, we recommend using IIS (Internet Information Services).
COM Add-in vs Web Add-in
Which add-in will work best for your organization? Would you benefit from using both? What's the difference between the different add-ins? For the most part, both add-ins perform the same function but they do differ in some significant ways.
The COM (Component Object Model) add-in version of SafeSend only works in Windows. Refer to Related Articles to view those system requirements and a list of features from the previous release of our COM add-in version of SafeSend.
The Web add-in version of SafeSend expands support to non-Windows Operating Systems by working with both Microsoft Exchange Server and OWA (Outlook Web Access). See our latest Release Notes for a full list of system requirements and browsers we've tested with.
What to Look for
While using SafeSend v4.6, do you notice any errors? Does the web add-in seem to have issues when using it with OWA (Outlook Web Access) in a specific browser you're using? Is everything working as expected when using your chosen .NET Core 3.1 capable web server? Are you using both versions of the add-in? How about if you are using the new web add-in on different platforms? Perhaps everything is working perfectly? Let us know!
Your feedback as a beta tester is invaluable to the development process. Whether you love it or hate it, we want to hear from you. You can contact us via email at beta@vipre.com - please include the following information:
- Subject Line: SafeSend
- COM add-in and/or Web add-in
- Operating System
- Browser and version
- Feedback
Special Instructions
Install Web Add-in
While SafeSend v4.6 will work with any .NET CORE 3.1 capable web server, we recommend using IIS (Internet Information Services). If using IIS, you'll need to download and install the .NET Core Hosting Bundle found here.
- Extract the SafeSendWebAddInWeb .zip file
- Open the folder called SafeSendWebAddInWeb and look for the file called settings.json
- If you do not already have a code editor, you can right-click on the file and open with Notepad to make edits
- If you do not already have a code editor, you can right-click on the file and open with Notepad to make edits
- Adjust the following settings:
-
EmailProviderURL
- If you are using Microsoft 365, the EmailProviderURL should already be correct
- If you are using an Exchange Server, you will need to update that setting as appropriate
- Set LicenseKey
- Set SafeDomains
- Set EnablePlatform to True if you will be using Web, PC, or Mac and False for the platforms you will not be using
- If you are using Microsoft 365, Web Add-in works for all 3 available platforms
- If you are using Exchange Server, Web Add-in does not work for Outlook for Mac or OWA in Safari
- For full details, see list of Known Bugs below
-
EmailProviderURL
Important Notes
Microsoft requires the site, which the add-in is hosted on, to be SSL secured.
Deployment of the SafeSend v4.6 web add-in can take up to 12 hours to propagate the network.
Updating the Manifest
The manifest file from the archived .zip file will need to be edited and uploaded.
- Open the file called safesend-manifest.xml
- If you do not already have a code editor, you can right-click on the file and open with Notepad to make edits
- Using Find, search for all instances of the 'localhost' domain and replace this with the site where the add-in will be hosted
Upgrading from SafeSend 4.5 to v4.6
VIPRE Recommends
During the SafeSend v4.6 beta test, we recommend deploying to only a few users in your organization.
When using the COM add-in:
- Create a custom MSI installer
- If you require assistance, visit our Onboarding guide for details on how to customize SafeSend
- 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:
- Deploy a new instance of your chosen web server using your existing license
- Choose a few of your users and enable the web add-in