Re: DMARC: perspectives from a listadmin of large open-source lists

Dave Crocker <dcrocker@bbiw.net> Mon, 14 April 2014 14:25 UTC

Return-Path: <dcrocker@bbiw.net>
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 AFBC11A0491 for <ietf@ietfa.amsl.com>; Mon, 14 Apr 2014 07:25:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3] 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 ViDWXluqYu5N for <ietf@ietfa.amsl.com>; Mon, 14 Apr 2014 07:25:54 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id CDDBD1A03EB for <ietf@ietf.org>; Mon, 14 Apr 2014 07:25:54 -0700 (PDT)
Received: from [192.168.1.66] (76-218-8-156.lightspeed.sntcca.sbcglobal.net [76.218.8.156]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id s3EEPmkd009424 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Mon, 14 Apr 2014 07:25:51 -0700
Message-ID: <534BEF75.5060804@bbiw.net>
Date: Mon, 14 Apr 2014 07:23:49 -0700
From: Dave Crocker <dcrocker@bbiw.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.4.0
MIME-Version: 1.0
To: John C Klensin <john-ietf@jck.com>, Doug Barton <dougb@dougbarton.us>, ietf@ietf.org
Subject: Re: DMARC: perspectives from a listadmin of large open-source lists
References: <20140414024956.26078.qmail@joyce.lan> <534B524F.4050206@dcrocker.net> <alpine.BSF.2.00.1404132327560.26258@joyce.lan> <E0B7196CB2603B80BBEC21AF@JcK-HP8200.jck.com> <alpine.BSF.2.00.1404132346420.26386@joyce.lan> <1EBDF5239EEE5202D3837D25@JcK-HP8200.jck.com> <534B9760.90301@dougbarton.us> <6C80882F19CCEDFE15E987CA@JcK-HP8200.jck.com>
In-Reply-To: <6C80882F19CCEDFE15E987CA@JcK-HP8200.jck.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.67]); Mon, 14 Apr 2014 07:25:52 -0700 (PDT)
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/lky21iDSk03dDw7iWwg9OVkfTGo
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
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: <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: Mon, 14 Apr 2014 14:25:59 -0000

On 4/14/2014 2:14 AM, John C Klensin wrote:
> There is a strong rule in RFC 5321 and its predecessor
> forbidding anything but the final delivery system from rewriting
> a local-part and it is there precisely because one doesn't know
> what sorts of conventions and indicates were begin used there.


Just to avoid possible confusion about the implications of the above:

      Mediators, like mailing lists, take final delivery and post a new 
message.  In formal terms, it's legitimate for them to create a 
different rfc5322.From field, including one that looks like some sort of 
'rewrite' of the one used by the original author.

d/

-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net