On 2021-01-25 23:52:53 (+0800), Mark Sapiro wrote:
On 1/24/21 10:02 PM, Philip Paeps wrote:
Thanks for the tip! This list does have a `pipeline` attribute.
[...]
It seems to have both SpamDetect and CookHeaders. Our other mailing
lists do not have a pipeline attribute defined though
On 2021-01-25 18:39:15 (+0800), Onyeibo wrote:
On Sun, 24 Jan 2021 21:48:38 -0800
Mark Sapiro wrote:
On 1/24/21 7:46 PM, Philip Paeps wrote:
On 2021-01-24 14:08:28 (+0800), Philip Paeps wrote:
We have DMARC "munge from" configured on all mailing lists on
lists.freebsd.org.
Th
On 2021-01-25 14:02:55 (+0800), Philip Paeps wrote:
On 2021-01-25 13:48:38 (+0800), Mark Sapiro wrote:
On 1/24/21 7:46 PM, Philip Paeps wrote:
On 2021-01-24 14:08:28 (+0800), Philip Paeps wrote:
We have DMARC "munge from" configured on all mailing lists on
lists.freebsd.org.
Th
On 2021-01-25 13:48:38 (+0800), Mark Sapiro wrote:
On 1/24/21 7:46 PM, Philip Paeps wrote:
On 2021-01-24 14:08:28 (+0800), Philip Paeps wrote:
We have DMARC "munge from" configured on all mailing lists on
lists.freebsd.org.
This week, I learned that one of our lists is not actual
On 2021-01-24 14:08:28 (+0800), Philip Paeps wrote:
We have DMARC "munge from" configured on all mailing lists on
lists.freebsd.org.
This week, I learned that one of our lists is not actually munging
though.
I've done a `config_list -o` and compared the output to a list t
g that would explain the
problem.
When a poster from a DMARC-crippled domain tries to post to this list, I
see a line in vette that the DMARC policy has been found. There are no
messages in the error log.
Any idea what could explain this? And how I could go about fixing it?
Many thanks
pgrade (for whatever reason), we won't run into
too many edge cases of migration others haven't tried before us.
Meanwhile, we're very grateful for any efforts to keep Mailman 2.x at
least slightly maintained. Count me in for helping out with that.
Thank you!
Philip [hat: postm
