IETF Logo Mail Archive

Re: email/tools: WG unsubscribe notification

Jared Mauch <jared@puck.nether.net> Wed, 18 May 2022 23:56 UTC

Return-Path: <jared@puck.nether.net>
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 A2493C1B92B6; Wed, 18 May 2022 16:56:39 -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, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=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 c-FzsaJ0BGK9; Wed, 18 May 2022 16:56:35 -0700 (PDT)
Received: from puck.nether.net (puck.nether.net [204.42.254.5]) (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 07156C1B92B3; Wed, 18 May 2022 16:56:34 -0700 (PDT)
Received: from smtpclient.apple (unknown [IPv6:2600:381:4b2e:2d75:d062:54bc:57c0:dd9b]) (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 puck.nether.net (Postfix) with ESMTPSA id 09E95540095; Wed, 18 May 2022 19:55:43 -0400 (EDT)
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (1.0)
Subject: Re: email/tools: WG unsubscribe notification
From: Jared Mauch <jared@puck.nether.net>
In-Reply-To: <YoWGVb6TV5LO2Sn8@faui48e.informatik.uni-erlangen.de>
Date: Wed, 18 May 2022 19:55:42 -0400
Cc: tools-discuss@ietf.org, wgchairs@ietf.org, John Levine <johnl@taugh.com>, ietf-smtp@ietf.org
Message-Id: <1A2BE354-5AE3-4162-BEE3-979E673A8CC8@puck.nether.net>
References: <YoWGVb6TV5LO2Sn8@faui48e.informatik.uni-erlangen.de>
To: Toerless Eckert <tte@cs.fau.de>
X-Mailer: iPhone Mail (19F77)
Archived-At: <https://mailarchive.ietf.org/arch/msg/wgchairs/M4wtsvFMzxcq_OJDKGHHw4wL-sY>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.34
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: Wed, 18 May 2022 23:56:39 -0000

I expect you would need to code it to mailman as it's a standard mailman message. There's a lot of questions your ask raises not limited to mailman2 and the python2 requirement for it that is likely out of scope. 

Sent via RFC1925 complaint device

> On May 18, 2022, at 7:52 PM, Toerless Eckert <tte@cs.fau.de> wrote:
> 
> Dear IETF email team
> 
> (As ANIMA WG chair) i just received 31 emails of the type
> 
>> Date: Wed, 18 May 2022 09:00:01 -0700
>> From: mailman-bounces@ietf.org
>> To: anima-owner@ietf.org
>> Subject: Anima unsubscribe notification
>> 
>> someone@example.com has been removed from Anima. (disabled address)
> 
> I don't remember i have seen this before over the years. If this is a new feature,
> and there was an email explaining it, i must have missed the email or URL
> explaining it. Pointer welcome. 
> 
> This looks like a nice feature to eliminate old junk, except that i am worried
> (after the recent incident with my own emails spam filter caused unsubscription),
> how exactly the condition "disabled address" is determined.
> 
> In general, i am not a big fan of what is probably intended as a user-friendly
> explanation such as "disabled address" without also providing the actual
> root cause diagnostic. It ony gives me "Admiral Failure" frustration.
> 
> When i sent an email to one of the addresses i did know to be obsolete,
> SMTP gave me:
> 
> <someone@somewhere.com>: host mx5.somewhere.com[1xx.xx.xx.xxx] said: 551                                            
>    5.1.1 <someone@somewhere.com>: Recipient address rejected: Failed                                            
>    recipient validation check.: host 127.0.0.1[127.0.0.1] said: 554 5.7.1                                             
>    recipient verify from ldap failed (in reply to RCPT TO command) (in reply                                          
>    to RCPT TO command)  
> 
> I would appreciate if this error indication would also be included in the
> "Unsubscribe notification" email, so that we as WG chairs (or other mailing
> list owners) can do our best to help finding false positives.
> 
> Cheers
>    Toerless

v2.23.0 | Report a Bug | By Email