On 5/21/21 3:58 PM, dancab@caltech.edu wrote:
Each time this problem has come up I've had to change the moderation setting from "List Default" to "Default Processing". But I've also noticed that some non-members were imported and already have "Default Processing" configured.
Can you help me understand what determines this setting in Mailman3?
It seems this would be something addressed via the mailman import21 option I've been using to import the lists.
It depends in part on the version of Mailman core as mailman import21
has had some changes, but here's how it should work.
Regexps in MM 2.1 *_these_nonmembers are imported into the corresponding MM 3 *_these_nonmembers.
Addresses in MM 2.1 *_these_nonmembers are imported into MM 3 as
non-members with their moderation_action set to defer, hold,
'rejectordiscardaccording to which *_these_nonmembers they came from.acceptmaps todeferand the others to the same. Prior to Mailman 3.3.0,acceptmapped toacceptbutdefer` is better.
This can get very convoluted if the same address is both a member and in *_these_nonmembers, but in both MM 2.1 and MM 3, the member takes precedence.
Is this not what you are seeing?
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan