This message generated a parse failure. Raw output follows here. Please use 'back' to navigate. From devnull@lkml.org Tue Jun 28 02:33:06 2022 Received: from spaans.ds9a.nl (adsl-xs4all.ds9a.nl [213.84.159.51]) by kylie.puddingonline.com (8.11.6/8.11.6) with SMTP id g8IIifX21177 for ; Wed, 18 Sep 2002 20:44:42 +0200 Received: (qmail 28861 invoked from network); 18 Sep 2002 06:32:17 -0000 Received: from unknown (HELO spaans.ds9a.nl) (3ffe:8280:10:360:202:44ff:fe2a:a1dd) by mayo.ipv6.ds9a.nl with SMTP; 18 Sep 2002 06:32:17 -0000 Received: (qmail 27386 invoked by uid 1000); 17 Sep 2002 19:59:36 -0000 Received: (maildatabase); juh Received: (qmail 13211 invoked by alias); 24 Jan 2001 10:51:48 -0000 Received: (qmail 13208 invoked from network); 24 Jan 2001 10:51:47 -0000 Received: from vger.kernel.org (199.183.24.194) by spaans.ds9a.nl with SMTP; 24 Jan 2001 10:51:47 -0000 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Wed, 24 Jan 2001 05:51:03 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Wed, 24 Jan 2001 05:50:54 -0500 Received: from mail.zmailer.org ([194.252.70.162]:4360 "EHLO zmailer.org") by vger.kernel.org with ESMTP id ; Wed, 24 Jan 2001 05:50:41 -0500 Date: Wed, 24 Jan 2001 12:50:31 +0200 From: Matti Aarnio To: linux-kernel@vger.kernel.org Subject: What that Majordomo testing was about ... Message-Id: <20010124125031.W25659@mea-ext.zmailer.org> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="livrSZtJkVq9DDdS" Content-Disposition: inline Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org --livrSZtJkVq9DDdS Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Ok, I think I have waited enough to be fairly sure that now the thing worked. The first goal was to create configuration which detects the presense of: X-Mailing-List: linux-kernel@vger.kernel.org header, and blocks it. That should prevent loops in the list when somebody goofs up and sends email out from their fetchmail, or whatever, to the VISIBLE headers of the message. Tabooing some discussion subjects isn't primary goal, but apparently such is also possible, if needed. Also tabooing messages which contain juicy key phrases which spammers often use to "legitimize" their postings is possible, although presently not very much such spam email makes to the system (and thus thru the lists). It is amazing what RBL+DUL+RSS trio can filter quickly. ... and none of that discussion above should make to the list under subject of "Third Majordomo Test" ;) /Matti Aarnio --livrSZtJkVq9DDdS Content-Type: message/rfc822 Content-Disposition: inline Received: (from localhost user: 'mea' uid#500 fake: STDIN (mea@zmailer.org)) by mail.zmailer.org id ; Wed, 24 Jan 2001 12:39:32 +0200 Date: Wed, 24 Jan 2001 12:39:32 +0200 Sender: Matti Aarnio From: Matti Aarnio To: linux-kernel@vger.kernel.org Subject: Third Majordomo taboo_header test Message-ID: <20010124123932.V25659@mea-ext.zmailer.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-Mailing-List: linux-kernel@vger.kernel.org Return-Path: X-Envelope-To: (uid 500) X-Orcpt: rfc822;mea@mea-ext.zmailer.org The first goal is to create configuration which detects the presense of: X-Mailing-List: linux-kernel@vger.kernel.org header, and blocks it. That should prevent loops in the list when somebody goofs up and sends email out from their fetchmail, or whatever, to the VISIBLE headers of the message. Tabooing some discussion subjects isn't primary goal, but apparently such is also possible, if needed. ... and none of that discussion should make to the list ;) /Matti Aarnio --livrSZtJkVq9DDdS-- - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org Please read the FAQ at http://www.tux.org/lkml/