IETF Logo Mail Archive

Re: [dmarc-ietf] Identification of an email author (was - Re: IETF Mailing Lists and DMARC)

Dave Crocker <dcrocker@gmail.com> Mon, 07 November 2016 22:54 UTC

Return-Path: <dcrocker@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2DD68129B86; Mon, 7 Nov 2016 14:54:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level:
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 lDoDHQ4QlY7q; Mon, 7 Nov 2016 14:54:37 -0800 (PST)
Received: from mail-pf0-x22d.google.com (mail-pf0-x22d.google.com [IPv6:2607:f8b0:400e:c00::22d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6B4C8129B7B; Mon, 7 Nov 2016 14:54:33 -0800 (PST)
Received: by mail-pf0-x22d.google.com with SMTP id 189so97030514pfz.3; Mon, 07 Nov 2016 14:54:33 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:subject:to:references:cc:organization:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=2ARjVzDiyoQH/obHLek8GYHoYHGiQ3TngjQfeb3Ey1g=; b=lrJ1bFmOXQ5N1aem/deF+3JYQGWOX05eW8r4civ4M0MQkFAkBslzXvDd3uSu2BPjeC 7Vf7StrvzY8SSTd3ziRIbUgyWO8BQTioXicavl1K7iq6sCbwGDSG7l35Mwdg9iPm5B9y KZuQqdL7UlyZk+XEbuvHafomwaIH4g3yykw5zY4vtkBDfGj6fHSajgT1tulcxSGqmqbc OHnpxzJCgZtycwOmHec4ToS/umZv1eekMab5AdQi/B6dWjQLNwxXau6He4O7+lP5CWK5 iVIZnFyGHCfwBmCHzE+KxBZwHZ4tb0fjM8cqNGrkQwk5XDV63dp9Y1sQyAdZFo059gGi 1WIg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:subject:to:references:cc:organization :message-id:date:user-agent:mime-version:in-reply-to :content-transfer-encoding; bh=2ARjVzDiyoQH/obHLek8GYHoYHGiQ3TngjQfeb3Ey1g=; b=AqFENuLnjazxlyVzSfgqvpNcmct4wDspUMwHvdiM3TNEYwUEGbNvKQ2dKVcnpcVBU+ /Z6/EIA0yTwtwDgVKv+TvCH8LT2FRmd40zJKfZY8Gwy8Zyw+P7aEpXm8IeoM/BYn4KxQ Mcpr+qZZOB9zmAGoAHr8hc6HAB/6CqWysFrseA6pC6XhVq9P7foHON/tRjGEAIFBopWu W2QdOefS0atDzS/FPN9ADFluq4kUODAtLdge3ngSP0UOGJ7so3EoYxb0nViGYnxcMGGl 0yLJr6M/lvo7Uo2O7SwUiwL85uWODDaLZsT/npEFIEcBLNy163zEUud/IE7vOYgxmrQS vQAQ==
X-Gm-Message-State: ABUngvdwpbiALFm95tCk1RCLhABA3xySiiQipmkQuo9H5AWbW7sAxxZ0xFy2RIlmhXgHIg==
X-Received: by 10.98.196.89 with SMTP id y86mr17456448pff.172.1478559272998; Mon, 07 Nov 2016 14:54:32 -0800 (PST)
Received: from ?IPv6:2602:304:cda0:8800:3c9f:b94c:7e47:7e87? ([2602:304:cda0:8800:3c9f:b94c:7e47:7e87]) by smtp.gmail.com with ESMTPSA id tx10sm43110940pab.40.2016.11.07.14.54.31 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 07 Nov 2016 14:54:32 -0800 (PST)
From: Dave Crocker <dcrocker@gmail.com>
X-Google-Original-From: Dave Crocker <dcrocker@bbiw.net>
Subject: Re: [dmarc-ietf] Identification of an email author (was - Re: IETF Mailing Lists and DMARC)
To: Terry Zink <tzink@exchange.microsoft.com>, Ted Lemon <mellon@fugue.com>
References: <678C2FBA-A661-4556-A300-5C08562B5F8A@iii.ca> <29429.1478113235@obiwan.sandelman.ca> <CABa8R6vHdt75NFKW3s6xOzLcq=jmVAHDPX0tjLRdGpYSTP2cYA@mail.gmail.com> <33b100ac-c035-8b49-22e1-edbe47f41919@dcrocker.net> <CABa8R6u7WbbeXzkhkNM46RYtMSw7V9FT2m_LvKLHaFDvF3cw3A@mail.gmail.com> <CO2PR00MB0103566D260F9BFEC7166C9B96A20@CO2PR00MB0103.namprd00.prod.outlook.com> <5FA03832-D38F-47F2-B974-7C903C7513FD@fugue.com> <CO2PR00MB01034350A8C90A1E039336F796A20@CO2PR00MB0103.namprd00.prod.outlook.com>
Organization: Brandenburg InternetWorking
Message-ID: <4b029229-a08f-15c3-0ba4-74756e1ed1f1@bbiw.net>
Date: Mon, 07 Nov 2016 14:54:25 -0800
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.4.0
MIME-Version: 1.0
In-Reply-To: <CO2PR00MB01034350A8C90A1E039336F796A20@CO2PR00MB0103.namprd00.prod.outlook.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/rlMsBaK5zx1X_5_dG77_fAwgG1g>
Cc: "dmarc@ietf.org" <dmarc@ietf.org>, IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
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>
X-List-Received-Date: Mon, 07 Nov 2016 22:54:39 -0000

On 11/4/2016 2:54 PM, Terry Zink wrote:
> If you hit “Reply-All”, at least when I use Gmail, it includes both the
> From: and the Reply-To using the scheme below (I tested it out just
> now). In Outlook desktop I have to also copy/paste the From: address
> (mailing list). It’s not ideal in Outlook desktop, but I can live with it.
>
> In this email discussion, I hit Reply-All and includes Ted on the To:,
> and dmarc@ietf.org <mailto:dmarc@ietf.org> and ietf@ietf.org
> <mailto:ietf@ietf.org> on the cc.

RFC5322:

> When the "Reply-To:" field is present, it
>    indicates the address(es) to which the author of the message suggests
>    that replies be sent.

and

> In the absence of the "Reply-To:" field,
>    replies SHOULD by default be sent to the mailbox(es) specified in the
>    "From:" field unless otherwise specified by the person composing the
>    reply.


This does not prohibit also sending to the From: address, but it makes 
clear that including the From: address goes against the intent of having 
the Reply-To: field.  So such copying violates the intent of the 
Reply-to field.

That such behavior is common doesn't make it a good choice.

d/


-- 

   Dave Crocker
   Brandenburg InternetWorking
   bbiw.net

v2.23.0 | Report a Bug | By Email