SB> Well I belong to a lot of mailing lists, and I'm not aware of any of them SB> that have actual virus scanning and blocking facilities.
I RUN a lot of mailing lists, and EVERY SINGLE ONE OF THEM has a mechanism to stop most viruses. The most sensible is to disallow attachments, but if attachments are allowed, then the alternative is to set up a size threshhold that prevents dissemination of files above a certain size. Mailman has moderation features that would allow any such mail to be held for approval; if it were legit it could be allowed through. SB> At the end of the day the responsibility for blocking SB> viruses rests with YOU the end reader, not with someone SB> else. I'm not the one allowing the virus to be spread to hundreds or thousands of users by maintaining a mailing list that is essentially an open door for a virus that is contained in a 115Kb attachment. I won't get infected -- but other users invariably will, because sooner or later someone (or someone's kid or secretary or whatever who has access to the same computer) inevitably clicks on the file. How do you think these viruses disseminate in the first place? Every time we see one of these coming through the list, and then 4 or 5 bounce messages, it is probably also going to several people who will make the mistake of opening it. The responsibility for ANYONE running a mailing list is to set up a system to guard against this sort of stuff, just as it is the responsibility of server managers to guard against open proxies on their system. I subscribe to many other lists, including others maintained by sourceforge, and this is the ONLY one with this problem or issue -- I've seen dozens of instances of this your_details.zip since it came out last week, but this is the ONLY mailing list where it is coming through. In any case, it isn't a sourceforge problem, I'm sure that individual list maintainers have access to the Mailman administrative interface, and all the filtering needed is there. SB> My systems virus scanner is blocking them just fine, thank you. Well, my PC systems' spam filtering software does a nifty job, too - so I guess I should just let the users of my servers take care of their own spam filtering as well(?). That is an ODD rationale -- it's fine to just go ahead and allow this known virus with it's built in SMTP engine and trojan capabilities to propagate all over, we'll just assume that everyone knows how to protect themselves. I'm ranting because this problem has been on this list for a week now. When I first saw this virus last week, I took the 5 minutes needed to research it and write a filter for it to prevent it from being propagated either via my mailserver or the lists that I maintained. -Abigail ------------------------------------------------------- This SF.Net email sponsored by: Free pre-built ASP.NET sites including Data Reports, E-commerce, Portals, and Forums are available now. Download today and enter to win an XBOX or Visual Studio .NET. http://aspnet.click-url.com/go/psa00100006ave/direct;at.asp_061203_01/01 _______________________________________________ Spamassassin-talk mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/spamassassin-talk
