Re: [ietf-822] (DMARC) We've been here before, was Why mailing lists
"John Levine" <johnl@taugh.com> Fri, 18 April 2014 01:38 UTC
Return-Path: <johnl@iecc.com>
X-Original-To: ietf-822@ietfa.amsl.com
Delivered-To: ietf-822@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BD4A31A01D4 for <ietf-822@ietfa.amsl.com>; Thu, 17 Apr 2014 18:38:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.357
X-Spam-Level:
X-Spam-Status: No, score=-0.357 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HELO_MISMATCH_COM=0.553, HOST_MISMATCH_NET=0.311, SPF_NEUTRAL=0.779] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id byljdhddoUDQ for <ietf-822@ietfa.amsl.com>; Thu, 17 Apr 2014 18:38:02 -0700 (PDT)
Received: from miucha.iecc.com (abusenet-1-pt.tunnel.tserv4.nyc4.ipv6.he.net [IPv6:2001:470:1f06:1126::2]) by ietfa.amsl.com (Postfix) with ESMTP id BE89B1A0148 for <ietf-822@ietf.org>; Thu, 17 Apr 2014 18:37:59 -0700 (PDT)
Received: (qmail 22177 invoked from network); 18 Apr 2014 01:37:55 -0000
Received: from miucha.iecc.com (64.57.183.18) by mail1.iecc.com with QMQP; 18 Apr 2014 01:37:55 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:reply-to:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=ae4.535081f3.k1404; i=johnl@user.iecc.com; bh=xI4Q9fA/refsOLIPiJtYgIg4JpO01fSqgTQrJuiQN+M=; b=cbwd7lf5YzeMPuUrGO+1Q68ecoRVe5FJO3rNFuTQCWCFvQdAnOJRmZN3JTYy8b9dUVS1UNpdJb/tPDrPXku/+cjdLYfDA/gJque5GbsFF5N1WkKdANraD4zJL9ZBmcDfQ8Xy9XrqxFHqr049QmVnul9nZsUSmUg496fIxyUtslnNig/jKfRwhIASTCdhPbeOhGmH0B6H55jRP2NyU/v0ObREWaFcuyCrBWuePrUu9l3v/8r9a1wtzmR5uPawZxeF
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:reply-to:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=ae4.535081f3.k1404; olt=johnl@user.iecc.com; bh=xI4Q9fA/refsOLIPiJtYgIg4JpO01fSqgTQrJuiQN+M=; b=ceHcDD8vx5H9meFdC4CzSq76aGvsb5qMXehROpCjhwXL6HYpDj4pSk47TbA2KURbGuM55iIdlxheClO7WCepbhOKzdGAXkCuGXxxn2smzifOQeTuMg2+4eizw//CM3tv+K18XfP9C4Dh4j26pOWwK3iAqQRy8qKSc/WFig2111SQdA6d92HPA2pvgX4c8lqSqHcEoacNMlyjSMwHspkOqEGon/aVsJHorSAHepi2PMuh8cNjPZERLgXUUIKyfc8n
Date: Fri, 18 Apr 2014 01:37:33 -0000
Message-ID: <20140418013733.2787.qmail@joyce.lan>
From: John Levine <johnl@taugh.com>
To: ietf-822@ietf.org
In-Reply-To: <01P6QXI47QVW00004W@mauve.mrochek.com>
Organization:
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset="utf-8"
Content-transfer-encoding: 8bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf-822/XfJpuVOmja9O_CiqacdI__746yU
Cc: ietf@ietf.org
Subject: Re: [ietf-822] (DMARC) We've been here before, was Why mailing lists
X-BeenThere: ietf-822@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: ietf-822@ietf.org
List-Id: "Discussion of issues related to Internet Message Format \[RFC 822, RFC 2822, RFC 5322\]" <ietf-822.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-822>, <mailto:ietf-822-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf-822/>
List-Post: <mailto:ietf-822@ietf.org>
List-Help: <mailto:ietf-822-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-822>, <mailto:ietf-822-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 18 Apr 2014 01:38:02 -0000
>> We're now *way* into technical discussion. Let's take those to >> https://www.ietf.org/mailman/listinfo/dmarc shall we? > >How about we take it some place else? I really don't want this intermingled >with discussions of things like how to revise the current DMARC specifications >that hopefully are taking place on that list. Let's take it to ietf-822 since it seems to be about stuff we'd stick into message headers. R's, John