Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email email@example.com
From: Todd Lyons (toddmrball.net)
Date: Thu Dec 06 2001 - 11:58:21 CST
Buchan Milne wanted us to know:
>Well, the script takes variables for the paths to all the supported
>scanners, and uses all the scanners it finds. So theoretically you could
It would be rather painless to cut the chunk of the script out where it
defines all of the constants and put it in a seperate config file which
is then sourced by the main file. Again, my experience is with the
shell script version, not the perl version. I do not know how easy this
would be with the perl version.
>>The problem is if we build amavis, we have to build *many* packages.
>>For instance, we could use kaspersky by default, but then we would
>>have to have:
I disagree. Move the configuration out to a separate file
(/etc/sysconfig/amavis or /etc/amavis.conf for example). Then one
amavis package can handle any of the virus scanners that the current
script works with. The configure script will have to be hacked, but on
the surface that doesn't appear very complicated.
>Apparently the new amavisd with a newer postfix can run with only one
>I am also not sure whether amavisd can keep the virus scanning engine
>running (for Sophos and Trend) similar to how sophie and trophie do.
I'm not exactly sure what you're saying here. We only use sweep to scan
incoming mail, we don't use amavisd on the mail server. Now the samba
server, that's a different story. amavisd is running on the samba
server as well as a cron'd sweep process (just in case). Finally SAV on
each of the clients. Got the wagons circled up :)
-- Blue skies... Todd | Get a bigger hammer! | Are you feeling lucky...punk? | | http://www.mrball.net | I've had better days... | | http://faq.mrball.net | It's the end of the world as we know i|