On 9/18/19 11:13 PM, Paul Arenson wrote:
Thank you Mark. I appreciate the response. Let me respond in two messages. The first is to confirm the rules for signing off for both types of used:
The second is to clarify my problems with the signup procedure and how I might deal with it. (Mostly a very small change on your part and an explanation on my website for my users)
- So, for both subscribers vi postorius only and hyperkitty users: email to discuss-leave@list.tokyoprogressive.org (or discuss-unsubscribe@list.tokyoprogressive.org)
Yes, but you seem to have some confusion about how things work.
Mailman 3 consists of several pieces. See <https://mailman.readthedocs.io/en/latest/src/mailman/docs/introduction.html#mailman-the-gnu-mailing-list-management-system>.
As it says there, Postorius and HyperKitty are separate, web based applications for list management and archiving respectively. Both of these are Django projects - Django is a Python web framework.
What you refer to as hyperkitty users are actually Django Users. When you create and account and/or log in at Postorius or HyperKitty, you are creating/logging in to a Django account.
When you are logged in, Django, and thus Postorius and HyperKitty know who you are. If you aren't logged in, they don't.
- Only for hyperkitty users, you can login, go to https://list.tokyoprogressive.org/postorius/lists/discuss.list.tokyoprogress... and click the big red unsubscribe button.
You need to be logged in for this so Postorius knows who to unsubscribe.
- Also only for hyperkitty users, log in and click the dropdown at the upper right, select Account and click the Delete Account tab or go directly to https://list.tokyoprogressive.org/user-profile/ and click the Delete Account tab or go directly to https://list.tokyoprogressive.org/user-profile/delete
This deletes your Django account, but does not affect your list memberships.
(Guessing that #3 will not unsubscribe the person and--if they have already done 1 or 2, failing to do number 3 is not going to be a big problem. Am I right?)
That's right.
The important thing is Postorius itself knows nothing about lists or list settings or list members. It gets and/or sets this information by communicating with Mailman core. You saw an example of this when you changed an archive from public to private. Postorius told Core to make it private and Postorius would then tell you it was private because it would get that information from Core. But, it required a daily cron job to propagate that setting to HyperKitty, so HyperKitty didn't get the memo until later.
I hope this helps rather than adding confusion.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan