On 2/12/21 1:02 PM, Brian Carpenter wrote:

On 2/12/21 3:14 PM, Mark Sapiro wrote:

...

It seems you imported to an existing list with import21. This is probably not a good idea.

Those members who were moderated members of the MM 2.1 list will have their moderation action set to Hold, Reject or Discard based on the 2.1 list setting.

I don't understand. Does not the import21 script require the Mailman 3 list to be created first? The Mailman 3 list was new with no members when I ran the import script.

Yes, You did the right thing. I was mislead by "He said the previous moderation was the list's default which was hold for moderation." which is Mailman 3 terminology.

The list does need to be created first, but it should be a new list with no members, owners, etc., not an operational Mailman 3 list.

So, it seems that most of the members of the MM 2.1 list were moderated and the list's member_moderation_action was Reject. Is this not the case?

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

I can't confirm what was set on the old MM2 list as it is no longer accessible. I am just going on the word of the List Owner. My opinion is that the moderation for those list members were set to Reject on the previous MM2 list. I am mainly interested to see if you know of this happening to anyone else and/or perhaps there is an existing bug that could impact the moderation settings of imported MM2 lists.

If you have the config.pck and any MM 2.1 installation, you can get all the info from the config.pck. For example

/path/tp/mm2.1/bin/dumpdb /path/to/config.pck|grep member_moderation_action

will show the setting with 0 = Hold, 1 = Reject and 2= Discard. Finding which members are moderated is more difficult as there is a dictionary named user_options with keys = to email addresses and integer values and the integer is a bit field defined as follows (from Defaults.py)

# Bitfield for user options. See DEFAULT_NEW_MEMBER_OPTIONS above to set # defaults for all new lists. Digests = 0 # handled by other mechanism, doesn't need a flag. DisableDelivery = 1 # Obsolete; use set/getDeliveryStatus() DontReceiveOwnPosts = 2 # Non-digesters only AcknowledgePosts = 4 DisableMime = 8 # Digesters only ConcealSubscription = 16 SuppressPasswordReminder = 32 ReceiveNonmatchingTopics = 64 Moderate = 128 DontReceiveDuplicates = 256

However, to address your concern, As far as I know, import21 is doing the right thing. If you want to send me the config.pck you imported, I can try to verify that.

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

Mark,

I have a somewhat related issue regarding member moderation settings.

I've imported a list where the default member moderation is reject (with notification).

dumpdb /var/lib/mailman/lists/wiser-announce/config.pck |grep member_moderation_action 'member_moderation_action': 1,

The Message Acceptance default is set for that as well. Default action to take when a member posts to the list: Reject (with notification)

Members that were imported all show Moderation Action: Reject (with notification)

However when a new member is added in Mailman3 the properties for the member show the following: Moderation Action: None

In Mailman2 new members had their moderation action set according to the list configuration. Are we missing something?

Thanks.

-- Dan

Thanks much. That's what I suspected and was hoping to be true.

I do think explicitly showing "List Default" would be better than "None" as a value in that field.