IETF Logo Mail Archive

Re: [dmarc-ietf] Spirit of RFC8601 section 5 for invalid A-R headers

John Levine <johnl@taugh.com> Fri, 03 April 2020 20:09 UTC

Return-Path: <johnl@iecc.com>
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 9A8FD3A094C for <dmarc@ietfa.amsl.com>; Fri, 3 Apr 2020 13:09:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.85
X-Spam-Level:
X-Spam-Status: No, score=-1.85 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, HEADER_FROM_DIFFERENT_DOMAINS=0.25, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1536-bit key) header.d=iecc.com header.b=s/Au50Z8; dkim=pass (1536-bit key) header.d=taugh.com header.b=Gx7W2WrL
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 dVUZ19dDYm8A for <dmarc@ietfa.amsl.com>; Fri, 3 Apr 2020 13:09:39 -0700 (PDT)
Received: from gal.iecc.com (gal.iecc.com [IPv6:2001:470:1f07:1126:0:43:6f73:7461]) (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 3AC6A3A0934 for <dmarc@ietf.org>; Fri, 3 Apr 2020 13:09:38 -0700 (PDT)
Received: (qmail 74829 invoked from network); 3 Apr 2020 20:09:38 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=1244a.5e879802.k2004; bh=EkzAJ6UlNf1pTcEKC77AwiM8YAKbAcISp4+nkl1WDO4=; b=s/Au50Z8KOpdHEQQX+RiLzxapPwXX+z4C2go+q7+FnUTDq1Z9Nw3nexG9pOaYmmr3zipTFTlpBBjmhw7v8re8bvC1AZB6dJuPd43xSwjdl3GjAUiWkwq5Ngaq7kCSBckunnFP8xnvEYHiNm158JfmpDV1TVeZ0ABQ+xGpIJLXtbeC/ui5l7uIVAfyBIAV4OkpEYMNIvURVnsO6y7+YtWxzBrt/pj06x0AOJuO929E7sCJmUNCEBnLBsuclrDtFXo
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=1244a.5e879802.k2004; bh=EkzAJ6UlNf1pTcEKC77AwiM8YAKbAcISp4+nkl1WDO4=; b=Gx7W2WrL/VKXplr48w/UKoV+MYIKERnOaUiwn5wi+BFxWB5EDKMvyu5ummts1XQqTr2/9Xjw/mPib+dRnScUEjtIAwkj5k/tWj40hmZ1JTqn83xGWNlKg+d0j/v9Mc9fuyOqsQ0284CFjgCp+H5HnWkF43O5/50Rte31tEZTjPzUuJVjaI/d//RS4+eKD8kVOT8hkE9R1Zuj38087oFnodB7h47TjTL0L03ek+ZtTmA8qDXgYpNNLMQRgtJ9kpwu
Received: from ary.qy ([IPv6:2001:470:1f07:1126::78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) with ESMTP via TCP6; 03 Apr 2020 20:09:37 -0000
Received: by ary.qy (Postfix, from userid 501) id AAFD716FCA1B; Fri, 3 Apr 2020 16:09:37 -0400 (EDT)
Date: Fri, 03 Apr 2020 16:09:37 -0400
Message-Id: <20200403200937.AAFD716FCA1B@ary.qy>
From: John Levine <johnl@taugh.com>
To: dmarc@ietf.org
Cc: blong@google.com
In-Reply-To: <CABa8R6sbHLfkzHD4gaPBxQbgNy57J1eLXt2sPyAfaTYAY3tG-Q@mail.gmail.com>
Organization: Taughannock Networks
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset="utf-8"
Content-transfer-encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/f740_G-Cos2TcvKtg451cJWC4So>
Subject: Re: [dmarc-ietf] Spirit of RFC8601 section 5 for invalid A-R headers
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: Fri, 03 Apr 2020 20:09:42 -0000

In article <CABa8R6sbHLfkzHD4gaPBxQbgNy57J1eLXt2sPyAfaTYAY3tG-Q@mail.gmail.com> you write:
>In practice, I don't know how common it is for clients to consume this
>header.

They have to if they're adding ARC seals on the way out.  Other than
that I don't have much idea either.  On my system my mailing list software
looks at it them to decide how much DMARC hackery to do but again I don't
know how common that is.

Since the point of the text is that you can only trust your own A-R
headers, presumably the code that adds them and that consumes them are
at least partly under the same management so I'd think they could agree
on their quoting practices.

R's,
John

v2.23.0 | Report a Bug | By Email