Re: [Tools-discuss] Step backwards: <noreply@ietf.org>

Henrik Levkowetz <henrik@levkowetz.com> Wed, 13 March 2019 03:57 UTC

Return-Path: <henrik@levkowetz.com>
X-Original-To: tools-discuss@ietfa.amsl.com
Delivered-To: tools-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2EAE3127970 for <tools-discuss@ietfa.amsl.com>; Tue, 12 Mar 2019 20:57:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
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 iabHLHL-KWir for <tools-discuss@ietfa.amsl.com>; Tue, 12 Mar 2019 20:57:36 -0700 (PDT)
Received: from zinfandel.tools.ietf.org (zinfandel.tools.ietf.org [IPv6:2001:1890:126c::1:2a]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 731EA12788D for <tools-discuss@ietf.org>; Tue, 12 Mar 2019 20:57:36 -0700 (PDT)
Received: from h-202-242.a357.priv.bahnhof.se ([158.174.202.242]:62970 helo=tannat.localdomain) by zinfandel.tools.ietf.org with esmtpsa (TLS1.2:DHE_RSA_AES_128_CBC_SHA1:128) (Exim 4.80) (envelope-from <henrik@levkowetz.com>) id 1h3v1L-0004dE-Mj; Tue, 12 Mar 2019 20:57:36 -0700
To: Patrik Fältström <paf=40frobbit.se@dmarc.ietf.org>
References: <186f4ff4-e31e-80c6-600f-9521694734f0@gmail.com> <656168f7-ed79-e19e-ea73-433cd9b49994@levkowetz.com> <AF03E2FC-A1F4-4585-B40F-9A263035D7BC@frobbit.se>
Cc: tools-discuss@ietf.org
From: Henrik Levkowetz <henrik@levkowetz.com>
Message-ID: <5eee9abc-4919-d3f3-9d5c-ec05823cf479@levkowetz.com>
Date: Wed, 13 Mar 2019 04:57:27 +0100
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
In-Reply-To: <AF03E2FC-A1F4-4585-B40F-9A263035D7BC@frobbit.se>
Content-Type: multipart/signed; micalg="pgp-sha256"; protocol="application/pgp-signature"; boundary="OBkn2U2mCf7AhclHohUM1x2hlEFud31jH"
X-SA-Exim-Connect-IP: 158.174.202.242
X-SA-Exim-Rcpt-To: tools-discuss@ietf.org, paf=40frobbit.se@dmarc.ietf.org
X-SA-Exim-Mail-From: henrik@levkowetz.com
X-SA-Exim-Version: 4.2.1 (built Mon, 26 Dec 2011 16:24:06 +0000)
X-SA-Exim-Scanned: Yes (on zinfandel.tools.ietf.org)
X-Clacks-Overhead: GNU Terry Pratchett
Archived-At: <https://mailarchive.ietf.org/arch/msg/tools-discuss/5HQvWzvvaPFVswRItYP4rddBqys>
Subject: Re: [Tools-discuss] Step backwards: <noreply@ietf.org>
X-BeenThere: tools-discuss@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF Tools Discussion <tools-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tools-discuss>, <mailto:tools-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tools-discuss/>
List-Post: <mailto:tools-discuss@ietf.org>
List-Help: <mailto:tools-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tools-discuss>, <mailto:tools-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 13 Mar 2019 03:57:38 -0000

Hi Patrik,

On 2019-03-13 00:25, Patrik Fältström wrote:
> On 13 Mar 2019, at 8:19, Henrik Levkowetz wrote:
> 
>> I believe this will make Reply and Reply All work as before, while
>> still avoiding the troubles we've seen from using a From: address
>> that may look like a forgery.
> 
> May I suggest stopping changing the body of the email messages (by
> adding a footer). That way DKIM signatures will work, and the email
> will indeed not be defined being forgery which in fact they are as
> long as the body is changed.

That is a different issue (that will hopefully be solved by ARC, which
we hope to deploy soon).

Brian is talking about a recent change away from a practice where
when a reviewer would enter his review into the datatracker, it would
originate a mail purporting to be from <reviewer@reviewers.domain>,
and send that out from the server mail.ietf.org, which is not mentioned
in the SPF record of reviewers.domain.

Since this was becoming increasingly troublesome, as more and more
domains were adopting stricter SPF settings, we've stopped sending
mail purporting to be sent by <reviewer@reviewers.domain>, and are
now sending from <noreply@ietf.org>, but we missed adding a Reply-To:
header field that would make replies work as before.

Regards,

	Henrik