Once again Thomas, thank you for your help.

Nico, I'll be in touch.

Alex 

Have successfully upgraded to the current release of Mercury.  Been running an old version for so long that I have been using F-Prot policies for virus scanning - did not realize until today that program was no longer being supported and that my virus database was a couple of years old...

Am now trying to install ClamAV (using the installer from http://hideout.ath.cx/clamav) on my Win98 mailserever.

Installation to default directory completes normally, but cannot get ClamD to run (in CMD window) - the library LIBCLAMAV.DLL calls and illegal instruction and the program terminates with an "Illegal Operation" error.

Am I missing a system component? 

Installation to default directory completes normally, but cannot get

ClamD to run (in CMD window) - the library LIBCLAMAV.DLL calls and

illegal instruction and the program terminates with an "Illegal

Operation" error.

Am I missing a system component?

Possibly, you might ask Nico tbb@hideout.ath.cx if this version of ClamAV uses some function that is not available in Win98.  I do know that Win98 does not have a lot of the functions of WinXP.

[quote user="Thomas R. Stephenson"]

Possibly, you might ask Nico tbb@hideout.ath.cx if this version of ClamAV uses some function that is not available in Win98.  I do know that Win98 does not have a lot of the functions of WinXP.

[/quote]

I'm here :) This ClamAV build should run under Win98 as well but unfortunately I have no possibility to test it under this OS. What might cause crashes is a CPU below pentium pro because this build is optimized for i686 (and above). Could that be the problem?

Best regards,

Nico

Thomas and Nico - thank you for the replies.

I think Nico's got it - the processor in this old dinosaur is a P5 chip (Intel P54C2 0050566).

But what to do? - this old Dell XPS system keeps runnig 24/7 year after year - and (unitl now) worked just fine as a mailserver for a small handful of users...  And it has the advantage of being relatively immune to current-day exploits.

Any suggestions as to what I can do for AV at the Mercury-level  using this setup, or is it finally time to retire the old guy?

Alex 

Any suggestions as to what I can do for AV at the Mercury-level  using this setup, or is it finally time to retire the old guy?

Use a different commandline scanner with VirPROT for Mercury.  See http://www3.telus.net/public/irelam/  There must be some sort of command line scanner that works with your setup.

VIRPROT for Mercury Mail Transport System (tm) Version 1.6 January 2006

Virprot was devised to interface in an intelligent way between Mercury and any one of many Anti-Virus software products.
This allows the inspection of email message parts such as attachments and alternate forms of message body text.

Virprot 1.6 is a maintenance release that detects Windows MetaFiles (WMF) and determined by the value of DenyWmf= in Virprot.ini, can reject the attachment entirely. It also detects
any attachment file with file extension type that is not .WMF but contains the .WMF header bytes, ie is a disguised .WMF file

Virprot is a silent 32 bit console application that is invoked by Mercury, and in turn invokes the user choice of anti-virus scanning software.
The result of the scan is passed back to Mercury in one of two ways:

1. Return code method. 0 indicating no problems found, and 1 indicating virus or other problem found, by the AV software

2. Sentinel file method. Mercury waits until a sentinel file that Mercury creates, is deleted by Virprot when scanning has completed.
A second file, the ResultFile, created by Mercury, should it exist when Virprot ends, indicates a problem found by the AV software and usually
contains the report created by the AV software. If the AV software found no problem, Virprot will delete the ResultFile which signals Mercury
that there is no problem with the scanned file.

Well, if there is demand I could of course provide a build which runs on smaller CPU's as well. For now please contact me by mail and I'll see what I can do.

Best regards,

Nico