alain williams writes:
Hmmm, I get your point. I was not paranoid enough :-(
Yeah, I'm going to post it as an RFE since you're the third person to support it. I've also tagged it "won't fix" :-) but if somebody has a really brilliant idea with a merge request, I'll review it. https://gitlab.com/mailman/postorius/-/issues/642
Maybe some really clearly written end user documentation that is easily found might help. I think that I have just given myself a job.
The easily-found part would be easy to implement with link in the Postorius template(s).
Or the process could be implemented with a workflow starting at the landing page:
- a prominent button "change address" takes you to the addresses page
- each address would have a "change address" button which has a form prompting for the new address
- submitting the form sends a verification code to the address,
- clicking on the verification link takes you to a page which asks if the old address should be deleted or kept
- if you click "keep", you get a list of memberships using the old address with radio buttons for "keep <old>" and "change to <new>".
Bonus points for short-circuiting trivial cases (only one address, only one subscription). Need to handle primary address.
The main problem is (as always) the Postorius authentication step. People forget their passwords or get scared by social auth. :-(
-- GNU Mailman consultant (installation, migration, customization) Sirius Open Source https://www.siriusopensource.com/ Software systems consulting in Europe, North America, and Japan