[EMAIL PROTECTED] wrote:
Mathew,
Sorry for not answering your exact question...BUT
What should should sertainly do is upgrade mimedefang to latest 2.54 and SA
3.0.3 and clamAV 0.87
Actually, SA 3.0.3 is still susceptable to a remote exploitable DoS
attack, if anything upgrade to 3.0.4 (o
Hi All,
Thanks you all for the feedback. The problem is happening only when
the system update the new dat file for the uvscan. Usually it is OK and
get only one or two error message when it do the dat update. Yesterday
somehow it took some time to do it. I was advised by the McAfee
engineer tha
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
[EMAIL PROTECTED] wrote:
> Mathew,
>
> Sorry for not answering your exact question...BUT
>
> What should should sertainly do is upgrade mimedefang to latest 2.54 and SA
> 3.0.3 and clamAV 0.87
>
Actually, SA 3.0.3 is still susceptable to a remo
Mathew,
Sorry for not answering your exact question...BUT
What should should sertainly do is upgrade mimedefang to latest 2.54 and SA
3.0.3 and clamAV 0.87
Meni
Quoting Mathew Thomas <[EMAIL PROTECTED]>:
Dear All,
We have got four mail gateways runninng Solaris 9 with
Sendmail 8-13.1
Mi
> Uvscan 4.3.20
4.3.20 is an old uvscan and they have code that disables the virus scanner
past a certain date. It's possible you've hit that date.
4.4.00 is out and 5.0 beta is out as well.
Find a file that is a test file called eicar.com and run uvscan against that
file with --verbose and se
Dear All,
We have got four mail gateways runninng Solaris 9 with
Sendmail 8-13.1
Mimedefang 2.44
SpamAssassin 2.64 +Razor 2.61 + DCC 1.2.50
Clamav 0.75.1
Uvscan 4.3.20
There were thousands of following error message yesterday. The above
version/set have been running for the last 2 years wi
6 matches
Mail list logo
