IETF Logo Mail Archive

Re: [dmarc-ietf] Reporting DMARC policy in A-R header fields

tjw ietf <tjw.ietf@gmail.com> Fri, 02 August 2019 11:26 UTC

Return-Path: <tjw.ietf@gmail.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 8F20512004A for <dmarc@ietfa.amsl.com>; Fri, 2 Aug 2019 04:26:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.997
X-Spam-Level:
X-Spam-Status: No, score=-1.997 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, MIME_QP_LONG_LINE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 ui502J4BK4sF for <dmarc@ietfa.amsl.com>; Fri, 2 Aug 2019 04:26:31 -0700 (PDT)
Received: from mail-io1-xd29.google.com (mail-io1-xd29.google.com [IPv6:2607:f8b0:4864:20::d29]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E2787120033 for <dmarc@ietf.org>; Fri, 2 Aug 2019 04:26:30 -0700 (PDT)
Received: by mail-io1-xd29.google.com with SMTP id i10so38071268iol.13 for <dmarc@ietf.org>; Fri, 02 Aug 2019 04:26:30 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=/rwim81GaLd4tD/oQDyrZPbA608/BJHuSd0UQcQjdfQ=; b=rDvsUnqYFBnOS5u0zFo+Fq0TJxd5HiuWcUqwjOYZujBml6IEkvGf915YkeH6CAVMWi zkmkvzcvQoWeKGe/odAtpMHs/iAkE0zE89Bec+CNgM5FraH2XtStmUF63b/PForzdQBI nEMQeVKZzpKwKtZ5r0TOesVUrMD2+ypF2FCojiPAUvmV4qZ6YolyggX6/Fv8WW/a+6GL WHv7fvz1y7X8lDslJcV28TqzNv6PwIj/KJ8FhD3plApuR0EPbz5T2VrOYvSzVbP57oHA qNC5HjPJMCEbjT/r35nlV0EG6KKIt9o2spvSjybHVXEvv9F4zLKK2Sv/NZ9QddqAeIjI gh4Q==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=/rwim81GaLd4tD/oQDyrZPbA608/BJHuSd0UQcQjdfQ=; b=RmBJu5ZxR3VqIM2nCYphRwvpiZIco6xMP4MT+cQK8my7+HFInI0SfFKiB6/Hght8S3 GkDFnvpotmZGB3HTHMszR94vicxuYi544KufEX+Ske0Ipq9d7wcDXy83GJNx3cXI/3r8 NB/waggkd07UPwRlA1vECNTRWdz+6Kgqg+JAmX9uFOPcLDlu5N4dXkDanSYO0YLPUch2 GQ9rAMv/mJVJc7J3zELDp7xtrZOeTNs8Q8jNwOIXnXaZMwYf3c7eRTeYMZhD30wk3XvG w3yfkcNieFcm9az007isnO2dKu5XoMdiZuWynTHPWUfq3gY0GT5nHo/xJ1ec/gy/xPQz 1OmQ==
X-Gm-Message-State: APjAAAVSTSTdnbqJC4fp2darZo11sdDzLt5fIWSfcpSTQXYzuGap8caa wy9FhYVmeDpgbvDoh6KHWPDaiFPu
X-Google-Smtp-Source: APXvYqx11I2iNUye56LfFYqBuHqb+H0E+CIgh518if2Rd3l8V3vcmi/xAGlroielKBhnVi5DvLS+PQ==
X-Received: by 2002:a02:ce37:: with SMTP id v23mr28786898jar.2.1564745189999; Fri, 02 Aug 2019 04:26:29 -0700 (PDT)
Received: from [192.168.1.34] ([50.110.73.130]) by smtp.gmail.com with ESMTPSA id k26sm56157500ios.38.2019.08.02.04.26.29 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 02 Aug 2019 04:26:29 -0700 (PDT)
Content-Type: multipart/alternative; boundary="Apple-Mail-417CE4A4-503B-47DC-9BD1-B870BAC3FD86"
Mime-Version: 1.0 (1.0)
From: tjw ietf <tjw.ietf@gmail.com>
X-Mailer: iPhone Mail (16G77)
In-Reply-To: <d94cc4f0-cf2e-4cd1-95b3-9c00d7e50966@www.fastmail.com>
Date: Fri, 02 Aug 2019 07:26:28 -0400
Cc: dmarc@ietf.org
Content-Transfer-Encoding: 7bit
Message-Id: <13954F80-F37D-488A-A810-A0942750A1D2@gmail.com>
References: <20190802031401.2C5AD752163@ary.qy> <d94cc4f0-cf2e-4cd1-95b3-9c00d7e50966@www.fastmail.com>
To: Stan Kalisch <stan@glyphein.mailforce.net>
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/NCjwq2Qx8U6J5XqA8HX79sJhhq8>
Subject: Re: [dmarc-ietf] Reporting DMARC policy in A-R header fields
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, 02 Aug 2019 11:26:33 -0000

+1

No hats

From my high tech gadget

> On Aug 2, 2019, at 02:23, Stan Kalisch <stan@glyphein.mailforce.net> wrote:
> 
>> On Thu, Aug 1, 2019, at 11:14 PM, John Levine wrote:
>> Catching up on my mail after a laptop disaster, ...
>> 
>> In article <4600949.rz9u5RyGOV@l5580> you write:
>> >I think comments should be free-form.  If we want data that can be machine 
>> >parsed, we should specify it.
>> >
>> >I think the above works in ABNF terms.  It's:
>> >
>> >Authentication-Results:" authserv-id; method=result ptype.property=value 
>> >ptype.property=value
>> 
>> I agree.  We all put the DKIM stuff in comments but that's silly.  If
>> it's worth recording, it's worth doing in a way that we all agree
>> about and can parse.
> 
> Yes please.
> 
> 
> Stan
> 
> _______________________________________________
> dmarc mailing list
> dmarc@ietf.org
> https://www.ietf.org/mailman/listinfo/dmarc

v2.23.0 | Report a Bug | By Email