Re: Subscriber List Damage

Glen <glen@amsl.com> Tue, 01 July 2008 00:36 UTC

Return-Path: <ietf-bounces@ietf.org>
X-Original-To: ietf-archive@megatron.ietf.org
Delivered-To: ietfarch-ietf-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id DA7253A681F; Mon, 30 Jun 2008 17:36:54 -0700 (PDT)
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 4740E3A681F; Mon, 30 Jun 2008 17:36:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.492
X-Spam-Level:
X-Spam-Status: No, score=-100.492 tagged_above=-999 required=5 tests=[AWL=0.003, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, RDNS_NONE=0.1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FeViMzITTqTz; Mon, 30 Jun 2008 17:36:52 -0700 (PDT)
Received: from mail.amsl.com (mail.amsl.com [IPv6:2001:1890:1112:1::14]) by core3.amsl.com (Postfix) with ESMTP id 7AD713A67F7; Mon, 30 Jun 2008 17:36:52 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by thunder2.amsl.com (Postfix) with ESMTP id AD4A7480B4; Mon, 30 Jun 2008 17:37:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from mail.amsl.com ([64.170.98.20]) by localhost (thunder2.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KHaAOisN6XCx; Mon, 30 Jun 2008 17:37:12 -0700 (PDT)
Received: from [192.168.1.100] (c-76-103-55-1.hsd1.ca.comcast.net [76.103.55.1]) by thunder2.amsl.com (Postfix) with ESMTP id 690B047ED5; Mon, 30 Jun 2008 17:37:12 -0700 (PDT)
Message-ID: <48697C2F.7050207@amsl.com>
Date: Mon, 30 Jun 2008 17:37:03 -0700
From: Glen <glen@amsl.com>
User-Agent: Thunderbird 2.0.0.14 (Windows/20080421)
MIME-Version: 1.0
To: Michael Thomas <mat@cisco.com>
Subject: Re: Subscriber List Damage
References: <48671722.1020502@amsl.com> <486962AA.3000800@cisco.com>
In-Reply-To: <486962AA.3000800@cisco.com>
X-Enigmail-Version: 0.95.6
Cc: sip@ietf.org, IAOC <iaoc@ietf.org>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org

Michael Thomas wrote:
> 1) Have you brought this up with the mailman folks? I've interacted with
>    them and they seem like a responsive set of folks. I'm sure that this 
> sort
>    of thing would horrify them.

I haven't yet, but will try.  They'll probably want more information 
than I can give them.

> 2) 3 years since the last backup? Oi.

No - not three years since the last backup.  I have MUCH more recent 
backups than that, of course!

Three years is the age of the file that I suspect mailman used to pull 
its old configuration from.  An old copy of the database for those two 
lists that was just sitting around, not being used.

Glen
_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www.ietf.org/mailman/listinfo/ietf