[Tools-discuss] Re: Reminder re: mailman3 list owner/moderator roles

Toerless Eckert <tte@cs.fau.de> Fri, 17 May 2024 06:37 UTC

Return-Path: <eckert@i4.informatik.uni-erlangen.de>
X-Original-To: tools-discuss@ietfa.amsl.com
Delivered-To: tools-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C625AC14F5E0; Thu, 16 May 2024 23:37:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.65
X-Spam-Level:
X-Spam-Status: No, score=-6.65 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.249, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=unavailable 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 dcf1FOtxt3Pb; Thu, 16 May 2024 23:37:10 -0700 (PDT)
Received: from faui40.informatik.uni-erlangen.de (faui40.informatik.uni-erlangen.de [IPv6:2001:638:a000:4134::ffff:40]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9077AC14F5FC; Thu, 16 May 2024 23:37:08 -0700 (PDT)
Received: from faui48e.informatik.uni-erlangen.de (faui48e.informatik.uni-erlangen.de [IPv6:2001:638:a000:4134::ffff:51]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits)) (No client certificate requested) by faui40.informatik.uni-erlangen.de (Postfix) with ESMTPS id 4Vgch146lfznkZW; Fri, 17 May 2024 08:37:05 +0200 (CEST)
Received: by faui48e.informatik.uni-erlangen.de (Postfix, from userid 10463) id 4Vgch13HZpzknh9; Fri, 17 May 2024 08:37:05 +0200 (CEST)
Date: Fri, 17 May 2024 08:37:05 +0200
From: Toerless Eckert <tte@cs.fau.de>
To: tools-discuss <tools-discuss@ietf.org>
Message-ID: <Zkb7EYgaEDLqHG2F@faui48e.informatik.uni-erlangen.de>
References: <b1f6aa34-eeba-402c-a781-ae81da85e702@nostrum.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <b1f6aa34-eeba-402c-a781-ae81da85e702@nostrum.com>
Message-ID-Hash: IBMCLY64ZSEUZNUH42IZIXFOOLHPJCAH
X-Message-ID-Hash: IBMCLY64ZSEUZNUH42IZIXFOOLHPJCAH
X-MailFrom: eckert@i4.informatik.uni-erlangen.de
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-tools-discuss.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: Working Chairs <wgchairs@ietf.org>, irsg@irtf.org
X-Mailman-Version: 3.3.9rc4
Precedence: list
Subject: [Tools-discuss] Re: Reminder re: mailman3 list owner/moderator roles
List-Id: IETF Tools Discussion <tools-discuss.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/tools-discuss/MAnpvE4HzMF7X1sWqc_jtZ6fPLs>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tools-discuss>
List-Help: <mailto:tools-discuss-request@ietf.org?subject=help>
List-Owner: <mailto:tools-discuss-owner@ietf.org>
List-Post: <mailto:tools-discuss@ietf.org>
List-Subscribe: <mailto:tools-discuss-join@ietf.org>
List-Unsubscribe: <mailto:tools-discuss-leave@ietf.org>

Nice new user interface with mailman3. Thanks for the work.
Authentication via login is a lot easier now than those magic cross-chair/admin shared
list management passwords of the past!

Cheers
    Toerless

On Thu, May 09, 2024 at 02:48:22PM -0500, Robert Sparks wrote:
> If you were a list owner or moderator, you remain so for the list that was
> migrated into mailman3.
> 
> To operate on the list, you will need to claim the address used for that
> list as part of your account at mailman3. The mailman2 password you have
> used in the past is no longer useful in any way.
> 
> When you first create an account, you'll prove you can receive email at the
> address being claimed, and then set a password. At that point, you will have
> owner/moderator access for every list that used that email address.
> 
> For any other addresses that you may be configured as an owner or moderator
> of some list, you should claim those as additional addresses while logged
> into the first one. If you don't, and claim the second or subsequent
> addresses while logged out, you'll end up with multiple accounts, which will
> work, but you will probably want to merge them later, and its better to
> avoid the work in the first place. If you find you created multiple accounts
> accidentally, you can delete the one you didn't intend, and then claim its
> address in the one you wanted to keep.
> 
> For instance, over time, I've had rjsparks@nostrum.com and RjS@nostrum.com
> (and maybe a few others) end up in configuration for lists that manage. I
> will create an account using rjsparks@nostrum.com and from inside that
> account claim RjS@nostrum.com.
> 
> If you can no longer receive mail at an address that is listed for you as
> owner or moderator, you will have to ask your co-owner/moderators to change
> that value once they have access. You will also be able to request help from
> the secretariat, but please help each other as much as you can first.
> 
> If you don't remember what address you were configured as owner or moderator
> with, look at the moderation reminder messages, ask your co-owner, or ask
> the secretariat.
> 
> Note also that we do intend to eventually change this so that you use your
> datatracker credentials to access mailman3. There are a number of things
> that kept us from going straight to that without this intermediate step. But
> going through this step will make that future change easier.
> 
> RjS

-- 
---
tte@cs.fau.de