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

Robert Sparks <rjsparks@nostrum.com> Thu, 01 June 2023 12:53 UTC

Return-Path: <rjsparks@nostrum.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C1F2FC15152C for <wgchairs@ietfa.amsl.com>; Thu, 1 Jun 2023 05:53:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.077
X-Spam-Level:
X-Spam-Status: No, score=-7.077 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, HTML_MESSAGE=0.001, NICE_REPLY_A=-0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, T_SPF_HELO_PERMERROR=0.01, 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 (1024-bit key) header.d=nostrum.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 tgGNxZq1NTwS for <wgchairs@ietfa.amsl.com>; Thu, 1 Jun 2023 05:53:33 -0700 (PDT)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 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 44180C15199A for <wgchairs@ietf.org>; Thu, 1 Jun 2023 05:53:33 -0700 (PDT)
Received: from [192.168.1.102] ([47.186.48.51]) (authenticated bits=0) by nostrum.com (8.17.1/8.17.1) with ESMTPSA id 351CrRLa039781 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO); Thu, 1 Jun 2023 07:53:28 -0500 (CDT) (envelope-from rjsparks@nostrum.com)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=nostrum.com; s=default; t=1685624009; bh=mQxoroizsOo3QzxRiXCropNb2kefTdme7MJ4IEmONN8=; h=Date:Subject:To:Cc:References:From:In-Reply-To; b=g9UFvy3cHjHTcFDuATAbJsBum2g7W52EXm7COBMJOl0vG07jycvxNXlmgF/2YnN+s S5k3BoCM4JFid6yRmylXp7yiFr4cWfUO4jXidP8ZICzIMsxmcDEPEXCxHilLyC0VP0 G5FB8K2Bg1ooWXr5xnCBRC9tLuhRCKHTjrO/by9M=
X-Authentication-Warning: raven.nostrum.com: Host [47.186.48.51] claimed to be [192.168.1.102]
Content-Type: multipart/alternative; boundary="------------pBakB0ArRPR0M1OE69MyQokI"
Message-ID: <96d29105-2a91-dd70-a5ea-ce70ae02e804@nostrum.com>
Date: Thu, 01 Jun 2023 07:53:22 -0500
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:102.0) Gecko/20100101 Thunderbird/102.11.2
Subject: Re: Weird messages from IETF/Google Mailservers (WG: PALS WG Adoption poll draft-schmutzer-pals-ple)
Content-Language: en-US
To: "Andrew G. Malis" <agmalis@gmail.com>, Loa Andersson <loa@pi.nu>
Cc: wgchairs@ietf.org
References: <BEZP281MB2008B40D838DDC78B76B4DFA9849A@BEZP281MB2008.DEUP281.PROD.OUTLOOK.COM> <9bb42d57-1fd7-ddee-a451-53f3ad9f8fe4@pi.nu> <CAA=duU2o3Qn2f6MrAX4faDs4=-KVOqPm9R3w=MVPmRJ2s5Fq6A@mail.gmail.com>
From: Robert Sparks <rjsparks@nostrum.com>
In-Reply-To: <CAA=duU2o3Qn2f6MrAX4faDs4=-KVOqPm9R3w=MVPmRJ2s5Fq6A@mail.gmail.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/wgchairs/hdYc4brOPklYxDG9Wb12Vft9qpc>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/wgchairs/>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 01 Jun 2023 12:53:37 -0000

Changing the aliases to work more like the lists has been planned as 
part of the mailman3 transition, but we are tracking this issue 
separately at https://github.com/ietf-tools/postconfirm/issues/33. Note 
also the discussion at the May tools-team meeting at 
<https://notes.ietf.org/tools-team-20230516#New-data-on-dmarc-failures-for-aliases---RobertJohn>.

RjS

