Re: [dmarc-ietf] auth-res vs. dmarc
Michael Thomas <mike@mtcc.com> Tue, 29 December 2020 17:48 UTC
Return-Path: <mike@fresheez.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 1DEDB3A0140 for <dmarc@ietfa.amsl.com>; Tue, 29 Dec 2020 09:48:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.749
X-Spam-Level:
X-Spam-Status: No, score=-1.749 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.25, HTML_MESSAGE=0.001, NICE_REPLY_A=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=mtcc.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 QFwbGBvKaXoT for <dmarc@ietfa.amsl.com>; Tue, 29 Dec 2020 09:48:05 -0800 (PST)
Received: from mail-pj1-x1032.google.com (mail-pj1-x1032.google.com [IPv6:2607:f8b0:4864:20::1032]) (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 8D4AC3A0127 for <dmarc@ietf.org>; Tue, 29 Dec 2020 09:48:05 -0800 (PST)
Received: by mail-pj1-x1032.google.com with SMTP id b5so1881626pjl.0 for <dmarc@ietf.org>; Tue, 29 Dec 2020 09:48:05 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mtcc.com; s=fluffulence; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-language; bh=eHiP2ddFCXgkPc34+hiSZ81LZ9LoGj/RHkbrLpZKIFc=; b=lIWAqPplCZtRgVEKS0l/tQ7weEQzE+p8uQldbH2w2YpEkkERKtKVau4pPBAmj4V//L ibOQmgSERMFQZ0HEQOBYZGs7PC2psDEg1LVA1RmF14uHANmcQZM6ZJyu4rmCCw6MHhTa PphO3fdHeS2DwuO2JpegK5SQV5myLA4tQq/5MsM9k3pXhLYX4V7eqwA9LaWcCLzCaJ3b zxi0cF4Nzsh3hOVSDE56cMMF6zur4rZG42Nk0gWSfoDI2R5L75zUcxOvwJEWUbXjpNzl 0FDIZxpLZqrcdKnVFt/QUiNs5CwG8czeck7GVGYNiXk3kFhi1xN2zRHtl+7Y6hy1XFwr VOhA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language; bh=eHiP2ddFCXgkPc34+hiSZ81LZ9LoGj/RHkbrLpZKIFc=; b=S50ZAu2nMz6NI4rTq2mKTM0Ia1+tlOpLuyt7SGyqVnMHDFdefO0ARty5GbpEwQQWd/ nEWnPkmjjrxE5zJg1FhixTfSOzxTl1cwHkZJfQPTotlj5H5UjpfLUSQ2Bp0JhD9l+k2v mY9EheOusqWj/uBCxXl75NcjszNCA/MBFu9k3IGR8CyjadfVEOlaxfJ0lQNHnQiCKzIA U9Tp5QUmqw2kYBAGt+PmY0aytWptPyTxYz09BECP8AzkgliIlmVeIgNIHAyN5mmv75r8 bPfrbZJWVGlycgRIWiJj/ZvkqD2aJF58l05Ol9msfPQTaMZyg/3AyA3NVIjtUFb5VfkT Ka5A==
X-Gm-Message-State: AOAM533sLS3LV3r9sYto3VkcTeI5OKuHylpSsHc7NXvTar6nKsoa7dGx lgMg7YfLaxILjRHn3fWJ/AqokwyiPwXT6A==
X-Google-Smtp-Source: ABdhPJzRTtXEMs+rwOyaF1mUPWiw5m9JUcRwWIInhMXfQaGhWuxn8kH97gBhq23yU1hjwvgQksuq/g==
X-Received: by 2002:a17:90b:512:: with SMTP id r18mr4830436pjz.166.1609264083622; Tue, 29 Dec 2020 09:48:03 -0800 (PST)
Received: from mike-mac.lan ([107.182.37.0]) by smtp.gmail.com with ESMTPSA id e4sm40152466pfh.206.2020.12.29.09.48.02 for <dmarc@ietf.org> (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Tue, 29 Dec 2020 09:48:03 -0800 (PST)
To: dmarc@ietf.org
References: <9f6782b1-e85b-1a9c-9151-98feff7e18ea@mtcc.com> <CAHej_8m0OWsTt+tcSgUh+Fxu=HH_57nsb2O1Q_fgA2453ceh4g@mail.gmail.com> <140485eb-020f-4406-3f2f-e2c475ea51e5@mtcc.com> <CAHej_8mApfoF2ORgL+DoYTanrdhMjvT9H27kORwLKCQc1C9sRw@mail.gmail.com>
From: Michael Thomas <mike@mtcc.com>
Message-ID: <5588dbbe-b876-ed80-c80f-792380e3718f@mtcc.com>
Date: Tue, 29 Dec 2020 09:48:01 -0800
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:78.0) Gecko/20100101 Thunderbird/78.6.0
MIME-Version: 1.0
In-Reply-To: <CAHej_8mApfoF2ORgL+DoYTanrdhMjvT9H27kORwLKCQc1C9sRw@mail.gmail.com>
Content-Type: multipart/alternative; boundary="------------39EEE14F3D5CAEE4B1812865"
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/03NO_68fkDXDSP7QpTJRn5XeVvE>
Subject: Re: [dmarc-ietf] auth-res vs. dmarc
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: Tue, 29 Dec 2020 17:48:07 -0000
On 12/29/20 9:18 AM, Todd Herr wrote: > > The intent of the p= value is for the domain owner to communicate a > request for message handling by the entity evaluation the DMARC > results; a policy of p=none means "please treat this message the same > as you would have if you hadn't performed a DMARC check on it, > regardless of the result obtained from the check". Right, but that is not what Google at least is doing in their Auth-res. It's marking it as DMARC=fail. I think the issue is with rfc 7601 because all I see in it are some DMARC codepoints for IANA unless I missed something. But it could also be considered a fault of DMARC if there isn't normative language on what constitutes pass/neutral or missing/fail. Of course this can just be a Google bug, but it looks more likely underspecification to me. Maybe Murray can chime in here. > > My feeling is that failure should be reserved only in the case > where both SPF and DKIM fail and that the p= > none. What I'd > *really* like from a UI standpoint is the p= value passed along as > well so I can decide to decorate reject differently from > quarantine and none. > > A typical domain owner with a non-trivial email infrastructure and an > eventual goal of getting to p=reject will start with p=none, and will > consume aggregate and failure reports, and will use the data in those > reports to address any shortcomings in their authentication practices. > Aggregate reports containing DMARC failure verdicts will be quite > useful to the domain owner, to ferret out those cases where Mike in > Marketing has contracted with a third party to send mail on behalf of > the domain, or where Ellen the Engineer has a server running off the > side of her desk, sending reports to $ARBITRARY_MAILBOXES and ensure > that such mailstreams are properly authenticated before updating the > DMARC policy to p=quarantine or p=reject. It's not uncommon for some > domains to be at p=none for months, perhaps twelve or more, depending > on their mailing practices and cadences before making the switch. > Domain owners won't move to p=reject until they're sure that > enforcement of such a policy won't have a negative impact on their > mail flow. > In the mean time, it would be nice for MUA's to be able to do their part with annotating mail. DMARC=fail is really unhelpful with p=none. Mike
- [dmarc-ietf] auth-res vs. dmarc Michael Thomas
- Re: [dmarc-ietf] auth-res vs. dmarc Todd Herr
- Re: [dmarc-ietf] auth-res vs. dmarc Hector Santos
- Re: [dmarc-ietf] auth-res vs. dmarc Michael Thomas
- Re: [dmarc-ietf] auth-res vs. dmarc Michael Thomas
- Re: [dmarc-ietf] auth-res vs. dmarc Todd Herr
- Re: [dmarc-ietf] auth-res vs. dmarc Michael Thomas
- Re: [dmarc-ietf] auth-res vs. dmarc Todd Herr
- Re: [dmarc-ietf] auth-res vs. dmarc Laura Atkins
- Re: [dmarc-ietf] auth-res vs. dmarc Michael Thomas
- Re: [dmarc-ietf] auth-res vs. dmarc Todd Herr
- Re: [dmarc-ietf] auth-res vs. dmarc Michael Thomas
- Re: [dmarc-ietf] auth-res vs. dmarc Todd Herr
- Re: [dmarc-ietf] auth-res vs. dmarc Michael Thomas
- Re: [dmarc-ietf] auth-res vs. dmarc Douglas Foster
- Re: [dmarc-ietf] auth-res vs. dmarc Kurt Andersen (b)
- Re: [dmarc-ietf] auth-res vs. dmarc Douglas Foster
- Re: [dmarc-ietf] auth-res vs. dmarc Alessandro Vesely
- Re: [dmarc-ietf] auth-res vs. dmarc Alessandro Vesely
- Re: [dmarc-ietf] auth-res vs. dmarc Todd Herr
- Re: [dmarc-ietf] auth-res vs. dmarc Michael Thomas
- Re: [dmarc-ietf] auth-res vs. dmarc Michael Thomas
- Re: [dmarc-ietf] auth-res vs. dmarc Michael Thomas
- Re: [dmarc-ietf] auth-res vs. dmarc Dotzero
- Re: [dmarc-ietf] auth-res vs. dmarc Laura Atkins
- Re: [dmarc-ietf] auth-res vs. dmarc Michael Thomas
- Re: [dmarc-ietf] auth-res vs. dmarc Todd Herr
- Re: [dmarc-ietf] auth-res vs. dmarc Todd Herr
- Re: [dmarc-ietf] auth-res vs. dmarc Michael Thomas
- Re: [dmarc-ietf] auth-res vs. dmarc Todd Herr
- Re: [dmarc-ietf] auth-res vs. dmarc Michael Thomas
- Re: [dmarc-ietf] auth-res vs. dmarc Michael Thomas
- Re: [dmarc-ietf] auth-res vs. dmarc Dotzero
- Re: [dmarc-ietf] auth-res vs. dmarc Michael Thomas
- Re: [dmarc-ietf] auth-res vs. dmarc Dotzero
- Re: [dmarc-ietf] auth-res vs. dmarc Todd Herr
- Re: [dmarc-ietf] auth-res vs. dmarc Michael Thomas
- Re: [dmarc-ietf] auth-res vs. dmarc Seth Blank
- Re: [dmarc-ietf] auth-res vs. dmarc Hector Santos
- Re: [dmarc-ietf] auth-res vs. dmarc Michael Thomas
- Re: [dmarc-ietf] auth-res vs. dmarc Seth Blank
- Re: [dmarc-ietf] auth-res vs. dmarc Alessandro Vesely
- Re: [dmarc-ietf] auth-res vs. dmarc Todd Herr
- Re: [dmarc-ietf] auth-res vs. dmarc Michael Thomas
- Re: [dmarc-ietf] auth-res vs. dmarc Alessandro Vesely
- Re: [dmarc-ietf] auth-res vs. dmarc Michael Thomas
- Re: [dmarc-ietf] auth-res vs. dmarc Seth Blank
- Re: [dmarc-ietf] auth-res vs. dmarc Michael Thomas
- Re: [dmarc-ietf] auth-res vs. dmarc Seth Blank
- Re: [dmarc-ietf] auth-res vs. dmarc Alessandro Vesely
- Re: [dmarc-ietf] auth-res vs. dmarc Alessandro Vesely
- Re: [dmarc-ietf] auth-res vs. dmarc John Levine
- Re: [dmarc-ietf] auth-res vs. dmarc Murray S. Kucherawy