From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 8632 invoked by alias); 20 Feb 2003 00:58:25 -0000 Mailing-List: contact overseers-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: , Sender: overseers-owner@sources.redhat.com Received: (qmail 8608 invoked from network); 20 Feb 2003 00:58:24 -0000 Received: from unknown (HELO molenda.com) (192.220.74.81) by 172.16.49.205 with SMTP; 20 Feb 2003 00:58:24 -0000 Received: (qmail 95535 invoked by uid 19025); 20 Feb 2003 00:58:24 -0000 Date: Thu, 20 Feb 2003 00:58:00 -0000 From: Jason Molenda To: overseers@sources.redhat.com Subject: Re: New version of mhonarc installed Message-ID: <20030219165824.A93762@molenda.com> References: <20030218225518.A13897@molenda.com> <20030219150011.GA410@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: <20030219150011.GA410@redhat.com>; from cgf@redhat.com on Wed, Feb 19, 2003 at 10:00:11AM -0500 X-SW-Source: 2003-q1/txt/msg00297.txt.bz2 On Wed, Feb 19, 2003 at 10:00:11AM -0500, Christopher Faylor wrote: > Thanks. I thought that munging email addresses in the body is not > something we'd consider because it would screw up ChangeLogs and even, > potentially, source code. I know that some people use the web rather > than subscribing to mailing lists so this might affect them. FWIW, I agree. The new version of mhonarc also handles messages with non-ASCII characters in them far better. Take a look at the aaaspam archives and you'll be impressed by how many lame languages it's being spammed. :-) The indexes for the current time period will have corrected names/subjects, and the newly incoming messages will be decoded correctly far more often now. > Of course, I don't know if we care. Everything we can do to stop the > evil spammers is good. I set up spamassassin a while back and I'm a lot less concerned about being harvested now. One or two spam notes get past my (conservatively configured) spamassassin filters a day, and I can live with that. Stopping spam sent to mailing lists is really important, but I suspect that most folks will get access to a spam filter of some sort sooner or later. > I had a spammer today actually subscribe to the cygwin-xfree mailing list > in order to bypass the spam checking. He unsubscribed shortly thereafter. > > I'm assuming that this unsubscribe was probably a mistake, so I've > resubscribed him. I might have to add the subscribe to a cron job, just > to make sure there are no further mistakes on his part. Excellent! Although he may have been mistaken and really intended to subscribe to cygwin. It doesn't seem to make much sense to just subscribe to cygwin-xfree, when you think about it -- you'd want to know everything that's happening with cygwin itself in addition to XFree86. :-) :-)