> I don't want to re-open the spamming saga, but I am rather alarmed
> to find that the Brown listserver is willing to send out to all
> tei-l list members a virus payload purporting to come from Peter
> Robinson (it doesn't, of course, its true origin is an infected
> machine on the campus of the Universidad Complutense de Madrid ).
> Many people will have had this safely intercepted or flagged by
> their receiving mailhost, but I don't think it's really acceptable
> for a current mailing list not to be able to catch and suppress
> this sort of pernicious traffic rather than blindly propagating it.
> If the current listserver software really can't do this, then I
> think it's time to look for an alternative.

[For those who did not get the infected mail, but really want to
catch the virus, it is archived at
http://listserv.brown.edu/archives/cgi-bin/wa?A2=ind0503&L=tei-l&F=&S=&P=6870.]

This is more interesting than you might think. Some years ago I set
TEI-L to
      Attachments= Yes,text
which means that any attachment that has a MIME type other than "text"
(or "text/[something]") is to be rejected. I've had enough "I can't
attach X" messages over the years to have been convinced it was
working just fine. This attachment is of type
application/octet-stream, so I don't understand at all how it got
distributed, if it did. (I never saw it, and last I knew Brown's mail
server would deliver such files with the attachment stripped out.)

I'll try to look into this a bit, but I'm not very confident I'll
find anything useful. Generally speaking, BTW, I'm told LSoft's
LISTSERV (the software tei-l uses) is very good at this sort of
thing.