Trend Anti-virus has a software package that scans mail before it gets to
the mail server.  It does slow stuff down some and we thought it sometimes
caused problems, but it did seem to work.  We have dropped it use here and
never used it to cover listserv.

John L. Mottl
Network Administrator
The American Ceramic Society
735 Ceramic Place
Westerville, OH 43081
Ph: 614.794.5864
E-mail: [log in to unmask]

...........................
...........................
On 1/17/01 at 11:19 AM the talented Kevin Parris
offered the following discourse in a most eloquent manner:


>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.
>
>>>> [log in to unmask] 01/17/01 09:04AM >>>
>[I offer the following *as is* w/ no further explanation.  I had recently
>sent this to another correspondent.]
>
> >help me out.  What kind of anti-virus setup are you using to scan
> >messages and attachments arriving at your LISTSERV for distribution?
>
>--
>
>First and Foremost, we use LISTSERV(R) brand mailing list management
>software.  We have configured it (relative to security) as such, which
>allows us to better ameliorate spam and virus/worms:
>
>ADMINISTRATION of USA Financial Aid Offices
>
>Subscription= Open,CONFIRM Reply-To= SENDER,Respect
>Confirm-Delay= 71 h
>Send= PRIVATE           Confidential= No        Review= owner
>Validate= NO            Language= NOHTML
>Attachments= No
>Default-options= Repro,Short,Review
>Filter= Also,*postmast*@*,*postmstr*@*,*maiser*@*,*nobody*@*
>Renewal= 3-monthly,Delay(7),Probe
>Sizelim= 200
>
>This translates into:
>
>One must subscribe in order to be allowed to post to the list
>
>One can only subscribe by going through a process: customer "asks" our
>software to subscribe, our software acknowledges that request by
>returning a pseudo random number to the requester, the requester returns
>that PRN back to our software and is successfully subscribed
>
>Subscribers can not get a list of other list subscribers, unless the
>latter post to the list
>
>List does NOT permit non-text attachments e.g., NO .WDP, .EXE, JPG, .XLS,
>.VCARD
>
>We limit per message size to 200 lines
>
>List distributions "default" REPLY-TO: the poster, and not the list (this
>isn't fool-proof)
>
>New subscribers are automatically moderated, though by manual
>intervention, we do turn off moderation for all .EDU subscribers; all
>others must "prove" themselves (within our target audience) in order to
>post w/o moderation
>
>Multiple list-owners are defined and we encourage the use of the generic
>list-owner address of [log in to unmask]; list-owners
>coordinate their activities so that mail to the generic address is
>answered a timely fashion
>
>One of its "secondary" features is an inter-connected network of peered
>(list) servers and it maintains an anti-spam feature among themselves, as
>close to real-time as a store-n-forward network will allow.
>
>Our institution has both centralized and distributed security,
>information, and network offices/personnel.  We highly encourage, and
>provide licenses (some no-charge, others costs) and WEB sites for A/V
software.
>
>See also:
>
>http://www.emoderators.com/moderators/how2list.html
>
>/Pete Weiss
>Sr. Systems Engineer -- Penn State
>
>
>At 09:56 01/16/2001 Tuesday,
> >Our state and regional organizations are looking at what can be done for
our
> >list serves to combat virus transfers.
> >
> >Would you mind sharing more information regarding what you do and other
> >possible resources we can investigate along these lines?

and that is what Kevin Parris said.
...........................
...........................