Re: [dmarc-ietf] DMARC-Compliant Mailing Lists

Alessandro Vesely <vesely@tana.it> Thu, 07 October 2021 09:37 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 251083A0C60 for <dmarc@ietfa.amsl.com>; Thu, 7 Oct 2021 02:37:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.089
X-Spam-Level:
X-Spam-Status: No, score=-2.089 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.001, RCVD_IN_MSPIKE_WL=0.001, SPF_PASS=-0.001, T_FILL_THIS_FORM_SHORT=0.01, 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 px-wNdHMCjFr for <dmarc@ietfa.amsl.com>; Thu, 7 Oct 2021 02:37:49 -0700 (PDT)
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 E54EC3A0C5E for <dmarc@ietf.org>; Thu, 7 Oct 2021 02:37:48 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tana.it; s=delta; t=1633599463; bh=oSKsjnsOyQAZhVbiiEAMqFtNuEZVtOpg+nfC2Dn6xeM=; l=2404; h=To:References:From:Date:In-Reply-To; b=COjrjWTazz/430Se3DXVNXwjpFEvlP3OnzjxbXlH9bKt2FRH9JnoVpfq/XOHNcpIk kI4ShHYffvRlKO+WdqRiEMKyRgwlYcli6KmNBkQTUm7DH+p7mASndRSyeQI+bi79M1 7qma2CXhG/G7NWLVJ8FRwoc9MyCXs8eBmlKjPiRSp4gYd7eRVLr+89YZRZBUx
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 00000000005DC008.00000000615EBFE7.00006B7C; Thu, 07 Oct 2021 11:37:43 +0200
To: dmarc@ietf.org
References: <20211006233727.24C1429DC897@ary.qy> <3FEEBDB4-D559-49FB-AFC6-3C7298F63ED6@kitterman.com> <56B7A1D4-B683-47D3-8871-2A1F283FA464@wordtothewise.com>
From: Alessandro Vesely <vesely@tana.it>
Message-ID: <c1e199f1-0c91-9c39-1479-e9ba76af493e@tana.it>
Date: Thu, 07 Oct 2021 11:37:43 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.11.0
MIME-Version: 1.0
In-Reply-To: <56B7A1D4-B683-47D3-8871-2A1F283FA464@wordtothewise.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/40a5ud9ij6kX08vKipHxHsdCYIw>
Subject: Re: [dmarc-ietf] DMARC-Compliant Mailing Lists
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: Thu, 07 Oct 2021 09:37:54 -0000

On Thu 07/Oct/2021 09:48:12 +0200 Laura Atkins wrote:
>> On 7 Oct 2021, at 01:08, Scott Kitterman <sklist@kitterman.com> wrote:
>> On October 6, 2021 11:37:26 PM UTC, John Levine <johnl@taugh.com> wrote:
>>> It appears that Alessandro Vesely  <vesely@tana.it> said:
>>>> Doug's emphasis on aliases tends to give that impression.  Otherwise it can 
>>>> finally be a much needed attempt at formalizing the old, known From: rewriting.
>>> 
>>> To point out what I would think is obvious, formalizing a bad idea doesn't make
>>> it any less bad an idea.
>> 
>> Agreed.
>> 
>> To give a specific example:
>> 
>> The mobile mail client I use (K-9 Mail) will either display friendly name or email address.  Due to the compact user interface, both isn't an option.
>> 
>> There's one Google Group I'm a member of with a number of users with DMARC p=reject domains, so their addresses are rewritten to the list address.  As a result, when people don't bother to say who they are in a message, I end up digging through the message header to find out who wrote it.
>> 
>> This is not a good user experience.  It's not salvageable.
> 
> Agreed. The other day I was trying to refer work to a colleague I’ve only really interacted with on a professional mailing list. Due to header re-writing and no email address in any other place in the email, I didn’t actually have a direct email address for her.
> 
> It’s also become almost impossible to search for messages from some people in some clients because you can’t search on from: address any longer.
> 
> These are usability and UX problems induced by DMARC.


What do we want to do, then?

Let's exclude, for the sake of reality, both dropping DMARC altogether and 
stopping to use mailing lists.  What realistic possibilities are there?

ARC, when 60% of receivers will have (reliably) implemented it?  This is not 
more realistic than the Vernon's kook I cited upstream.

After careful consideration, header re-writing doesn't have to imply no email 
address in any other place.  Savvy lists save the original From: in Reply-To: 
or Cc:.  If some lists don't do that, perhaps specifying how to re-write From: 
can improve that condition, no?  When everything is done well, it is possible 
to unmunge From: and fully recover pre-DMARC functionality while still enjoying 
DMARC checks.


Do you see other possibilities?


Best
Ale
--