On Wed, May 05, 2004 at 09:25:08PM -0400, Chris Devers wrote: > Okay, so two viruses have made it to the list today. In both cases, it > looks like the mail came from Verizon customers: > > Received: from pm.org (pool-141-154-212-242.bos.east.verizon.net > [141.154.212.242]) > by mail.pm.org (8.11.6/8.11.6) with ESMTP id i45Joc914994 > for <[EMAIL PROTECTED]>; Wed, 5 May 2004 14:50:39 -0500 > > Received: from pm.org (pool-141-154-222-33.bos.east.verizon.net > [141.154.222.33]) > by mail.pm.org (8.11.6/8.11.6) with ESMTP id i460aa919816 > for <[EMAIL PROTECTED]>; Wed, 5 May 2004 19:36:36 -0500 > > Boston.pm's mail is served by Mailman, right? Does Mailman have a way to > filter [presumably unsubscribed] incoming mail by network?
These messages were both forged from addresses that are subscribed to the mailing list, which is why they made it through. Incoming mail from non-member addresses is already moderated. > Going to a purely moderated list might be annoying for whoever has to do > it [maybe Ronald, maybe someone else]. I have already turned on content filtering for the list. This will remove unwanted attachments, but still sends the remainder of the message through. (This is why the second message was missing its payload.) If that's not sufficient I can try rejecting all messages that contain attachments, but that will block some legitimate posts. > Going to the pure Perl Siesta list manager software would be an > interesting move, but I'm not sure if it's stable enough yet. That would be up to the pm.org sysadmins. Ronald _______________________________________________ Boston-pm mailing list [EMAIL PROTECTED] http://mail.pm.org/mailman/listinfo/boston-pm
