Hi Mark,
Am 18.09.2018 um 20:48 schrieb Mark Sapiro:
On 09/18/2018 10:26 AM, Jonas Meurer wrote:
Apparently, that's not the case. If the default message acceptance setting for members is set to "reject", then mails from *@freesources.org get rejected even though the header filter says "accept". In other words, the default message acceptance action seems to overrule any header filters.
Is this expected behaviour?
Yes. Rules are normally checked in a sequence defined in mailman/chains/builtin.py and that sequence checks several things including member moderation before checking header matches, so if "Default action to take when a member posts to the list" is anything other than "Default processing", that action will take precedence over header matches.
Thanks for the clarification.
Maybe then the description for chain "accept" in postorius needs to be adjusted. Currently it says "Accept immediately (bypass other rules)". This gives the impression, that it will overrule the default action.
A related followup question: what configuration is recommended for an announcement list where only specific senders (e.g. sender@example.org) should be allowed to post and mail from all (other) subscribers should be rejected?
The only way I see to achieve this currently is:
- Set default action for member posts to "Default processing"
- Add a header filter to accept "sender@example.org"
- Add a header filter to reject ".*"
In my eyes, that's very counter-intuitive and cumbersome to configure. But maybe I just missed a more obvious and elegant solution to achieve the same?
And one more comment: if I make the list an "anonymous list" (i.e. "hide the sender of a message, replacing it with the list address"), then header filters for the "from" header don't work any longer. That's kind of unexpected as well. I would have expected mailman to process the header filters at reading the incoming mail, not after rewriting headers of the outgoing mail?
Cheers jonas