Re: Weird messages from IETF/Google Mailservers (WG: PALS WG Adoption poll draft-schmutzer-pals-ple)

Jim Fenton <> Thu, 01 June 2023 14:38 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id A65A6C151065; Thu, 1 Jun 2023 07:38:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Status: No, score=-2.097 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_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (1024-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id mjZTkxE-SRJZ; Thu, 1 Jun 2023 07:38:15 -0700 (PDT)
Received: from ( [IPv6:2607:f2f8:a994::2]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by (Postfix) with ESMTPS id 62076C14CEF9; Thu, 1 Jun 2023 07:38:15 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed;; s=supersize; h=Content-Transfer-Encoding:Content-Type: MIME-Version:References:In-Reply-To:Message-ID:Date:Subject:Cc:To:From:Sender :Reply-To:Content-ID:Content-Description:Resent-Date:Resent-From: Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Id:List-Help: List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=AuOvvaVtOEcPW+VC/zsLPCO8yduBVyG8n6DTWmL1SJg=; b=jED7/sAocJQqSihiSSLytkRPHe vl4kTP/9JD0QYETZNZojmJCq4HOxLBI5X20S9Q5VHIRJ4pC5pdYTra+kj845f4zvdbDDCgSheDsSo LJ9lukTNewZt8mgw0KlZMpbNUYVciZEailIVEiRruki3jGAClgNUDUnrhEOhWTU5WbfU=;
Received: from [] (helo=[]) by with esmtpsa (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from <>) id 1q4jRF-0005Fx-Tc; Thu, 01 Jun 2023 07:38:06 -0700
From: Jim Fenton <>
To: Toerless Eckert <>
Subject: Re: Weird messages from IETF/Google Mailservers (WG: PALS WG Adoption poll draft-schmutzer-pals-ple)
Date: Thu, 01 Jun 2023 07:38:00 -0700
X-Mailer: MailMate (1.14r5852)
Message-ID: <>
In-Reply-To: <>
References: <BEZP281MB2008B40D838DDC78B76B4DFA9849A@BEZP281MB2008.DEUP281.PROD.OUTLOOK.COM> <>
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <>
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Working Group Chairs <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Thu, 01 Jun 2023 14:38:19 -0000

On 1 Jun 2023, at 7:12, Toerless Eckert wrote:

> Please complain with the ART email folks. It is the IETF that standardized all those
> email "security" mechanisms such DMARC that google is now using to effectively make
> email unusable for many people (and this is primarily what i heard from outside the IETF).

IETF did not standardize DMARC: RFC 7489 is an informational specification published via the independent submission track.

Unfortunately many people and organizations, including some that are mandating the deployment of DMARC and publication of “reject” policies, so not understand the difference between informational and standards-track.