SpamSentinel Version 7.7.2.8
STILL the best anti-spam and anti-virus solution for Notes and Domino!

Release Date: December 2012

Welcome to SpamSentinel Version 7.7.2.8. 
We have updated our core engines with the latest code available, continuing to bring you the best anti-spam and anti-virus option for Lotus Notes/Domino. There are a number of new features, along with the regular round of fixes - please see below for the full list. As always, if you have any questions, feedback or requests for new functionality we would be very happy to hear from you.

SpamSentinel 7.7.2.8 runs on Lotus Domino versions 6 and higher.

Version Highlights:


A new feature called 'X-Field Eliminator' has been added which addresses an issue with Domino when the maximum number of fields that can be stored in a database is reached. This mainly affects the mail.box files and results in the error 'Cannot store document - database has too many unique field names'. X-Field Eliminator gives you the option to delete the X-Fields, rename them or roll them up into a single field. More information can be found here: X-Field Eliminator in SpamSentinel

We would also like to remind you that our popular Manage By Example (MBE) tool is now included in the SpamSentinel package. "SpamSentinel MBE", unlike previous versions, does not require any changes to the mail template and runs as an add-in on the servers hosting your mail files. It replaces the daily report as the most up-to-date way to manage suspect messages. We also include the MBE installer to allow you to easily install onto mail servers that do not necessarily run SpamSentinel
.

MBE gives your users complete control over the grey area of Spam-B and Newsletters, freeing up your administrators and help-desk staff. Unless you already use MBE this option will be installed in the disabled state, please see www.maysoft.com/mbe for more information, a short but instructive video and a guide that you can send to your users.


SpamSentinel Version 7.7.2.8 Improvements


SpamSentinel Interceptor 2.6.5.6
  • The Interceptor has been updated to perform an X-Field rollup. There are four options, delete X-Fields, rename X-Fields, rollup X-Fields into RFC822 text field, or rollup X-Fields into a rich text field. You can also white list X-Fields so that they are not processed.
  • Update to check for Skip Forms for outbound messages. This is necessary for Message Recall to work properly.
  • Preserve UNID of outbound messages when copied to the scan.box.

SpamSentinel Duo Engines 3.5.0.6 
  • Updated with Authentium AV SDK 5.3.20.6.
  • Updated Commtouch version 8.0.0.63
  • Updated Cloudmark version 1.7.4.14

SpamSentinel Router 2.6.2.9
  • Send 'dbcache flush' to server console after writing signed database 'pointer' file. Uses NABServerName field for server.

SpamSentinel Scanner 7.7.2.8
  • Truncate e-mail addresses greater than 256 characters.
  • Automatically enable Notes name resolution for Spam-D when using Skip or Include Recipients. Notes Name resolution only occurs for Spam-D if name resolution is enabled. One way that name resolution is enabled is when messages are quarantined for reporting. If no reporting is selected, then Notes names are not resolved from e-mail addresses, and no lookups (skip, included, etc) are performed.
  • Added code to restore Delivery Confirmation field from a backup field. The backup field is created by the Interceptor when messages are signed or sealed and mailed to the scan box. If the field is not backed up then a delivery confirmation is sent to the user when the message is delivered to the scan box.
  • Enhanced license expiration email with server name and links to admin database.
  • Fixed problem where a non-hierarchal user appeared to have a profile document. This caused the message to be duplicated in order to 'use' the profile.
  • When a user is white listed, the SpamSentinel fields are normally removed. This can make is difficult to determine if the message was spam when white listed. The fields are now added to a SpamS_SpamReport field before they are removed.
  • If a message has multiple recipients, and one is white listed, the white listed user is treated as a skip recipient. This can cause some confusion because the message appears in the user mail box with most of the SpamSentinel fields, but does not have a message type field. Temporarily, a message type field was added with the value "Skipped or White Listed". In a future version, the white listed recipient will appear as white listed rather than skipped.
  • Fixed naming issue with X-Field names. X-Field name 'dashes' were encoded by Domino before they were mailed.
  • This version also contains the code to release held messages on a checking machine when SpamSentinel is disabled. This prevents mail from backing up when SpamSentinel expires.

SpamSentinel Reporter 2.0.3.5
  • Added 'Large memory aware' code fix for 32-bit Domino running on a 64-bit operating system

SpamSentinel Administration Database
  • Added UI options to support new features.
  • Removed some obsolete settings.

SpamSentinel Manager 2.6.2.8 
  • No changes have been made to the SpamSentinel Manager.

SpamSentinel Monitor 2.7.0.7 
  • No changes have been made to the SpamSentinel Monitor

Non-Windows/Checking Machine Installations (AS400/Linux/Solaris)
  • Engine, scanner and database updates have been made as above.
  • Fix for a scenario where Spam-D would occasionally be delivered to the Inbox.
  • Please be aware that the new SpamSentinel MBE tool will only be installed on servers that run Linux. Servers running AS/400 or Solaris should use MBE version 3. 

Click here to learn more about our previous release: Improvements in 7.7.2.1
SpamSentinel: It just works!

MayFlower Software
(978) 635-1700
http://www.maysoft.com/

©Copyright 2011 MayFlower Software, Inc. - All rights reserved worldwide.