If all the "clients" who participate in the lists we host were here inside our local network, then perhaps desktop virus scanning might be a source of some comfort.  But they aren't, so we can't presume them to be properly protected.  Taking steps to prevent an email-born virus passing through our listserv is a very important additional piece of the picture when dealing with diverse and dispersed populations.

Protecting only a server is not enough.  Protecting only end-user machines is not enough either.

>>> [log in to unmask] 01/17/01 11:38AM >>>
At 11:19 01/17/2001 Wednesday, Kevin Parris wrote:
 >Thanks for that.... but what I need goes beyond - I need an explicit
 >virus-scanner/detector application that will check all messages coming
 >into the LISTSERV before they are considered for distribution to any
 >lists.  For some lists, we need to allow distribution of any type file, so
 >simply filtering out non-text is no good for this situation.  And
 >preferably, I'd like one that runs on the same NT box that currently hosts
 >LISTSERV and LSMTP for simplicity.

Based upon my small experience, it seems that client-side scanning (and
responsibility) is thee most preferred method.  Penn State operates both
centralized and departmental Mailing List Managers as well as mail
servers, along with folks who have non-PSU server accesses.  If PSU
"just" had/depended upon scanning on our MLM machine(s), we would have
lots of problems.

Just my 0.02 non-denominated units.