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

"Andrew G. Malis" <> Fri, 11 May 2018 14:12 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id A4F5712D777 for <>; Fri, 11 May 2018 07:12:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (2048-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id UOtbp5e-m_va for <>; Fri, 11 May 2018 07:12:41 -0700 (PDT)
Received: from ( [IPv6:2607:f8b0:4003:c0f::234]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 3D0D21200C1 for <>; Fri, 11 May 2018 07:12:41 -0700 (PDT)
Received: by with SMTP id l22-v6so6393142otj.0 for <>; Fri, 11 May 2018 07:12:41 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=11jBRdXy4beSiyCSO3ntEwAXyQRMmrNaP80ROhT4IQE=; b=fjNf75ybzq8JWcrDuTJBT6i4rzOeJ8ow3AZZ4XSGMUqd1uIWzIW9AJhzefDhd/rkaN Dg+ef2+k9IiLMNcs/KSZXKtad2Xi6ahNdgl6Wub2ptd2Sli6n80pKI5rbjNk72oWUuzN Ob9A0ZivUs57TNgNF85zN7iDh0p4o/ugQiLJOOjfdQz6wFhAB8Hwtplk3OJg4akpBriD LH6Pep+QFha6mxvIG5ICEvpQlIyLXvkSjbn1IadoYbAFTrw0a3NYboCSqbx0FmmhnWBS fErP8KJzEgB2YHyiTiQvdltUSnn/VvvEJ8xqRzziSP4OrF1A5Q9XRAF9aQPLWXZv7I75 d4+w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=11jBRdXy4beSiyCSO3ntEwAXyQRMmrNaP80ROhT4IQE=; b=QCTvT0DjMFdAyTixFiwkfPrMeZoECWP88hlfnen05CR8/ATvyBzsnIUEggCcdIKPK1 4kgdr2tS9KGuhjbpBhrBzf3tXf+wjSOAOhWjbB+8n0fFalwxlpkU39draf4hT7XHgOol paHRqz52ir++8ACyUcQF31oasXwTLlodc5i6Ch36uUtLig4wvz26lK03p/rMKc4yoF+J Dj7I58SDmV87HD7neFDTRE+oKz+eWKF0GA9Y4VMMMkoWLccEAg6DViQEgRX1jBJNasz4 hH01yURxkBO7eWHUlu/gJ6H7vRlWlLYOI+cYStyhb0hiKnQGOtVLfEiVnCUad0VUVcuG EI/w==
X-Gm-Message-State: ALKqPwfLSkMPSl5K5i+I4F+ikLcc6kF6v0GSaRIqjRuzXIyiDcSJFHq2 yLZFMWajObaw2Fas49ILLQr743TfJa673OIyTY8=
X-Google-Smtp-Source: AB8JxZpOyUqOkj7srNhn2D4DeDLR3V9RWNEN27Ttd8sMdU0kAqAckCrpxTvaiSwon1ZfJoY9eK/MDE3QtqYtGFHzFYk=
X-Received: by 2002:a9d:26e2:: with SMTP id i31-v6mr3739062otd.27.1526047960475; Fri, 11 May 2018 07:12:40 -0700 (PDT)
MIME-Version: 1.0
Received: by 2002:a9d:1f27:0:0:0:0:0 with HTTP; Fri, 11 May 2018 07:12:20 -0700 (PDT)
In-Reply-To: <>
References: <>
From: "Andrew G. Malis" <>
Date: Fri, 11 May 2018 10:12:20 -0400
Message-ID: <>
Subject: Re: Enabling DMARC workaround code for all IETF/IRTF mailing lists
To: Alexey Melnikov <>
Cc: IETF Discussion <>
Content-Type: multipart/alternative; boundary="000000000000982b24056beeba32"
Archived-At: <>
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Fri, 11 May 2018 14:12:42 -0000


Many thanks to you, Henrik, and the team!


On Fri, May 11, 2018 at 8:00 AM, Alexey Melnikov <>

> 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 @
> domain (which will have a p=none policy). For example, "
>" email address would become "alexey=
>"quot;. 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 email address.
> Best Regards,
> Alexey