From: George Dunlap <george.dunlap@eu.citrix.com>
To: Ian Jackson <Ian.Jackson@eu.citrix.com>
Cc: Lars Kurth <lars.kurth@xen.org>, Matt Wilson <msw@amazon.com>,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: lists.xen.org Mailman configuration and DKIM
Date: Fri, 3 Aug 2012 17:24:23 +0100 [thread overview]
Message-ID: <501BFB37.4010307@eu.citrix.com> (raw)
In-Reply-To: <20507.58318.416753.917851@mariner.uk.xensource.com>
On 03/08/12 15:44, Ian Jackson wrote:
> Matt Wilson writes ("[Xen-devel] lists.xen.org Mailman configuration and DKIM"):
>> Several folks have let me know that my messages sent via lists.xen.org
>> are marked as spam / spoofed, especially when using Gmail to receive
>> Xen mail. I believe this is because outbound Amazon email contains a
>> DKIM signature. When Mailman modifies my message and re-sends it, the
>> DKIM signature is invalidated [1].
>>
>> To work around this, Mailman 2.1.10 and later contain a configuration
>> variable called "REMOVE_DKIM_HEADERS" [2]. Perhaps if this were turned
>> on we'd work around the problem.
> ...
>> [1] http://wiki.list.org/display/DEV/DKIM
>> [2] https://bugs.launchpad.net/mailman/+bug/557493
> Having checked RFC4871 I think it is clear that according to the
> standards
> - Mailman SHOULD NOT [1] strip DKIM-Signature
> - No-one should treat a message with an invalid DKIM signature
> differently from a message with no DKIM signature at all [2]
It's actually pretty likely that gmail would also reject the mail if it
had no DKIM signature, isn't it? In which case stripping the signature
wouldn't really help.
-George
next prev parent reply other threads:[~2012-08-03 16:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-02 21:11 lists.xen.org Mailman configuration and DKIM Matt Wilson
2012-08-03 14:44 ` Ian Jackson
2012-08-03 16:24 ` George Dunlap [this message]
2012-08-03 20:51 ` Matt Wilson
2012-08-06 14:31 ` Ian Jackson
2012-08-07 21:56 ` Matt Wilson
2012-08-06 15:09 ` George Dunlap
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=501BFB37.4010307@eu.citrix.com \
--to=george.dunlap@eu.citrix.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=lars.kurth@xen.org \
--cc=msw@amazon.com \
--cc=xen-devel@lists.xen.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).