From mboxrd@z Thu Jan 1 00:00:00 1970 From: Chris Mason Subject: Re: Recent spam Date: 05 Jun 2003 12:30:27 -0400 Message-ID: <1054830626.23132.169.camel@tiny.suse.com> References: <3EDAEEBE.3050202@netscape.net> <200306020833.40614.m.c.p@gmx.net> <1054538668.8091.8.camel@localhost> <200306021859.39138.russell@coker.com.au> <3EDF450A.1060003@namesys.com> <20030605145709.GM15761@parcelfarce.linux.theplanet.co.uk> <1054825912.23132.152.camel@tiny.suse.com> <16095.24867.932302.642195@laputa.namesys.com> Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Return-path: list-help: list-unsubscribe: list-post: Errors-To: flx@namesys.com In-Reply-To: <16095.24867.932302.642195@laputa.namesys.com> List-Id: Content-Type: text/plain; charset="us-ascii" To: Nikita Danilov Cc: Chris Dukes , Hans Reiser , Russell Coker , Soeren Sonnenburg , reiserfs-list On Thu, 2003-06-05 at 11:26, Nikita Danilov wrote: > Chris Mason writes: > > [...] > > > > > These two are unrelated. SPAM is a fact of life on the internet, list > > admins have a responsibility to try and make things better for list > > subscribers, how well namesys meets is directly related to the quality > > of the list and its content. > > Probably irrelevant, but I have spam assassin installed on my machine, > and I see exactly zero spam coming from reiserfs list. Same here (bogofilter), either one would have filtered the spam with or without the tagging on the reiserfs list side. The problem is how the headers are stripped from the spam that is tagged by the mailing list. People that use automated spam reporting tools end up blaming namesys instead of the actual sender. -chris