On Thu, 21 Mar 2019 17:27:01 -0000, Mark Sapiro <mark@msapiro.net> wrote:
On 3/21/19 3:02 AM, Malcolm Austen wrote:
My only experience of MM3 is with Ancestry's 'RootsWeb' installation. From the emails I can see a header "X-Mailman-Version: 3.1.0" but I can't find anything to identify Postorius which is the only interface I have to the system.
Isn't there a footer at the bottom of wach page with something like: Postorius Documentation • GNU Mailman • Postorius Version 1.2.5
Unfortunately not Mark, Ancestry/RootsWeb have a history of tailoring
Mailman heavily - and then deciding they don't have the resources to
update to a new version :-(
All there is on <https://lists.rootsweb.com/postorius/> is:
RootsWeb is funded and supported by Ancestry.com and our loyal RootsWeb
community. Learn more.
About Us | Contact Us | Rootsweb Blog | Copyright
© 1997-2018 Ancestry | Corporate Information | Privacy | Terms and
Conditions
From symptoms seen and described by others, I have deduced that the Postorius admin-per-user moderation options of "Default processing" and "List default" mean that a user may be set (by default on the rootsweb system!) to use the system default moderation settings rather than the list default settings.
New (non-)members always have Moderation set to List default. This means their posts are governed by the applicable Settings -> Message Acceptance settings.
I suspect that everyone on the rootsweb system was mistakenly set to
'Default processing' when they were bulk-imported from Mailman2.
Setting a user's Moderation to Default Processing means that users posts will not be held/rejected/discarded/accepted immediately based on "Default action to take when a (non-)member posts to the list", but additional checks will not be bypassed. See <https://mailman.readthedocs.io/en/latest/src/mailman/rules/docs/rules.html>.
I will read that, and whatever else I can.
Are my deductions correct? And if so, could this be the explanation of the issue detailed in this thread?
Setting a user's Moderation to Default Processing (or Accept) would bypass the list defaults and could be the explanation of this issue.
When the non-member owner first posts to the list that address becomes a non-member of the list. I.e. it is in the roster of known non-members of the list and that non-member record could have had its Moderation set to Accept or Default Processing at some point which would explain why the posts are accepted.
Thanks for the explanation and link, Malcolm.
-- Malcolm Austen <malcolm.austen@weald.org.uk>