Re: [dmarc-ietf] DMARCbis WGLC - Issue 141 DMARC and What To Say About SPF -all

Neil Anuskiewicz <neil@marmot-tech.com> Mon, 08 April 2024 01:03 UTC

Return-Path: <neil@marmot-tech.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 B30F3C14F618 for <dmarc@ietfa.amsl.com>; Sun, 7 Apr 2024 18:03:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.086
X-Spam-Level:
X-Spam-Status: No, score=-2.086 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, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, T_SPF_PERMERROR=0.01, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=marmot-tech.com
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 10IzSlMwKAcg for <dmarc@ietfa.amsl.com>; Sun, 7 Apr 2024 18:03:06 -0700 (PDT)
Received: from mail-pg1-x52b.google.com (mail-pg1-x52b.google.com [IPv6:2607:f8b0:4864:20::52b]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2DA95C14F60A for <dmarc@ietf.org>; Sun, 7 Apr 2024 18:03:05 -0700 (PDT)
Received: by mail-pg1-x52b.google.com with SMTP id 41be03b00d2f7-5d42e7ab8a9so2401783a12.3 for <dmarc@ietf.org>; Sun, 07 Apr 2024 18:03:05 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=marmot-tech.com; s=google1; t=1712538185; x=1713142985; darn=ietf.org; h=to:in-reply-to:cc:references:message-id:date:subject:mime-version :from:content-transfer-encoding:from:to:cc:subject:date:message-id :reply-to; bh=X6XDrZerbQMbQFnzY3Vz/2T0QA3Pe1RvKHrXRkUycP8=; b=cyi4k01M/m7h4gqCs6LVCIEX8xhc4XQHMQtzsRuKFOHhcrg9zeEc/nYVmjOhVBTA7X NJmml/98ETDHbPRN7msQbdFkVA2lEiZ/feahzNTJmMdEcgMlylCN6OhhkSekllGc0lUC xWMdAf6wKjz/iMfzigXOfr3tOlu2Ri/qcZ3DD5gvmBeFc9t4jDnj30EBMLV3gsXbAnM0 TN/4DPs2sVuIE+M/5uisw/8zkqqXSvws3IVVyrhb38P7OF3OuADF9iosL6W9UPlYQ4Gt DAfZLJ0N+qIxFIUqTfQxHBTXuuuEnq/WbPXVmMkqI8pLB4/Sm1dvU04qDmN0ceylFRdy W6qg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1712538185; x=1713142985; h=to:in-reply-to:cc:references:message-id:date:subject:mime-version :from:content-transfer-encoding:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=X6XDrZerbQMbQFnzY3Vz/2T0QA3Pe1RvKHrXRkUycP8=; b=RO6ZCRmhihIaqyvg6OA7Mk0tGAoJyrr2564YqZkEQ78hJMWI+VXN7F+7TOQJtE4O3i NHJIKWCVsyMrlPhBeoNh4E2wBzxhXscFXLL/8X5G1lfBBp5rcSuofZV3+do1RPuaxYUs FHTWYKdgmS3dPckF8SN9uIZf2JTsuexWTV/v1LKdCLgdp6YzR7zme/oBM1yIT6/rJmds lST4jRoSqoRC7PBDopoFKOXmdtpAU50WLG39Rt2rDc07T6HcovCZszLvSG6qLKAbklb2 1UTHl59Mm5qrMwK+370NUJ8LRB/IKkoa8SM3EHUax7R6rR7+3gKU1eyD0Jpl9CNdpxNv xnfg==
X-Forwarded-Encrypted: i=1; AJvYcCV8pNjFEjMIbM32XBwdi03sXboo4EoSdMELaNqyA4Xzq02JPWKgU0+7N+GA8OL/sNzhIO3rs3G0SmgKBjq50g==
X-Gm-Message-State: AOJu0Yw5szBYFT3wPmOdG5NhQKaBGK5mLARGI/Bg6uwGkhQG2zGQySK/ owbhrufpa9NY52nWvFxPOq9xPAu82ML2UqXbOLKROz/yXM/F/Agk8AFvMVJ2XWCFRF1qcounMXq j
X-Google-Smtp-Source: AGHT+IHC0EOawwOrK4RfdCu27FxJfWvVOabicGEIsWc91nyzb/w5cp/mnwcV6i/ePqwen4KERbW6hA==
X-Received: by 2002:a17:90a:eb88:b0:2a5:575:5f59 with SMTP id o8-20020a17090aeb8800b002a505755f59mr1341409pjy.3.1712538184681; Sun, 07 Apr 2024 18:03:04 -0700 (PDT)
Received: from smtpclient.apple (c-73-96-89-175.hsd1.or.comcast.net. [73.96.89.175]) by smtp.gmail.com with ESMTPSA id mm15-20020a17090b358f00b002a058af5e12sm7046280pjb.12.2024.04.07.18.03.04 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Sun, 07 Apr 2024 18:03:04 -0700 (PDT)
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: Neil Anuskiewicz <neil@marmot-tech.com>
Mime-Version: 1.0 (1.0)
Date: Sun, 07 Apr 2024 18:02:53 -0700
Message-Id: <B20A0399-1AF8-4A5F-8D55-7F156A366637@marmot-tech.com>
References: <57C20A88-5461-4BA4-9597-1D138B71EF24@marmot-tech.com>
Cc: Scott Kitterman <sklist@kitterman.com>, dmarc@ietf.org
In-Reply-To: <57C20A88-5461-4BA4-9597-1D138B71EF24@marmot-tech.com>
To: Tero Kivinen <kivinen@iki.fi>
X-Mailer: iPad Mail (21E236)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/Zci6DM3duJ3YSWIvQL5Kku2DCMU>
Subject: Re: [dmarc-ietf] DMARCbis WGLC - Issue 141 DMARC and What To Say About SPF -all
X-BeenThere: dmarc@ietf.org
X-Mailman-Version: 2.1.39
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: Mon, 08 Apr 2024 01:03:10 -0000


> On Apr 7, 2024, at 7:00 AM, Neil Anuskiewicz <neil@marmot-tech.com> wrote:
> 
> 
> 
>> On Apr 7, 2024, at 6:54 AM, Tero Kivinen <kivinen@iki.fi> wrote:
>> 
>> Scott Kitterman writes:
>>> I hear you. Your operational issue is my system working as designed.
>>> DMARC works on top of SPF, it doesn't change it.
>> 
>> Yes, DMARC works on top of SPF, and DKIM and provides policy layer. We
>> are trying to change the fact that people rely purely on SPF, and try
>> to get them moved to use DMARC istead, and we are trying to explain
>> that if you do SPF inside the DMARC context, you get exactly same
>> policy results you get as when you do SPF before, except you get it
>> better, as you have more data available. Using -all would be
>> completely ok if everybody would be doing DMARC, but as there are some
>> systems which do SPF outside DMARC, and there having -all might
>> shortcircuit DMARC out from the equation, we should provide guidance
>> to those people how they can get best results in current environment.
>> Thus the best current practice should be use to use ~all instead of
>> -all if you are trying to use DMARC, and want other systems to
>> actually act based on your DMARC policy.

The problem I see is that some receivers never got the memo and still enforce just on an SPF hard fail which only creates fear, uncertainty, doubt, and annoyance.