Re: (DMARC) Why mailing lists are only sort of special

mrex@sap.com (Martin Rex) Thu, 17 April 2014 13:11 UTC

Return-Path: <mrex@sap.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 325DA1A0168 for <ietf@ietfa.amsl.com>; Thu, 17 Apr 2014 06:11:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.552
X-Spam-Level:
X-Spam-Status: No, score=-6.552 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_HI=-5, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
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 sZq15Ul56BKg for <ietf@ietfa.amsl.com>; Thu, 17 Apr 2014 06:11:40 -0700 (PDT)
Received: from smtpde01.sap-ag.de (smtpde01.sap-ag.de [155.56.68.170]) by ietfa.amsl.com (Postfix) with ESMTP id 417DB1A013C for <ietf@ietf.org>; Thu, 17 Apr 2014 06:11:40 -0700 (PDT)
Received: from mail05.wdf.sap.corp by smtpde01.sap-ag.de (26) with ESMTP id s3HDBYvT028190 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Thu, 17 Apr 2014 15:11:34 +0200 (MEST)
Subject: Re: (DMARC) Why mailing lists are only sort of special
In-Reply-To: <B3467912-BDCA-4AE8-9939-60013DA99267@gmail.com>
To: Yoav Nir <ynir.ietf@gmail.com>
Date: Thu, 17 Apr 2014 15:11:34 +0200 (CEST)
X-Mailer: ELM [version 2.4ME+ PL125 (25)]
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="US-ASCII"
Message-Id: <20140417131134.5CEFC1ACCF@ld9781.wdf.sap.corp>
From: mrex@sap.com (Martin Rex)
X-SAP: out
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/l7-hGTZEgzWysDGwy3mFUnnfMiI
Cc: "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: mrex@sap.com
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: <http://www.ietf.org/mail-archive/web/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: Thu, 17 Apr 2014 13:11:47 -0000

Yoav Nir wrote:
> 
> On Apr 17, 2014, at 9:35 AM, Dave Cridland <dave@cridland.net> wrote:
>> 
>> Right now, my MUA treats this as a message
>> "From John R Levine <johnl@taugh.com>"m>". This means that any policy
>> on the message origination comes from looking solely at the taugh.com
>> domain. We'll pretend it has a DMARC policy. Herein lies the
>> Yahoo/DMARC issue, because unless your policy essentially stipulates
>> that the IETF is allowed to spoof you, we're stuck.
> 
> Then perhaps this is what needs to change. John R Levine did not send
> you a message. He sent a message to the list. It is the list software
> that sent you a message. So perhaps the From field should have been
> ?From: IETF Mailing list on behalf of John R Levine <ietf@ietf.org>?g>?.

But that is EXACTLY what the IETF mailing list exploder *IS* doing
exactly as it has been specified for ages:

https://tools.ietf.org/html/rfc822#section-4.4.2
https://tools.ietf.org/html/rfc822#appendix-A.2

https://tools.ietf.org/html/rfc5322#section-3.6.2

            The "From:" field specifies the author(s) of the message,
   that is, the mailbox(es) of the person(s) or system(s) responsible
   for the writing of the message.  The "Sender:" field specifies the
   mailbox of the agent responsible for the actual transmission of the
   message. 

  From: Yoav Nir <ynir.ietf@gmail.com>
  Subject: Re: (DMARC) Why mailing lists are only sort of special
  Errors-To: ietf-bounces@ietf.org
  Sender: ietf <ietf-bounces@ietf.org>
  Date: Thu, 17 Apr 2014 13:50:30 +0300
  Message-ID: <B3467912-BDCA-4AE8-9939-60013DA99267@gmail.com>
  To: Dave Cridland <dave@cridland.net>
  CC: "ietf@ietf.org" <ietf@ietf.org>


Something as old as Outlook 2003 will properly display a message
that is received with a "Sender:" as "<Sender> on behalf of <From>"


-Martin