IETF Logo Mail Archive

Re: Enabling DMARC workaround code for all IETF/IRTF mailing lists

Alessandro Vesely <vesely@tana.it> Sun, 13 May 2018 11:50 UTC

Return-Path: <vesely@tana.it>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7AA5D127077 for <ietf@ietfa.amsl.com>; Sun, 13 May 2018 04:50:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.301
X-Spam-Level:
X-Spam-Status: No, score=-4.301 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-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 In6qGAntByqZ for <ietf@ietfa.amsl.com>; Sun, 13 May 2018 04:50:26 -0700 (PDT)
Received: from wmail.tana.it (wmail.tana.it [62.94.243.226]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 70C1B124BFA for <ietf@ietf.org>; Sun, 13 May 2018 04:50:26 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tana.it; s=gamma; t=1526212223; bh=tKMGKL81hcD7OYcVylq7dn8QQhi+bQaGkMCTOZDgrR4=; l=1593; h=To:References:From:Date:In-Reply-To; b=CzZvooJ69lbtRRpIbzPADB3oWAvoI2wtxtUV7U8eu2rg9wXVNItrWNiRR+W5INnFu xaZjdyc0Tit2JQJnUTWGZDRPpLr4O+8VE4Ip/k7s2UlDglzi5QJ+gqMt58p/JkZiRT 9NpXBj4v4mes8WBR3PmT8zgpbdDTumJtsV170ufydgOKt8pmSIS5aquIHgNbn
Authentication-Results: tana.it; auth=pass (details omitted)
Received: from [172.25.197.111] (pcale.tana [172.25.197.111]) (AUTH: CRAM-MD5 uXDGrn@SYT0/k) by wmail.tana.it with ESMTPA; Sun, 13 May 2018 13:50:23 +0200 id 00000000005DC077.000000005AF8267F.00004C04
Subject: Re: Enabling DMARC workaround code for all IETF/IRTF mailing lists
To: Alexey Melnikov <aamelnikov@fastmail.fm>, ietf@ietf.org
References: <919855CA-9F77-420A-8B8F-79174CD2FC19@fastmail.fm>
From: Alessandro Vesely <vesely@tana.it>
Openpgp: id=0A5B4BB141A53F7F55FC8CBCB6ACF44490D17C00
Message-ID: <5849b364-ee61-6c0c-4905-b7bca88d2fd3@tana.it>
Date: Sun, 13 May 2018 13:50:23 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.7.0
MIME-Version: 1.0
In-Reply-To: <919855CA-9F77-420A-8B8F-79174CD2FC19@fastmail.fm>
Content-Type: text/plain; charset="utf-8"
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/bptFored_pOnAQKvYX-VtwYcxVU>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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: Sun, 13 May 2018 11:50:29 -0000

Just a couple of notes:

On Fri 11/May/2018 14:00:15 +0200 Alexey Melnikov wrote: 
> 
> Below are some technical details on how the email address rewriting workaround is going to work:
> 
> Emails from domains that don't have a p=reject DMARC setting are not going to be affected in any way.
> 
> For emails from p=reject domains:

Some put p=reject; pct=0; for the sole purpose of having From: rewritten.  The
principle of least surprise would suggest to apply rewriting uniformly.

> - The From header field of such emails will be rewritten to be under
> @dmarc.ietf.org domain (which will have a p=none policy). For example,
> "alexey@example.com" email address would become
> "alexey=40example.com@dmarc.ietf.org". The original From header field will
> be preserved in the X-Original-From header field, which can be used for
> automatic message processing by Sieve and Mail User Agents.
Besides encoding, the semantic of alexey=40example.com@dmarc.ietf.org will
never be clear, even to those familiar with DMARC.  My experience after
replying "all" on one of those messages was not what I expected, and I couldn't
tell if that was a bug[*].  How about just appending the original address to
Reply-To[**]: and keep the From: address as simple as dmarc@ietf.org?

jm2c
Ale
-- 

[*] IIRC, my reply was duplicated and one of those messages had three DKIM
signatures bearing d=ietf.org; s=ietf1; rather than the usual two ones.


[**] Or a brand new field such as List-Reply-To:, when we'll standardize
rewriting  --no, I don't think it's going to go away with ARC.

v2.23.0 | Report a Bug | By Email