IETF Logo Mail Archive

Re: [dmarc-ietf] Nitpicky questions about DMARC record syntax

"John R Levine" <johnl@taugh.com> Wed, 16 January 2019 17:26 UTC

Return-Path: <johnl@taugh.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 83FF7124BAA for <dmarc@ietfa.amsl.com>; Wed, 16 Jan 2019 09:26:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, 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=1w9Iyhls; dkim=pass (1536-bit key) header.d=taugh.com header.b=DBP7rKjc
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 0vp0_alauhqT for <dmarc@ietfa.amsl.com>; Wed, 16 Jan 2019 09:26:14 -0800 (PST)
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 70D671228B7 for <dmarc@ietf.org>; Wed, 16 Jan 2019 09:26:14 -0800 (PST)
Received: (qmail 4044 invoked from network); 16 Jan 2019 17:26:10 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:user-agent; s=fc6.5c3f6932.k1901; bh=WwQKwQtFEVIs1jFwtqOfNTuV3oEg78lSEh1H+cEx94w=; b=1w9IyhlsYh4vsMii9z1Nm7DjiC76fxHQSHkZe+J2lrjgTQinbVtkFoN2lLGe6GugcP5DQR48Ri5lw404/x8rKSraqEB4PJ7/e4xBPVTJ01hRtk+rLwSiUwNhbjoTHQqlLWLGAORTLQ3+QMIqUx7RbNpBsvU0BDxwdFnu8IiUE7w692hlZ0sUpOVYNUtsODggZqXcMiPSZG7DIrmNZE+B0D99NbP1c3Yz2Z8DNP8JD+KedXjX0xyZpl69Krk4sbzg
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:user-agent; s=fc6.5c3f6932.k1901; bh=WwQKwQtFEVIs1jFwtqOfNTuV3oEg78lSEh1H+cEx94w=; b=DBP7rKjc+tkn1cqNMBqaCArXM4+qUqoy/2oL/+WYzh8cM7ng3kER2/rLfjVFE6ygPfhUsV3p75lH9++eagATwvKN/Qw0hSVCPG4GpTWc0WDe4nCzCCqnlMQNKpxv3m4xr63yPifyETKnzFBK8mj/pEbkZ43UD8xtzhg6l47SoaAgWKqYvfqk5SlG3HzfPT55DjhWPiipELUdmxrhFHs5zkpNZGdxbwMV1sSERWQ+8BDl5jeUbP8H7HwNd7d4qzMf
Received: from localhost ([IPv6:2001:470:1f07:1126::78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) with ESMTP via TCP6; 16 Jan 2019 17:26:10 -0000
Date: Wed, 16 Jan 2019 12:26:10 -0500
Message-ID: <alpine.OSX.2.21.1901161222030.38502@ary.qy>
From: John R Levine <johnl@taugh.com>
To: Kurt Andersen <kurta@drkurt.com>
Cc: dmarc@ietf.org
In-Reply-To: <CABuGu1oqy8NxfpCZOu0v-z2D2MmZUfD43B3diGZ0xQtNwPD8EQ@mail.gmail.com>
References: <20190116005804.A0A80200CACDA9@ary.qy> <b6d9024b-8a88-66fb-cfe7-800ee463c01c@gmail.com> <alpine.OSX.2.21.1901161029520.36401@ary.qy> <babe5ec6-9ceb-c7e1-1758-8dc20d116b55@gmail.com> <alpine.OSX.2.21.1901161050550.36401@ary.qy> <CABuGu1oqy8NxfpCZOu0v-z2D2MmZUfD43B3diGZ0xQtNwPD8EQ@mail.gmail.com>
User-Agent: Alpine 2.21 (OSX 202 2017-01-01)
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"; format="flowed"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/EsIktoXdwFalzdrdwaflQB49u6Y>
Subject: Re: [dmarc-ietf] Nitpicky questions about DMARC record syntax
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: Wed, 16 Jan 2019 17:26:17 -0000

> Is there really a benefit in filtering out people/organizations that are
> not fastidious in the use of whitespace and character case?

Maybe, but that's not what standards are about.  The point of a standard 
is to say here's what you do if you want to interoperate.  I have never 
found it productive to speculate about what you might or might not want to 
do when you run into people who didn't read the spec.

In the particlar case I ran into, they're all in .bank and I would expect 
that .bank's auditors would contact their clients and get them to fix 
things.  They have worse problems than wrong capitalizations, like banks 
publishing two different DMARC policies, or one that includes "pct:1" 
whatever that's supposed to mean.

Also, in this case keep in mind that the default is not to filter, so 
you're not going to lose any mail.  You might receive a few more phishes.

Regards,
John Levine, johnl@taugh.com, Taughannock Networks, Trumansburg NY
Please consider the environment before reading this e-mail. https://jl.ly

v2.23.0 | Report a Bug | By Email