Received: with ECARTIS (v1.0.0; list linux-xfs); Fri, 16 Jan 2004 15:07:26 -0800 (PST)
Received: from mail.myphorum.de (mysnip.de.gw.net-build.de [194.25.82.254] (may be forged))
	by oss.sgi.com (8.12.10/8.12.9) with SMTP id i0GN7CmK013211
	for <linux-xfs@oss.sgi.com>; Fri, 16 Jan 2004 15:07:14 -0800
Received: from localhost (myphorum [127.0.0.1])
	by mail.myphorum.de (Postfix) with ESMTP id 0E9BD274463
	for <linux-xfs@oss.sgi.com>; Sat, 17 Jan 2004 00:07:11 +0100 (CET)
Received: from mail.myphorum.de ([127.0.0.1])
 by localhost (myphorum.de [127.0.0.1]) (amavisd-new, port 10024) with ESMTP
 id 11399-08 for <linux-xfs@oss.sgi.com>;
 Sat, 17 Jan 2004 00:07:10 +0100 (CET)
Received: from myphorum.com (pD9E8323C.dip.t-dialin.net [217.232.50.60])
	by mail.myphorum.de (Postfix) with ESMTP id 7199627445D
	for <linux-xfs@oss.sgi.com>; Sat, 17 Jan 2004 00:07:10 +0100 (CET)
Message-ID: <40086E9F.90602@myphorum.com>
Date: Sat, 17 Jan 2004 00:07:11 +0100
From: "Thomas (maillists)" <thomas-lists@myphorum.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.5) Gecko/20031007 MultiZilla/1.6.0.0b
X-Accept-Language: en-us, en
MIME-Version: 1.0
Cc: linux-xfs@oss.sgi.com
Subject: Re: List configuration
References: <Pine.LNX.4.58.0401151607460.26076@bifrost.nevaeh-linux.org> <4007500D.1060806@linuxmail.org> <Pine.LNX.4.58.0401161340400.16362@bifrost.nevaeh-linux.org> <Pine.LNX.4.55.0401161753240.6290@linux-sxs.org> <Pine.LNX.4.58.0401161351360.16362@bifrost.nevaeh-linux.org>
In-Reply-To: <Pine.LNX.4.58.0401161351360.16362@bifrost.nevaeh-linux.org>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: by amavisd-new at mysnip.de
X-archive-position: 1781
X-ecartis-version: Ecartis v1.0.0
Sender: linux-xfs-bounce@oss.sgi.com
Errors-to: linux-xfs-bounce@oss.sgi.com
X-original-sender: thomas-lists@myphorum.com
Precedence: bulk
X-list: linux-xfs
Content-Length: 751
Lines: 31

Arthur Corliss wrote:

> I've got a damned good reason for sending this to the list:
>
>  1) Any managed list should have the applicable administrator
>     subscribed, or someone who reports to him/her, and
>  
>
Why? You could simply contact him directly.

>  2) Publicising the problem may cause others to confirm that
>     they're seeing the exact same behaviour I am.  As a result,
>     the admin might be able to prioritise this based on the
>     severity of the affected.
>  
>

What is severe here? I got my local spamassassin catching the spam just 
fine.


>Deal with it.  Let's get the damned list fixed or boot me off.  Either
>solution would provide positive results for me at this point.
>  
>

You are free to unsubscribe.


thomas