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

John C Klensin <john-ietf@jck.com> Mon, 14 April 2014 14:37 UTC

Return-Path: <john-ietf@jck.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 C6B0E1A02F7 for <ietf@ietfa.amsl.com>; Mon, 14 Apr 2014 07:37:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.872
X-Spam-Level:
X-Spam-Status: No, score=-2.872 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.272] 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 rYVrKzw_lDsz for <ietf@ietfa.amsl.com>; Mon, 14 Apr 2014 07:37:22 -0700 (PDT)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id C04D01A02F5 for <ietf@ietf.org>; Mon, 14 Apr 2014 07:37:22 -0700 (PDT)
Received: from [198.252.137.115] (helo=JcK-HP8200.jck.com) by bsa2.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1WZi0b-0004yg-HR; Mon, 14 Apr 2014 10:37:17 -0400
Date: Mon, 14 Apr 2014 10:37:12 -0400
From: John C Klensin <john-ietf@jck.com>
To: Dave Crocker <dcrocker@bbiw.net>, Doug Barton <dougb@dougbarton.us>, ietf@ietf.org
Subject: Re: DMARC: perspectives from a listadmin of large open-source lists
Message-ID: <641C1E5EF4C1D458FF909DAF@JcK-HP8200.jck.com>
In-Reply-To: <534BEF75.5060804@bbiw.net>
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> <534BEF75.5060804@bbiw.net>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-SA-Exim-Connect-IP: 198.252.137.115
X-SA-Exim-Mail-From: john-ietf@jck.com
X-SA-Exim-Scanned: No (on bsa2.jck.com); SAEximRunCond expanded to false
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/VjUR4a3GR4OK9I_NouyPGUBHFKI
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:37:28 -0000

--On Monday, April 14, 2014 07:23 -0700 Dave Crocker
<dcrocker@bbiw.net> wrote:

> 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.

Yes.

     john