An Activation Code is required to enable the antivirus plug-in. You may apply online to receive a free activation code that will be valid for the duration of the beta program.

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.

Changes from the previous beta are as follows:
// New to VersionNumber = '2.5.0.434';
{TODO -cNew : A current antivirus Activation Code is required to enable antivirus plugin}
{TODO -cNew : Added automatic hourly virus definition updates}
{TODO -cNew : Added custom response for SPF filter}
{TODO -cNew : Added custom response for antivirus filter}
{TODO -cNew : Added "aa.bb.cc.dd - No Data Received" log entry if remote server is disconnected without receving any data from it (probes, port scanners,etc)}

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\Nvc\Nse directory:

NSE /INSTALL

This will add the correct registry entries.

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

George,

Roberto has addressed this and I have verified the fix on build 435. Re-Download the Beta and you will get the new build.

Dan

George,

I AM getting plenty of Virus blocks going on.  Double chenk that all the dll's are in place and also, I *manualy* set up the nvc path and registry entries because I originally had the actual Norman installed and then un-installeed it to make sure the new SpamFilter version was working correctly.  My registry "script" is as follows:

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Norman Data Defense Systems]
"NsePath"="D:\\SpamFilterISP\\nvc\\nse"
"RootPath"="D:\\SpamFilterISP"

If you save this as a file named "anything.reg" and douple click on it, it will update the registry (after making mods to match your system).

If I can find your address, I will email you some stats.

Dan S.

Geroge,

If you do have another AV running, make sure it is *not* scanning the SpamFilter folder.

Dan

Roberto,

The new beta 434 is making max incoming connections reach limit.  This is happening on 2 servers that normally have 35-50 incomming connections.  Once the service is started with ver 434 about an hour later the limit is reached at 250 on both servers.  I went back to ver 431 and the problem went away.  I'm running 434 on 2 other servers but the incoming connections never reach over 10.  They too is set for the limit of 250.

FYI: We are not running bayesian filter on those 2 servers.

Thanks,
Dan B

Dan,

This seems to be fixed in 435 as per the post above.  I had the exact same issue and 435 filed it.

Dan S.

Thanks,

That fixed it.

Dan B

George,

I never noticed that because my SpamFilter in not on the root drive.  I just looked and *yikes* there is a ton of tmp files. Thanks for pointing that out to me.

Roberto,

If possible, if the AV used the "tmp" enviroment variable, that would work because I script all the temp files away at midnight.  For now, I have a small java applett that does all my server clean-ups.  I am now setting it up to remove the tmp files in the root.   I NEVER write anything to the root so seeing these was an eye opener.

Regards,

However,

In the short term a simple scheduled task to run a .cmd file will work easily:

del /q c:\*.tmp

Run say once / hour

For George, I guess the c:\*.tmp could be "Excluded" from the AV scanning ... Yes?

Dan

I already have a Norman AV Server Installation on my server. The previous beta (431) happily used this Norman instance.

The new build (435) now says: no antivirus support files found on server and no virus checking is being done.

The 2 plugin dlls are in the spamfilter folder though...

Help!

Mikek,

If norman is installed, try removing the registry entry "Norman Defense Systems" but still make sure all the dll's are in the SpamFilter root ... I think 3 not 2 dll's.  And make sure the On Access Scanner is NOT scanning the SpamFilter folder.  Remember that the Norman Application will be doing the updates ... not spam filter so make sure that is disabled on spamfilter.  In this mode, SpamFilter does not actually use the plugin but detects the "Real" Norman scan engine.

I do not know if this will help but when I had Norman on my server, this is what I did.  I no longer am running the Norman App on my SpamFilter server so I had to put the registry entries back in and (THIS IS IMPORTANT) I still did not work until I rebooted.  I got the "no antivirus support files found on server" error.   Once I rebotted, it worked.

All the above may or may not be your issue but give it a shot.

Regards,

Roberto,

Will Do.

Dan

Desperado wrote: If norman is installed, try removing the registry entry "Norman Defense Systems" but still make sure all the dll's are in the SpamFilter root ... I think 3 not 2 dll's.  And make sure the On Access Scanner is NOT scanning the SpamFilter folder.  Remember that the Norman Application will be doing the updates ... not spam filter so make sure that is disabled on spamfilter.  In this mode, SpamFilter does not actually use the plugin but detects the "Real" Norman scan engine. I do not know if this will help but when I had Norman on my server, this is what I did.  I no longer am running the Norman App on my SpamFilter server so I had to put the registry entries back in and (THIS IS IMPORTANT) I still did not work until I rebooted.  I got the "no antivirus support files found on server" error.   Once I rebotted, it worked. All the above may or may not be your issue but give it a shot. Regards,

Dan, I can't remove the Norman Data Defense Registry Entries because the Mailserver on the same server is using the Norman Engine as well. I have rebooted the server after installing the new SpamFilter version and activating the AV plugin.

Roberto: any help on this issue? "Activation Status" is empty, although the activation code has been entered and saved in SpamFilter.ini. What exactly is SpamFilter looking for to determine if "Antivirus support files" are found or not?

Just FYI... not a SpamFilter problem, but something you need to be aware of.

The email containing the activation code can apparently be corrupted by Microsoft Outlook.  I installed the new beta earlier today, and requested the activation code through the online form.  The activation code email that was sent to me appeared to have the code split across two lines.  My first thought was that it was just a line-wrap issue, so I just concatenated the two lines manually... this didn't work.

Finally, after trying several other measures, I requested another activation code, but this time opened it in a Web Mail client (non-Microsoft).  The activation code displayed properly, and the problem became clear.

For some reason, Outlook is breaking-up the activation code after the 72nd character.  On the next line, the first 12 characters of the activation code are REPEATED, followed by the remaining few characters of the activation code.

Again, this isn't a LogSat or SpamFilter problem, it's an Outlook issue... and may even be more specific than that, it might only be CERTAIN VERSIONS of Outlook, I don't know.  But if anyone else is seeing this same issue (the activation code split across two lines, with the first 12 characters repeated on both lines) you might consider using a different mail client to get the activation code.

LogSat wrote: The plugin will not initialize until a valid activation code has been entered. Once you paste the activation code and click on "Activate", you should see some status "stuff" appearing below the "Activate" button, and only after that happened the AV plugin is loaded. Can you describe what happens after you click on the Activate button?

Hi Roberto,

Thanks for your reply. When I click on "Activate" I can not see anything happen. The "Activation Status" Windows remains empty... I tried activating with a bogus key as well - same here - no display of any kind...

The AV plugin will not activate if the regional settings of the server define a date format different from the standard "English" date (mm/dd/yyyy). My server is running "German (Switzerland)" (dd.mm.yyyy), that's why the AV plugin will not activate.

Roberto and I have verified this and he is working on a fix for this problem as I type