Grant Taylor via Mailman-Users writes:
> Thus, recipients see that messages aren't coming from where the sender
> says they should be and that the cryptographic signature is broken.
> Hence the receiving server is naturally treating the message from the
> mailing list as highly suspicious.
On 6/30/21 4:37 PM, Thomas Gramstad wrote:
I understand that he can't do anything about the DKIM setup at gmail.
Nor should he, or anyone else, need to.
Can I as list admin do something in the list setup (Mailman 2.29)?
As others have said, remove incoming DKIM headers from incoming
On 6/30/21 3:37 PM, Thomas Gramstad wrote:
A subscriber to one of my lists who posts from gmail has been
made aware that some list subscribers do not get his postings
because of DKIM setup at gmail. See attached error message.
I understand that he can't do anything about the DKIM setup at
One thing to try:
Add the following line to /etc/mailman/mm_cfg.py
REMOVE_DKIM_HEADERS = Yes
I did it. It clearly does no harm. Whether it helps, I don't know.
And "probably don't get" may sometimes mean "probably don't check my spam".
I'm thinking about removing all the headers with formail,
