Release information for VIPRE Email Security - Server Edition version 10.3. Released on February 7, 2019.

Release information

• Product: VIPRE Email Security - Server Edition
• Version: 10.3
• Released: February 7, 2019

Note: VIPRE Email Security for Exchange 2000/2003 will not receive this update.

This release rolls up changes from the 10.1 and 10.2 service releases with the feature change listed below. See Previous Releases below for more information on the previous changes.

System Requirements

Supported Microsoft Exchange Versions

• Exchange 2016
• Exchange 2013
• Exchange 2010
• Exchange 2007

Additional Requirements

• CPU: 2GHz or higher with multiple cores
• RAM: At least 1GB more than what is allocated for running Exchange
• .NET Framework 3.5
• Browser: Internet Explorer 6.0 or higher for disclaimer editing
• 512 MB memory
• Additional Space: 100MB for installation (Quarantine store requires more space)

Supported OS for Report & Quarantine Store Viewer

• Windows 8
• Windows 7
• Windows Vista
• Windows XP
• Windows Server 2012
• Windows Server 2008 x64
• Windows Server 2008 R2 x64
• Windows Server 2003 R2 x64
• Windows Server 2003 x64

Product and company names are trademarks and registered trademarks of their respective owners.

Important expiration details

Previous versions of VIPRE Email Security include third-party anti-spam components with a built-in expiration date. These components will stop working sometime between May 2019 and May 2020, depending on when you purchased the product.

It is VIPRE’s strong recommendation that you update to this latest release prior to May 2019 to avoid any possible service outages due to the embedded third-party licenses expiring.

Features

• New antispam engine – Upgraded the antispam engines to a consolidated, new technology engine

What you should know

With this release, we’ve upgraded the Antispam Engine, and as a result we now display all Antispam Engine settings in a single tab.

This engine change also affects the default antispam action. With the new default settings, all messages determined as spam will be quarantined, as opposed to the prior behavior where high-scoring items were set to be deleted.

Please take a moment to review your antispam settings — especially your “delete” and “quarantine” thresholds — based on the new change.  

To view your antispam settings

After updating to version 10.3, review your settings and adjust as necessary.

1. Navigate to Policies & Recipients > Antispam > Global Settings
2. Under Application Engine Settings, review the settings 
   1. Aggressivity - increasing this number will catch more spam, but increases the risk for false positives
   2. Score when... - for the given category, determine if you need to adjust the score depending on your company's requirements

Known issues and workarounds 

There are no known issues with this release.

Bug fixes and improvements

This release rolls up a variety of bugs fixed since the release of version 4.5.

Improvements

• NJA-628 - Attachment scanning speed has been improved
• NJA-659 - Increased database performance when server is under heavy mail flow
• NJA-712 - Better archive handling; removed failure condition for "Corrupt Archive"

Bugs fixed

• NJA-780 - Some emails with PDF attachments are quarantined with reason "scan failed". Immediately re-sending the email is usually successful
• NJA-768 - Migrating Report storage from the native MDB database to SQLExpress (SQL Server) causes log error message "Invalid object name 'VirusSenders'"
• NJA-761 - Certain messages scanned by antivirus could be placed in the "Unprocessed email" folder
• NJA-735 - Attachments less than 8 bytes could be quarantined with "Scan failed" message
• NJA-716 - Internal database could fail to purge old records
• NJA-709 - Message Tracker incorrectly showed Delaylisting as the source of Antispam delays
• NJA-638 - Recipients on different policies could fail to receive some group emails
• NJA-573 - Extraneous "Ninja Routing Agent went async" messages appearing in logs