Re: Subscriber List Damage

"Frank Ellermann" <nobody@xyzzy.claranet.de> Tue, 01 July 2008 07:04 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 EB8673A687C; Tue, 1 Jul 2008 00:04:52 -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 CA2CC3A687C for <ietf@core3.amsl.com>; Tue, 1 Jul 2008 00:04:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.864
X-Spam-Level:
X-Spam-Status: No, score=-3.864 tagged_above=-999 required=5 tests=[AWL=-0.265, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
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 VvSym8bR1n9K for <ietf@core3.amsl.com>; Tue, 1 Jul 2008 00:04:51 -0700 (PDT)
Received: from ciao.gmane.org (main.gmane.org [80.91.229.2]) by core3.amsl.com (Postfix) with ESMTP id EB9B83A67D6 for <ietf@ietf.org>; Tue, 1 Jul 2008 00:04:50 -0700 (PDT)
Received: from list by ciao.gmane.org with local (Exim 4.43) id 1KDZvA-0003fy-Hw for ietf@ietf.org; Tue, 01 Jul 2008 07:05:00 +0000
Received: from hmbg-d9b88e3c.pool.mediaways.net ([217.184.142.60]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for <ietf@ietf.org>; Tue, 01 Jul 2008 07:05:00 +0000
Received: from nobody by hmbg-d9b88e3c.pool.mediaways.net with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for <ietf@ietf.org>; Tue, 01 Jul 2008 07:05:00 +0000
X-Injected-Via-Gmane: http://gmane.org/
To: ietf@ietf.org
From: "Frank Ellermann" <nobody@xyzzy.claranet.de>
Subject: Re: Subscriber List Damage
Date: Tue, 1 Jul 2008 09:07:30 +0200
Organization: <http://purl.net/xyzzy>
Lines: 11
Message-ID: <g4ckuk$boq$1@ger.gmane.org>
References: <48671722.1020502@amsl.com> <486962AA.3000800@cisco.com><20080701014218.93BD5509A9@romeo.rtfm.com> <486996AC.2050405@amsl.com> <878wwmi02q.fsf@mocca.josefsson.org>
Mime-Version: 1.0
X-Complaints-To: usenet@ger.gmane.org
X-Gmane-NNTP-Posting-Host: hmbg-d9b88e3c.pool.mediaways.net
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2800.1914
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1914
Cc: sip@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Frank Ellermann <hmdmhdfmhdjmzdtjmzdtzktdkztdjz@gmail.com>
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-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org

Simon Josefsson wrote:
 
> How about an IETF "operations" mailing list?  There is the tools
> mailing list, but I don't think this kind of operational discussions
> belong there.  People interested in the operations of various IETF
> servers could join that mailing list.  The list might even be an
> helpful resource for incidents like this.

+1  Ideally hosted elsewhere, but using mailman to check out things.

 Frank

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