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