[Mailman-Users] Mapping member options from Mailman 2 to 3

[Mark Sapiro]

On 7/10/15 6:41 AM, Daniel Miller wrote:
> 
> I'm trying to migrate an existing list from Mailman 2 to Mailman 3, and I
> wanted to know more about user preferences and member options. Here is the
> mapping I have so far:
> 
> Mailman 2: Mailman 3
> realname: {address, user}.display_name
> password: user.password
> language: preferences.preferred_language
> delivery.status: preferences.delivery_status
> delivery.delivery: prefererences.delivery_mode
> noremind: ???

Mailman 3 doesn't send password reminders so the list member option to
suppress them doesn't exist in MM 3


> nodupes: ~preferences.receive_list_copy
> notmetoo: ~preferences.receive_own_postings
> hide: preferences.hide_address
> ack: preferences.acknowledge_posts
> mod: ???

I'm sure there is a concept of member moderation in MM 3, but I don't
know offhand exactly how it is implemented.


> nomail: ???

This is the member options name for mlist.delivery_status[member]

> nmtopics: ???
> topics: ???

I don't think topics are implemented in MM3. I think there is a Google
Summer of Code student working on dynamic sublists which is a different
approach to topics.


> Do the missing (???) options have any corresponding attribute in Mailman 3,
> and are these accessible through mailman.client?
> 
> I am particularly interested in the moderation flag, but any other
> information you may have would be useful. I am not entirely clear on
> whether an Address or Membership can exist without an associated User, and
> if I copy our existing roster as address-only memberships whether our
> subscribers will be able to update their preferences.


These questions are better asked on mailman-developers at python.org.

-- 
Mark Sapiro <mark at msapiro.net>        The highway is for gamblers,
San Francisco Bay Area, California    better use your sense - B. Dylan