Print Page | Close Window

New SpamFilter + antivirus beta 2.5.0.439

Printed From: LogSat Software
Category: Spam Filter ISP
Forum Name: Spam Filter ISP Support
Forum Description: General support for Spam Filter ISP
URL: https://www.logsat.com/spamfilter/forums/forum_posts.asp?TID=5124
Printed Date: 28 November 2025 at 1:25am


Topic: New SpamFilter + antivirus beta 2.5.0.439
Posted By: LogSat
Subject: New SpamFilter + antivirus beta 2.5.0.439
Date Posted: 03 April 2005 at 9:51pm
We have released the public beta for a new version of SpamFilter ISP v2.5.0.349. The following information, along with the download links, is also available on the beta page at http://www.logsat.com/sfi-beta.asp - www.logsat.com/sfi-beta.asp .
 

An Activation Code is required to enable the antivirus plug-in. A 15-day trial Activation Code can be obtained from SpamFilter's GUI on the Settings - Antivirus tab. The code is required only for the antivirus plug-in activation. SpamFilter (both retail and free versions), will continue to work and stop spam even without the antivirus plug-in. While only one request for a trial code will be honored per installation, the counter will be reset when the final retail version of the antivirus plug-in will be released.

Major Changes introduced in SpamFilter ISP v2.5 - The new SpamFilter ISP v2.5 includes support for an anti-virus plug-in. LogSat Software has partnered with http://www.norman.com/ - Norman to provide optional antivirus protection for email traffic.

The antivirus plug-in will be available for purchase separately from SpamFilter ISP and will be an optional component. Unlike SpamFilter ISP's licenses, the antivirus plug-in will be offered as a subscription service with a yearly subscription fee. The amount of the fee has not been finalized yet, but it will not exceed the price of a SpamFilter's license. The availability of the antivirus plug-in for the free version of SpamFilter ISP has not been determined yet.

Technical notes - SpamFilter can run with or without the antivirus plug-in. When SpamFilter starts, it will check for the plug-in files. If they are found, antivirus support will automatically be enabled. We recommend installing the antivirus plug-in after installing SpamFilter. Restart SpamFilter after installing the plug-in to activate it.

The antivirus plug-in is a set of 3 DLL's that are to be installed in the SpamFilter directory: dwnse.dll, ncl.dll and nselapi.dll. In addition to those files, the Norman scan engine needs to be present. If a Norman product is not already installed on the server, the installer adds the necessary files (including the virus definitions) in the SpamFilter\nse directory.

There are 2 additional DLL's that are placed in the SpamFilter directory by the install program: libeay32.dll and ssleay32.dll. These DLLs are used by the antivirus plug-in. If performing a manual install please make sure you copy these files to the SpamFilter directory.

Installation notes for latest antivirus plug-in upgrade - If you installed a previous beta of the plug-in, it is highly recommended that you uninstall it before upgrading with the new plug-in.

After uninstalling, manually delete the registry key:
HKEY_LOCAL_MACHINE\SOFTWARE\Norman Data Defense Systems
before reinstalling the plug-in.

You should not delete the registry entry if your are using other Norman antivirus products on the server.

The update released on 4-3-2005 fixes an issue with dates in non-US date format (mm/dd/yy) which caused the plug-in to fail activation. The same issue caused problems with update of virus definitions. This version also changes the way trial activation codes are made available.

The update released on 3-30-2005 should prevent the A/V plug-in to create temp files under the root of c:\ when scanning emails. This was causing virus infected files to be intercepted by other antivirus software potentially running on the server.

Known Issues - There are cases when the antivirus plug-in installation program does not update the Registry correctly. If the key HKEY_LOCAL_MACHINE\SOFTWARE\Norman Data Defense Systems is not created, please issue the following DOS command from the \SpamFilter\Norman\Nse\bin directory:

NSE /INSTALL

This will add the correct registry entries.

Disclaimer - This version is a pre-release beta. As such, problems are expected. 

This beta will expire on April 14, 2005.



-------------
Roberto Franceschetti

http://www.logsat.com" rel="nofollow - LogSat Software

http://www.logsat.com/sfi-spam-filter.asp" rel="nofollow - Spam Filter ISP



Replies:
Posted By: Guests
Date Posted: 04 April 2005 at 11:11am
What changed from 435 to 439?


Posted By: LogSat
Date Posted: 04 April 2005 at 4:58pm
Changes were indicated in the post above... :

The update released on 4-3-2005 fixes an issue with dates in non-US date format (mm/dd/yy) which caused the plug-in to fail activation. The same issue caused problems with update of virus definitions. This version also changes the way trial activation codes are made available.

The update released on 3-30-2005 should prevent the A/V plug-in to create temp files under the root of c:\ when scanning emails. This was causing virus infected files to be intercepted by other antivirus software potentially running on the server.




-------------
Roberto Franceschetti

http://www.logsat.com" rel="nofollow - LogSat Software

http://www.logsat.com/sfi-spam-filter.asp" rel="nofollow - Spam Filter ISP


Posted By: Guests
Date Posted: 05 April 2005 at 12:03pm

I was curious about the anti-virus reject codes. I do not have a reject code for the anti-virus in my tblrejectcodes.  I was going to run a report to review the antivirus effectiveness and found the missing code.  Is this by design?

 

Dwight



Posted By: Desperado
Date Posted: 05 April 2005 at 12:08pm

Dwight,

The reject code is 17.  It *should* insert the table entry automatically ... it did for me.
Regards,



-------------
The Desperado
Dan Seligmann.
Work: http://www.mags.net
Personal: http://www.desperado.com



Posted By: Guests
Date Posted: 05 April 2005 at 4:23pm
Dwight,

SpamFilter should automatically add any new reject codes to that table automatically. When that happens the entry:

Adding default Reject Codes:

is logged in the SpamFilter activity log. The new reject code was introduced in build 434, which was released on about March 24. You could try scanning the logs for those keywords to see if there were errors right after that entry.



Print Page | Close Window