Paul Tomblin wrote: > >I suspect it has something to do with the way GMail puts a >DKIM-Signature and DomainKey-Signature on outgoing mail. Something >Mailman is doing is making the signatures invalid.
If your list adds msg_header or msg_footer, that almost certainly breaks the signatures. If your list makes no alterations to the message body or subject or reply-to headers, it shouldn't break the signatures, but certain Python email library transformations over which Mailman has no control may break them anyway. >As a matter of >fact, doing a "Show original" on a couple of the flagged messages >seems to confirm that, with messages like > >Authentication-Results: mx.google.com; spf=pass (google.com: domain of >geeks-boun...@list.xcski.com designates 69.164.214.240 as permitted >sender) smtp.mail=geeks-boun...@list.xcski.com; dkim=neutral (body >hash did not verify) header...@gmail.com > >So what are my options here? Can I strip out the DKIM headers within >Mailman? Or should I just configure my mailserver to add a DKIM >header? Beginning in Mailman 2.1.7, these signatures were removed. Beginning in Mailman 2.1.10, this removal was made conditional on the new mm_cfg.py setting REMOVE_DKIM_HEADERS which defaults to No. So, assuming your Mailman is 2.1.10 or later, you can configure it to remove the headers by putting REMOVE_DKIM_HEADERS = Yes in mm_cfg.py. -- Mark Sapiro <m...@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan ------------------------------------------------------ Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
