[BLU/Officers] testing changes to Mailman and DKIM

[Bill Ricker]

Testing after latest change(s).

On Mon, Feb 9, 2026 at 3:30 PM Bill Ricker <bill.n1vux at gmail.com> wrote:

> Received.
> Still needed by GMAIL Rule to exempt a list from being classed as Spam,
> but otherwise looks good.
>
> SPF: NONE with IP 131.226.247.88 Learn more
> <https://support.google.com/a?p=show_original&hl=en>
> DKIM: 'PASS' with domain blu.org Learn more
> <https://support.google.com/a?p=show_original&hl=en>
> DMARC: 'PASS' Learn more
> <https://support.google.com/a?p=show_original&hl=en>
>  > headerr munging to make DKIM happy.
>
> That may make Google Spam filter happier too. (Even tho' it's contrary to
> RFC, it works.)
>
> // Bill
>
> On Mon, Feb 9, 2026 at 2:15 AM John Abreau via Officers <
> officers at lists.blu.org> wrote:
>
>> I think I have the SPF, DKIM, and DMARC issues straightened out.
>>
>> There's still a PTR issue. I've emailed our colo host's tech support to
>> get that dealt with.
>>
>> As for Mailman, it looks like DKIM requires that we turn on headerr
>> munging to make DKIM happy.
>>
>> I'm only doing it to the officers list for now, to see if it works.
>>
>> --
>> John Abreau / Executive Director, Boston Linux & Unix
>> Email: jabr at blu.org / WWW http://www.blu.org
>> PGP-Key-Fingerprint 87B1 6003 9962 0824 0406  8B93 B184 3040 5640 D33F
>> _______________________________________________
>> Officers mailing list
>> Officers at lists.blu.org
>> https://lists.blu.org/mailman/listinfo/officers
>>
>
>
> --
> Bill Ricker
> bill.n1vux at gmail.com
> https://www.linkedin.com/in/n1vux
>


-- 
Bill Ricker
bill.n1vux at gmail.com
https://www.linkedin.com/in/n1vux
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.blu.org/pipermail/officers/attachments/20260211/92ef1126/attachment.html>