bob 001 wrote: > >After upgrading to mailman 2.1.10, we were hoping for resolving the issue of >stripped keys. > >Although keys are not longer stripped, yahoo says domainkeys=fail (bad sig) >and gmail says "dkim=neutral (body hash did not verify)" > >Please note that, one to one email works fine and yahoo and gmail both >confirms that signature are ok and valid. It is *only* mailman list email >that gets invalidated :-( > >Any suggestions, how can this be resolved? How can we make sure that keys >are considered legitimate when email is sent to list? > >We are using dkimproxy...with both signatures .. and works great on >individual emails.
There are a couple of long threads on this at <http://mail.python.org/pipermail/mailman-developers/2007-February/thread.html>. The current situation in Mailman is sumarized in the following from Defaults.py ># Some list posts and mail to the -owner address may contain DomainKey or ># DomainKeys Identified Mail (DKIM) signature headers <http://www.dkim.org/>. ># Various list transformations to the message such as adding a list header or ># footer or scrubbing attachments or even reply-to munging can break these ># signatures. It is generally felt that these signatures have value, even if ># broken and even if the outgoing message is resigned. However, some sites ># may wish to remove these headers by setting this to Yes. >REMOVE_DKIM_HEADERS = No -- Mark Sapiro <[EMAIL PROTECTED]> 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://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq01.027.htp
