Re: Weird messages from IETF/Google Mailservers (WG: PALS WG Adoption poll draft-schmutzer-pals-ple)
Loa Andersson <loa@pi.nu> Thu, 01 June 2023 09:08 UTC
Return-Path: <loa@pi.nu>
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 ED53EC151087 for <wgchairs@ietfa.amsl.com>; Thu, 1 Jun 2023 02:08:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.896
X-Spam-Level:
X-Spam-Status: No, score=-1.896 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, NICE_REPLY_A=-0.001, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
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 3PxdGno2ZlPS for <wgchairs@ietfa.amsl.com>; Thu, 1 Jun 2023 02:08:45 -0700 (PDT)
Received: from pipi.pi.nu (pipi.pi.nu [83.168.239.141]) (using TLSv1.1 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8F555C14CE45 for <wgchairs@ietf.org>; Thu, 1 Jun 2023 02:08:44 -0700 (PDT)
Received: from [192.168.1.241] (c-72eb70d5.1063529-0-69706f6e6c79.bbcust.telenor.se [213.112.235.114]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: loa@pi.nu) by pipi.pi.nu (Postfix) with ESMTPSA id DA06736AA54; Thu, 1 Jun 2023 11:08:42 +0200 (CEST)
Message-ID: <9bb42d57-1fd7-ddee-a451-53f3ad9f8fe4@pi.nu>
Date: Thu, 01 Jun 2023 11:08:25 +0200
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; 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-GB
To: wgchairs@ietf.org, "n.leymann@telekom.de" <n.leymann@telekom.de>
References: <BEZP281MB2008B40D838DDC78B76B4DFA9849A@BEZP281MB2008.DEUP281.PROD.OUTLOOK.COM>
From: Loa Andersson <loa@pi.nu>
In-Reply-To: <BEZP281MB2008B40D838DDC78B76B4DFA9849A@BEZP281MB2008.DEUP281.PROD.OUTLOOK.COM>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/wgchairs/WIWU7apk-TnsYbJVkNasH9tmoaQ>
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 09:08:50 -0000
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. > > 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[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] 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[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] 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[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] 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
- Re: Weird messages from IETF/Google Mailservers (… Andrew G. Malis
- Weird messages from IETF/Google Mailservers (WG: … N.Leymann
- Re: Weird messages from IETF/Google Mailservers (… Loa Andersson
- Re: Weird messages from IETF/Google Mailservers (… Robert Sparks
- Re: Weird messages from IETF/Google Mailservers (… Carsten Bormann
- Re: Weird messages from IETF/Google Mailservers (… Paul Wouters
- Re: Weird messages from IETF/Google Mailservers (… Toerless Eckert
- Re: Weird messages from IETF/Google Mailservers (… Jim Fenton
- Re: Weird messages from IETF/Google Mailservers (… Barry Leiba
- Re: Weird messages from IETF/Google Mailservers (… David Noveck
- Re: [Tools-discuss] Weird messages from IETF/Goog… Brian E Carpenter
- Re: [Tools-discuss] Weird messages from IETF/Goog… Robert Sparks
- Re: [Tools-discuss] Weird messages from IETF/Goog… Tero Kivinen
- Re: Weird messages from IETF/Google Mailservers (… Tero Kivinen
- Re: Weird messages from IETF/Google Mailservers (… Toerless Eckert
- Re: [Tools-discuss] Weird messages from IETF/Goog… Tom Pusateri