I don't think it came through the list [Eug-lug] . I didn't see it, and my procmail log shows no message of that Return-Path:/From: address --there are many of that subject line, but none from that address.
Not in the archives either, as far as I can tell.

 - Horst


Date: Mon, 23 Jan 2006 08:08:05 -0800
From: Bob Miller <[EMAIL PROTECTED]>
Reply-To: Eugene Unix and Gnu/Linux User Group <euglug@euglug.org>
To: euglug@euglug.org
Subject: Re: [Eug-lug] Spam on euglug list

Edward Craig wrote:

That I haven't noticed this may be an artifact of Gmail's spam filters.
I wonder if examining the full headers might reveal this never passed
through EUGLUG servers, as I infer from the lack of munged  subject to
include [Eug-lug].

Here are the headers.

 Return-Path: [EMAIL PROTECTED]
 Delivered-To: [EMAIL PROTECTED]
 Received: (qmail 18891 invoked from network); 21 Jan 2006 11:37:36 -0000
 Received: from euglug.org (HELO tux.euglug.org) (207.189.131.194)
          by chezgeek.euglug.net with SMTP; 21 Jan 2006 11:37:36 -0000
 Received: from 207.189.131.194 (unknown [219.155.181.200])
          by tux.euglug.org (Postfix) with SMTP
          id EC67D481; Sat, 21 Jan 2006 03:36:19 -0800 (PST)
 Received: (from [EMAIL PROTECTED])
          by 219.155.181.200 (8.12.8/8.12.8/Submit) id j3CHmn9V937414
          for euglug@euglug.org; Sat, 21 Jan 2006 05:36:18 -0600
 Message-ID: <[EMAIL PROTECTED]>
 Date: Sat, 21 Jan 2006 05:36:18 -0600
 From: Wm Lacey <[EMAIL PROTECTED]>
 X-Mailer: MIME-tools 5.470 (Entity 5.059)
 MIME-Version: 1.0
 To: euglug@euglug.org
 X-Spam-Score: (-2.857) BAYES_00
 X-Scanned-By: MIMEDefang 2.52 on 219.155.181.200
 X-Scanned-By: SpamAssassin 3.511824, File::Scan 0.45, Archive::Zip 1.85
 X-Recipient: <euglug@euglug.org>
 Subject: Re-finance before rates skyrocket
 Content-Type: multipart/related; boundary="------------AttPart_02541267==.OLA"
 Status: O
 Content-Length: 8682
 Lines: 136

I don't pretend to understand mail routing.  It has Received headers
that indicate it went through EUGLUG's mail server.  It doesn't have
the [eug-lug] subject nugget to indicate it went through mailman.

I note that our mailman installation is at 2.1.5, and that 2.1.6
fixes a security hole related to revealing passwords.

--
Bob Miller                              K<bob>
                                       [EMAIL PROTECTED]
_______________________________________________
EUGLUG mailing list
euglug@euglug.org
http://www.euglug.org/mailman/listinfo/euglug

_______________________________________________
EUGLUG mailing list
euglug@euglug.org
http://www.euglug.org/mailman/listinfo/euglug

Reply via email to