[tcpm] FW: Enabling DMARC workaround code for all IETF/IRTF mailing lists

"Scharf, Michael (Nokia - DE/Stuttgart)" <michael.scharf@nokia.com> Fri, 11 May 2018 11:54 UTC

Return-Path: <michael.scharf@nokia.com>
X-Original-To: tcpm@ietfa.amsl.com
Delivered-To: tcpm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7111D126C25 for <tcpm@ietfa.amsl.com>; Fri, 11 May 2018 04:54:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.911
X-Spam-Level:
X-Spam-Status: No, score=-1.911 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=nokia.onmicrosoft.com
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 ruj5Fns8TO5g for <tcpm@ietfa.amsl.com>; Fri, 11 May 2018 04:54:05 -0700 (PDT)
Received: from EUR01-VE1-obe.outbound.protection.outlook.com (mail-ve1eur01on0119.outbound.protection.outlook.com [104.47.1.119]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B10C7124B0A for <tcpm@ietf.org>; Fri, 11 May 2018 04:54:04 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nokia.onmicrosoft.com; s=selector1-nokia-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=+5mQhgSygvH+2Q5RVtfAXsDGJ7yoID9fdqx/vvzYlqo=; b=QJU6jsekwZm++fnw+YEAuPkzZbyffgYu8bAvWTW2M547E+NXWZ0X8ucjG6Kl/qFbHXqOVwAZI7q4h81c/Sf5D3fPKNCY1BqDNLkPI29WvPGdrcPtY3lp2XeX+YQQbpUwe5EBv8xqL0RiHp6VICPQkzVurmw2w+H7Kh2XUY4qsYs=
Received: from AM5PR0701MB2547.eurprd07.prod.outlook.com (10.173.92.15) by AM5PR0701MB2979.eurprd07.prod.outlook.com (10.168.156.141) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.776.4; Fri, 11 May 2018 11:54:02 +0000
Received: from AM5PR0701MB2547.eurprd07.prod.outlook.com ([fe80::a1ee:77c0:a9c5:977e]) by AM5PR0701MB2547.eurprd07.prod.outlook.com ([fe80::a1ee:77c0:a9c5:977e%5]) with mapi id 15.20.0755.012; Fri, 11 May 2018 11:54:02 +0000
From: "Scharf, Michael (Nokia - DE/Stuttgart)" <michael.scharf@nokia.com>
To: "tcpm@ietf.org" <tcpm@ietf.org>
Thread-Topic: Enabling DMARC workaround code for all IETF/IRTF mailing lists
Thread-Index: AQHT6R4CMQODohl6S0i5BdJOGDl0Q6Qqap6Q
Date: Fri, 11 May 2018 11:54:02 +0000
Message-ID: <AM5PR0701MB2547EB54CF3E54CA656742D4939F0@AM5PR0701MB2547.eurprd07.prod.outlook.com>
References: <919855CA-9F77-420A-8B8F-79174CD2FC19@fastmail.fm>
In-Reply-To: <919855CA-9F77-420A-8B8F-79174CD2FC19@fastmail.fm>
Accept-Language: en-US, de-DE
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
msip_labels:
authentication-results: spf=none (sender IP is ) smtp.mailfrom=michael.scharf@nokia.com;
x-originating-ip: [92.203.149.190]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; AM5PR0701MB2979; 7:aEYTjjq490EbuKS/9Tog+FwrxZmjEXfpwwY+iR8+Q14c13j9OGWI9vVS/6PV3TqvXWSo7KXZiWg7VNxzMu2hemqXBXm9akrai1pLSKkWcmDBDLUAHSzmiLGULEw7VoCICFZGPbammQ5AjKt0V8z2D+fxNocfFJ8FJRppRaD6hk+th6N12nlewBHDbG1BfVDW0+c5Ed4fEXdZVbRJcGJncF+pJfOlEmRww0W7h28Sx835TuY8JtpsNM+7UlJIKue8
x-ms-exchange-antispam-srfa-diagnostics: SOS;
x-ms-office365-filtering-ht: Tenant
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(7020095)(4652020)(8989080)(4534165)(4627221)(201703031133081)(201702281549075)(8990040)(5600026)(48565401081)(2017052603328)(7193020); SRVR:AM5PR0701MB2979;
x-ms-traffictypediagnostic: AM5PR0701MB2979:
x-microsoft-antispam-prvs: <AM5PR0701MB2979FF2C9351256D9A9900F9939F0@AM5PR0701MB2979.eurprd07.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:;
x-ms-exchange-senderadcheck: 1
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(6040522)(2401047)(8121501046)(5005006)(3002001)(10201501046)(93006095)(93001095)(3231254)(11241501184)(806099)(944501410)(52105095)(6055026)(149027)(150027)(6041310)(20161123558120)(20161123564045)(20161123562045)(201703131423095)(201702281528075)(20161123555045)(201703061421075)(201703061406153)(20161123560045)(6072148)(201708071742011); SRVR:AM5PR0701MB2979; BCL:0; PCL:0; RULEID:; SRVR:AM5PR0701MB2979;
x-forefront-prvs: 06691A4183
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(39860400002)(376002)(396003)(39380400002)(366004)(346002)(199004)(189003)(13464003)(69234005)(6506007)(55016002)(53546011)(9686003)(2473003)(14454004)(53936002)(5640700003)(316002)(478600001)(97736004)(26005)(2351001)(2501003)(186003)(229853002)(33656002)(102836004)(105586002)(5250100002)(476003)(66066001)(11346002)(446003)(86362001)(2906002)(486006)(305945005)(74316002)(7736002)(76176011)(8676002)(2900100001)(6916009)(1730700003)(8936002)(81166006)(81156014)(6436002)(6116002)(68736007)(106356001)(3660700001)(3846002)(99286004)(25786009)(7696005)(3280700002)(5660300001)(197153002); DIR:OUT; SFP:1102; SCL:1; SRVR:AM5PR0701MB2979; H:AM5PR0701MB2547.eurprd07.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:1; MX:1;
received-spf: None (protection.outlook.com: nokia.com does not designate permitted sender hosts)
x-microsoft-antispam-message-info: PGCcENf0oujt0zxMMlVjMwbHGsmKekoCQ58NJ805oWaUWlIq5B5d8/phJCfrG7cfWAoLYqwwEVarWFFg+iQqpR5UDalfpym2IVruJY2iJml6oBR+G1EKXz0PwXLOntv8PHw9uZWaI8x0mZNN0BVJTsgL30baprgdpGgYBd9AxIfX/JiLuUjuOIySWOsqT/WGd7KNiuwKkFKtMvRxybZuo4abYqXO8g8gMxJOHDi/694=
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-MS-Office365-Filtering-Correlation-Id: 72952bd9-4905-4862-bf15-08d5b735e3ac
X-OriginatorOrg: nokia.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 72952bd9-4905-4862-bf15-08d5b735e3ac
X-MS-Exchange-CrossTenant-originalarrivaltime: 11 May 2018 11:54:02.2170 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 5d471751-9675-428d-917b-70f44f9630b0
X-MS-Exchange-Transport-CrossTenantHeadersStamped: AM5PR0701MB2979
Archived-At: <https://mailarchive.ietf.org/arch/msg/tcpm/KvffHj41nYl4tdLyPPvj93pJREg>
Subject: [tcpm] FW: Enabling DMARC workaround code for all IETF/IRTF mailing lists
X-BeenThere: tcpm@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: TCP Maintenance and Minor Extensions Working Group <tcpm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tcpm>, <mailto:tcpm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tcpm/>
List-Post: <mailto:tcpm@ietf.org>
List-Help: <mailto:tcpm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcpm>, <mailto:tcpm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 11 May 2018 11:54:07 -0000

FYI

I believe that, unfortunately, some TCPM list subscribers had issues with this in the past, and e.g. got unsubscribed. That was never a TCPM-specific problem.

I am myself not familiar with the technical details, and TCPM is not the right list to discuss this...

Michael


-----Original Message-----
From: ietf [mailto:ietf-bounces@ietf.org] On Behalf Of Alexey Melnikov
Sent: Friday, May 11, 2018 2:00 PM
To: ietf@ietf.org
Subject: Enabling DMARC workaround code for all IETF/IRTF mailing lists

Hi,
Many of you have seen several long discussions thread about DMARC and how it affects use of IETF/IRTF mailing lists.

After testing DMARC workaround code written by Henrik Levkowetz on several high volume IETF and IRTF mailing lists (e.g. CFRG, WebRTC, DMARC, QUIC), the tools team and the IESG decided that Henrik's code should be deployed for all IETF and IRTF mailing lists. In particular the workaround allows people from DMARC p=reject domains to participate in IETF mailing lists, as well as to avoid the problem of recipients being unsubscribed from mailing lists. These 2 issues were the main reasons for developing the DMARC workaround code..

The workaround will be deployed today, May 11th.


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:

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

Note that the mapping is reversible, so it is possible to send replies or new messages to an original sender by sending them to the corresponding mapped @dmarc.ietf.org email address.

Best Regards,
Alexey