On 6/1/23 5:34 AM, Andrew G. Malis wrote:
> Loa,
>
> There's a difference between email sent to an IETF email list (which 
> uses mailman to handle email authentication issues by acting as the 
> email source) and to an IETF email expander like pals-chairs, which 
> doesn't.
>
> When you're using an email expander, the original source of the email 
> doesn't change, which exposes the email to any issues the original 
> sender of the email may have. In this case, the issue is that Google 
> is rejecting the email to pals-chairs because the telecom.de 
> <http://telecom.de/> domain apparently doesn't support DKIM or SPF. 
> This is the same issue as pi.nu <http://pi.nu>.
>
> Cheers,
> Andy
>
>
> On Thu, Jun 1, 2023 at 5:08 AM Loa Andersson <loa@pi.nu> wrote:
>
>     Nic,
>
>     No I do get them also, it looks like gmail-addresses does not work
>     with
>     gmail addresses, for me it works if I send directly to the gmail
>     addresses (i.e. not using the mail-alias).
>
>     Andy reported this, and the answer was "know problem".
>
>     What I don't understand is that we must have gmail-addresses on the
>     working mailing list, but no bounces.
>
>     /Loa
>
>     On 2023-06-01 11:00, N.Leymann@telekom.de wrote:
>     > Hi,
>     >
>     > Am I the only one getting weird messages from IETF/Google Mail
>     Servers?
>     > Looks like that the expansion of an alias caused the problem.
>     >
>     > Regards
>     >
>     > Nic
>     >
>     > -----Ursprüngliche Nachricht-----
>     > Von: Mail Delivery System <MAILER-DAEMON@ietfa.amsl.com>
>     > Gesendet: Donnerstag, 1. Juni 2023 10:50
>     > An: Leymann, Nicolai
>     > Betreff: Unzustellbar: PALS WG Adoption poll
>     draft-schmutzer-pals-ple
>     >
>     > This is the mail system at host ietfa.amsl.com
>     <http://ietfa.amsl.com>.
>     >
>     > I'm sorry to have to inform you that your message could not be
>     delivered to one or more recipients. It's attached below.
>     >
>     > For further assistance, please send mail to postmaster.
>     >
>     > If you do so, please include this problem report. You can delete
>     your own text from the attached returned message.
>     >
>     >                     The mail system
>     >
>     > <agmalis@gmail.com> (expanded from
>     <expand-pals-chairs@virtual.ietf.org>): host
>     > gmail-smtp-in.l.google.com
>     <http://gmail-smtp-in.l.google.com>[2607:f8b0:4023:c06::1b] said:
>     550-5.7.26 This
>     >      mail is unauthenticated, which poses a security risk to the
>     550-5.7.26
>     >      sender and Gmail users, and has been blocked. The sender
>     must 550-5.7.26
>     >      authenticate with at least one of SPF or DKIM. For this
>     message, 550-5.7.26
>     >      DKIM checks did not pass and SPF check for [telekom.de
>     <http://telekom.de>] did not pass
>     >      550-5.7.26 with ip: [2001:559:c4c7::100]. The sender should
>     visit
>     >      550-5.7.26
>     https://support.google.com/mail/answer/81126#authentication for
>     >      550 5.7.26 instructions on setting up authentication.
>     >      g9-20020a17090ace8900b00246fe4e326dsi753688pju.81 - gsmtp
>     (in reply to end
>     >      of DATA command)
>     >
>     > <david.sinicrope@gmail.com> (expanded from
>     >      <expand-pals-chairs@virtual.ietf.org>): host
>     > gmail-smtp-in.l.google.com
>     <http://gmail-smtp-in.l.google.com>[2607:f8b0:4023:c06::1b] said:
>     550-5.7.26 This
>     >      mail is unauthenticated, which poses a security risk to the
>     550-5.7.26
>     >      sender and Gmail users, and has been blocked. The sender
>     must 550-5.7.26
>     >      authenticate with at least one of SPF or DKIM. For this
>     message, 550-5.7.26
>     >      DKIM checks did not pass and SPF check for [telekom.de
>     <http://telekom.de>] did not pass
>     >      550-5.7.26 with ip: [2001:559:c4c7::100]. The sender should
>     visit
>     >      550-5.7.26
>     https://support.google.com/mail/answer/81126#authentication for
>     >      550 5.7.26 instructions on setting up authentication.
>     >      g9-20020a17090ace8900b00246fe4e326dsi753688pju.81 - gsmtp
>     (in reply to end
>     >      of DATA command)
>     >
>     > <stewart.bryant@gmail.com> (expanded from
>     >      <expand-pals-chairs@virtual.ietf.org>): host
>     > gmail-smtp-in.l.google.com
>     <http://gmail-smtp-in.l.google.com>[2607:f8b0:4023:c06::1b] said:
>     550-5.7.26 This
>     >      mail is unauthenticated, which poses a security risk to the
>     550-5.7.26
>     >      sender and Gmail users, and has been blocked. The sender
>     must 550-5.7.26
>     >      authenticate with at least one of SPF or DKIM. For this
>     message, 550-5.7.26
>     >      DKIM checks did not pass and SPF check for [telekom.de
>     <http://telekom.de>] did not pass
>     >      550-5.7.26 with ip: [2001:559:c4c7::100]. The sender should
>     visit
>     >      550-5.7.26
>     https://support.google.com/mail/answer/81126#authentication for
>     >      550 5.7.26 instructions on setting up authentication.
>     >      g9-20020a17090ace8900b00246fe4e326dsi753688pju.81 - gsmtp
>     (in reply to end
>     >      of DATA command)
>     >
>
>     -- 
>     Loa Andersson                        email: loa@pi.nu
>     Senior MPLS Expert loa.pi.nu@gmail.com
>     Bronze Dragon Consulting             phone: +46 739 81 21 64
>