Re: [dmarc-ietf] ARC vs reject

Alessandro Vesely <vesely@tana.it> Tue, 08 December 2020 12:52 UTC

Return-Path: <vesely@tana.it>
X-Original-To: dmarc@ietfa.amsl.com
Delivered-To: dmarc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 85C1F3A0D2F for <dmarc@ietfa.amsl.com>; Tue, 8 Dec 2020 04:52:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.121
X-Spam-Level:
X-Spam-Status: No, score=-2.121 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, NICE_REPLY_A=-0.001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1152-bit key) header.d=tana.it
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 sypjod1A9STG for <dmarc@ietfa.amsl.com>; Tue, 8 Dec 2020 04:52:01 -0800 (PST)
Received: from wmail.tana.it (wmail.tana.it [62.94.243.226]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0C3F03A0D25 for <dmarc@ietf.org>; Tue, 8 Dec 2020 04:52:00 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tana.it; s=delta; t=1607431918; bh=Apet6lAi0L03ycYIRINCGDHgv45UF3QI1y/fW02RidE=; l=895; h=To:References:From:Date:In-Reply-To; b=DP3y/GCoiYWvbO06e+PUN/H5HVwJMoHGa6QdWCOn+RU7Q6cPGOXqgj21i3F8D/iGc NvXksAM34JtMr2FVuXAi8wwhyp808ckdgm8jfZGfvbjfkZZs784pLWLGW2Npkq5G5H HOb4nUqDrc+n+TctxEGs8TXccVGLI+JKMrIsZS2Z0QV6BRRM0ZI9O/GPesFyO
Authentication-Results: tana.it; auth=pass (details omitted)
Original-From: Alessandro Vesely <vesely@tana.it>
Received: from [172.25.197.111] (pcale.tana [172.25.197.111]) (AUTH: CRAM-MD5 uXDGrn@SYT0/k, TLS: TLS1.3, 128bits, ECDHE_RSA_AES_128_GCM_SHA256) by wmail.tana.it with ESMTPSA id 00000000005DC0CD.000000005FCF76EE.000015EC; Tue, 08 Dec 2020 13:51:58 +0100
To: John Levine <johnl@taugh.com>, dmarc@ietf.org
References: <20201207191959.6D772292166A@ary.qy>
From: Alessandro Vesely <vesely@tana.it>
Message-ID: <d6c6715b-9760-d846-2e99-38ff91a67add@tana.it>
Date: Tue, 8 Dec 2020 13:51:58 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.12.0
MIME-Version: 1.0
In-Reply-To: <20201207191959.6D772292166A@ary.qy>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/JTXqYhpgQ96jufbFtzqn8O6nU8s>
Subject: Re: [dmarc-ietf] ARC vs reject
X-BeenThere: dmarc@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Domain-based Message Authentication, Reporting, and Compliance \(DMARC\)" <dmarc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dmarc>, <mailto:dmarc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dmarc/>
List-Post: <mailto:dmarc@ietf.org>
List-Help: <mailto:dmarc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dmarc>, <mailto:dmarc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 08 Dec 2020 12:52:10 -0000

On Mon 07/Dec/2020 20:19:59 +0100 John Levine wrote:
> In article <b069e7c1-51a8-4550-76a9-c7e78f04c780@tana.it> you write:
>>    Compared with the use of "l=" tag (Section 8.2 of [RFC6376]), the
>>    fact that footers are written in plain text ...
> 
> They are?  Some are, some are added as MIME parts.


The Content-Type: of the added MIME part, in that case.


> We really need to keep in mind that there is a lot of list management
> software with a vast array of configuration options.


The idea of the draft is that being reversible is a MLM configuration option.

The simplest case is that of lists that don't modify messages at all.  Nothing 
to revert in this case.

We can extend that case so as to include the addition of a simple footer and a 
subject tag.  That way, at least, we can discuss DMARC standardization on a 
DMARC-compliant mailing list.


Best
Ale
--