On 5/24/21 10:46 AM, dancab@caltech.edu wrote:
Sorry for any confusion. I'm specifically referring to addresses configured as "accept_these_nonmembers" in Mailman2. Upon importing to Mailman3 I see the moderation setting for most of those non-members as "Default Processing -- run additional checks and accept the message."
This is the correct result for an imported address from accept_these_nonmembers.
However, I've seen a few others set with the moderation option as "List default -- follow the list's default member action." after migrating to Mailman3. In our case that means "Hold for moderation". So we've had a couple of incidents where a user that was able to email the list just fine via Mailman2 is unable to message the list once migrated to Mailman3.
I'll try importing more lists to look for some kind of pattern now that I'm aware of this happening.
Yes. importing an address from accept_these_nonmembers should not result in a non-member with moderation_action = List Default. If you send me a config.pck that you imported that resulted in this, I'll investigate further, or perhaps you can identify the conditions that cause this.
One thing you might look at is whether the affected addresses were previously imported as members or non-members of another list.
Also, I don't know if this is possible given your list create/import scenario, but if there is a window between list creation and the import, if the non-member posts during that window, a non-member record will be created with moderation_action = List Default and the import won't change that. If this is the case, the import will print
<address> is already imported with role MemberRole.nonmember
for each such address.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan