Product release information for the initial release of SafeSend Cloud.

What's New

The next generation of email security is here: VIPRE SafeSend Cloud is officially available!

In today’s digital workspace, a single misdirected email or an accidental attachment can lead to a significant data breach. SafeSend Cloud is a Microsoft Outlook® Add-In that automatically scans your outbound emails, then alerts you when you're sending an email to an external recipient. At the Send prompt, SafeSend will present you with options via the Outlook task pane to confirm all external recipients of the email and review any attachments within the email.  

Key Features & Benefits

Get Started

To get up and going with SafeSend Cloud as quickly as possible, we have the Guided Setup of SafeSend Cloud which walks you through the minimum required steps.

SafeSend Cloud Product Documentation

Get Help & Submit Feedback

We are committed to making SafeSend Cloud an essential part of your security strategy, and your input is vital to that mission. You can view our product documentation, share your experiences, report bugs, or reach our Support team directly by clicking the Get Help button within the SafeSend Cloud admin console.

System Requirements for SafeSend Cloud

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.

Accessibility Features

• Issue: Ongoing development of accessibility features
• What’s Happening: Dedicated accessibility tools are not yet fully integrated into the Cloud platform
• What you might see/experience: Users who rely on assistive technologies may find certain interface elements or navigation paths difficult to interact with
• Workaround: We recommend that users with high-level accessibility requirements continue using the SafeSend Self-Hosted Web Add-in while we finalize these updates for the Cloud environment

Right-to-Left (RTL) Language Formatting

• Issue: Rendering limitations for RTL languages
• What’s Happening: The system does not currently render strings for Right-to-Left languages, such as Arabic or Hebrew, in the correct visual order
• What you might see/experience: Text intended for RTL reading may appear left-aligned or with characters out of sequence within the dashboard and user prompts
• Workaround: For optimal clarity, please use English or other Left-to-Right (LTR) languages for all policy configurations and string overrides during this phase

Policy String Validation

• Issue: Ability to save empty "Override Values"
• What’s Happening: The administrative console currently lacks a frontend validation check that prevents the submission of blank fields within the Strings tab
• What you might see/experience: If a user saves an empty override, the system processes it as a blank value. This results in the intended text disappearing entirely from the user interface, potentially leaving end-users without instructions
• Workaround: Ensure every "Override Value" field contains text before saving your policy. If you do not wish to override a specific string, leave the field in its default state rather than submitting an empty value

Event Email Scanning (400 Bad Request)

• Issue: Error status during XHTML attachment scanning for calendar events
• What’s Happening: When processing event-based emails, the scan for XHTML content can encounter a status error, causing the background request to fail
• What you might see/experience: While the SafeSend confirmation dialog will trigger, it may fail to display the specific matches or data expected from the attachment scan
• Workaround: We are currently optimizing the scan logic for these specific event types; in the meantime, we suggest a manual review of attachments on calendar invites before sending

Reporting Dashboard Date Boundaries

• Issue: Data visualizations omit the final date in a selected range
• What’s Happening: There is a minor inconsistency in how the dashboard interprets the end-date of a search. The "To" date is currently being treated as an exclusive boundary for charts
• What you might see/experience: Line graphs and pie charts will not include data from the very last day of your selected range. If you select a single-day range, the charts may appear blank even if the data grid below correctly lists the records
• Workaround: To view chart data inclusive of your target date, simply extend the "To" picker by one additional day. The data grid at the bottom of the page remains the most accurate source for specific daily totals

Nested Protected Attachments

• Issue: Missing password prompts for ZIP files nested within email files
• What’s Happening: The system is currently unable to trigger the password entry dialog for protected ZIP files that are attached inside other email files (such as .eml or .msg attachments)
• What you might see/experience: SafeSend may report the email scan as complete without flagging the protected content or asking for a password, which means matches within that nested ZIP cannot be identified
• Workaround: For the most reliable scanning of protected content, attach ZIP files directly to the primary email rather than nesting them within another attached message file

Policy and Ruleset List Limitations

• Issue: Administrative lists are capped at the first 100 items
• What’s Happening: A technical limitation in the current data request prevents the UI from retrieving or displaying more than 100 Policy Assignments or Rulesets at a time
• What you might see/experience: Existing policies beyond the first 100 will be hidden from view. This can also lead to "duplicate name" validation errors when creating new items that match an existing, but hidden, entry
• Workaround: We are working to implement full pagination shortly. Until then, we recommend consolidating policies where possible to stay within the visible 100-item limit

Distribution List (DL) Configuration

• Issue: Formatting and case sensitivity for Exchange DL matching
• What’s Happening: The setting to treat Exchange distribution lists as external currently does not support multi-line entries and requires an exact case match
• What you might see/experience: If you enter multiple distribution lists on separate lines or use casing that does not match the server exactly (e.g., "Internal_DL" vs "internal_dl"), the system may fail to recognize the lists, and they will not appear in the SafeSend task pane
• Workaround: Please ensure that distribution list names match the intended casing exactly and are entered as a single string per configuration until the multi-line parsing is updated