[ietf-dkim] change of venue for ietf-dkim mailing list

Dave Crocker <dcrocker@bbiw.net> Wed, 14 February 2018 19:26 UTC

Return-Path: <ietf-dkim-bounces@mipassoc.org>
X-Original-To: ietfarch-ietf-dkim-archive@ietfa.amsl.com
Delivered-To: ietfarch-ietf-dkim-archive@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id 55359127867 for <ietfarch-ietf-dkim-archive@ietfa.amsl.com>; Wed, 14 Feb 2018 11:26:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=bbiw.net header.b=mREkkl6W; dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=bbiw.net header.b=BfD8mSvy
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id Had4v2zEwd03 for <ietfarch-ietf-dkim-archive@ietfa.amsl.com>; Wed, 14 Feb 2018 11:26:38 -0800 (PST)
Received: from simon.songbird.com (simon.songbird.com []) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DFC34124205 for <ietf-dkim-archive@ietf.org>; Wed, 14 Feb 2018 11:26:38 -0800 (PST)
Received: from simon.songbird.com (simon.songbird.com []) by simon.songbird.com (8.14.4/8.14.4/Debian-4.1ubuntu1) with ESMTP id w1EJPd3G011220; Wed, 14 Feb 2018 11:25:40 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=bbiw.net; s=default; t=1518636359; bh=cCrNPH35tf0/vDeO0Svf0sFWWWPMxASyvdf4Hyd3zEE=; h=To:From:Date:Subject:List-Id:List-Unsubscribe:List-Archive: List-Post:List-Help:List-Subscribe:From; b=mREkkl6W2I+fNKorzPKvBxH3ji7aUQ96VEgmK+yy2poRNcPF7Yp/HO8aCcUsKJeMd YFkgzgr43mS8CEoYlrZGVWpR8MLZnsaSHgOWecExTyvyWPQxj05KjJY9pb1FZQoWFx aTtQUvwjvXOXc+LJRPFIhNHKUQFbeyDs8Q0b5sZs=
Received: from [] (76-218-8-128.lightspeed.sntcca.sbcglobal.net []) (authenticated bits=0) by simon.songbird.com (8.14.4/8.14.4/Debian-4.1ubuntu1) with ESMTP id w1EJPbwJ011203 (version=TLSv1/SSLv3 cipher=AES256-GCM-SHA384 bits=256 verify=NOT) for <ietf-dkim@mipassoc.org>; Wed, 14 Feb 2018 11:25:37 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=bbiw.net; s=default; t=1518636337; bh=sdRthayXHwfq1Z9lbIw+jrqTeSVUND9B4kze5zOLgig=; h=To:From:Subject:Date:From; b=BfD8mSvy2g9E6V9awBu7JbvcNt49bGqSRYBDxGJZBuzhJAJTREt495Q4afyrnjxy4 MdLTsQAca2mtjdwBODYaMYEVv3EA/fZvgckcBO05hpbpoo/pWuo4MruBK3fquz1ZJS VyAIu8w2aSXif2ktxGZ8KFnuebknMCJlYQTLfD/g=
To: DKIM List <ietf-dkim@mipassoc.org>
From: Dave Crocker <dcrocker@bbiw.net>
Organization: Brandenburg InternetWorking
Message-ID: <2fdeee93-1af7-9e67-33bb-c7253ef40be6@bbiw.net>
Date: Wed, 14 Feb 2018 11:24:29 -0800
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0
MIME-Version: 1.0
Content-Language: en-US
Subject: [ietf-dkim] change of venue for ietf-dkim mailing list
X-BeenThere: ietf-dkim@mipassoc.org
X-Mailman-Version: 2.1.16
Precedence: list
List-Id: IETF DKIM Discussion List <ietf-dkim.mipassoc.org>
List-Unsubscribe: <http://mipassoc.org/mailman/options/ietf-dkim>, <mailto:ietf-dkim-request@mipassoc.org?subject=unsubscribe>
List-Archive: <http://mipassoc.org/pipermail/ietf-dkim/>
List-Post: <mailto:ietf-dkim@mipassoc.org>
List-Help: <mailto:ietf-dkim-request@mipassoc.org?subject=help>
List-Subscribe: <http://mipassoc.org/mailman/listinfo/ietf-dkim>, <mailto:ietf-dkim-request@mipassoc.org?subject=subscribe>
Content-Transfer-Encoding: base64
Content-Type: text/plain; charset="utf-8"; Format="flowed"
Errors-To: ietf-dkim-bounces@mipassoc.org
Sender: "ietf-dkim" <ietf-dkim-bounces@mipassoc.org>


I've been very long remiss in responding to a request that the ietf-dkim 
mailing list re-locate, to home on the ietf.org site.  That process is 
now (finally) underway.

It is being done in stages, to try to mitigate against any loss of 
membership entries and/or messages in the archive.

      1. The first step will be creation of the list at the ietf.  (I've 
suggested a list name, but we'll see what they choose.)

      2. Membership in the current list is now set to be moderated and 
I'll decline new members until the list is moved (and then it won't by 
mine to worry about...)

      3. The existing membership will be copied over to the ietf list. 
I've suggested a direct enrolling, without making anyone re-subscribe, 
but again we'll see what ietf ops decides.

      4. After the switch is complete and the list is operational, we'll 
move a copy of the list archive over there.

Dave Crocker
Brandenburg InternetWorking
NOTE WELL: This list operates according to