On 2/2/23 09:28, Mike Wertheim wrote:
Now that we're on Mailman 3 and the email list was migrated from MM2 to MM3, we see that newaddress@gmail.com is a Member of the list, and we see that oldaddress@hotmail.com is a NonMember of the list. That all makes sense.
But now, this person has decided that they actually want to go back to using the old address.
So I ran the command "mailman changeaddress newaddress@gmail.com oldaddress@hotmail.com". But that gave me this output:
Usage: mailman changeaddress [OPTIONS] OLD_ADDRESS NEW_ADDRESS Try 'mailman changeaddress -h' for help.
Error: Address oldaddress@hotmail.com already exists; can't change.
Can anyone explain how I can do what I'm trying to accomplish?
The user needs to create an account in the web UI for newaddress@gmail.com and once that is done and she is logged in, she can add oldaddress@hotmail.com to her account.
There are alternatives that you as list owner can do such as mass subscribing oldaddress@hotmail.com to the list and then disabling delivery to newaddress@gmail.com.
There are also things you can do in mailman shell such as
$ mailman shell -l list.example.com
Welcome to the GNU Mailman shell
Use commit() to commit changes.
Use abort() to discard changes since the last commit.
Exit with ctrl+D does an implicit commit() but exit() does not.
The variable 'm' is the list.example.com mailing list
>>> mbr = m.nonmembers.get_member('oldaddress@hotmail.com')
>>> mbr.role = MemberRole.member
>>> commit()
(Also, why is this error displaying the usage message? That seems odd, since the number and type of arguments was correct.)
That's the way the mailman command works. All errors start with the usage.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan