On 1/7/20 7:35 AM, ritwik p wrote:
Mark Sapiro wrote:
The comment says # We can't assert anything about member. It will be None when # the workflow we're confirming is an unsubscription request, # and non-None when we're confirming a subscription request. # This class doesn't know which is happening. That's backwards. I.e, it should say # We can't assert anything about member. It will be None when # the workflow we're confirming is a subscription request, # and non-None when we're confirming an unsubscription request. # This class doesn't know which is happening.
So the comments which are already present in the file are wrong?
In that case, yes.
You can use mailman inject in lieu of sending email, but you can't test the REST interface that Postorius uses that way.
Can you point me to the docs where i can find the command/instructions for approval from the moderator?
See <https://mailman.readthedocs.io/en/latest/src/mailman/core/docs/chains.html#t...>. This applies to held posts, but held subscriptions are similar.
Also, If I, set the
unsubscription_policytoconfirm_then_moderatein mailman-shell, is it applied to the Postorius as well?
Postorius is a web UI that communicates with core fia core's REST interface to retrieve, display and update core settings. Postorius gets everything from core. It does not keep its own version of anything.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan