From: Mike Hearn <mike@plan99.net>
To: "Warren Togami Jr." <wtogami@gmail.com>
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Mailman incompatibility with DKIM ...
Date: Fri, 19 Jun 2015 11:56:16 +0200 [thread overview]
Message-ID: <CANEZrP3vut8uYWeeynLdwvSM56eXZZdgidaEgcvg1FNMye6P9w@mail.gmail.com> (raw)
In-Reply-To: <CAEz79PoDn+-aDkqSfPeQFUjYDEDEhSrJ2mFYcbitHBf4oADBSg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1060 bytes --]
>
> We already removed the footer because it was incompatible with DKIM
> signing. Keeping the "[Bitcoin-dev] " prepend tag in subject is compatible
> with DKIM header signing only if the poster manually prepends it in their
> subject header.
>
I still see footers being added to this list by SourceForge?
> Opinions?
>
I've asked Jeff to not use his @bitpay.com account for now.
The only real fix is to use a mailing list operator that is designed to
operate correctly with DKIM/DMARC, either by not modifying messages in
transit, or by re-sending (and ideally re-signing) under their own identity.
Though I'm sure this won't be an issue for the Linux Foundation, the latter
approach is dangerous because it means the list operator takes full
responsibility for any spamming that occurs from that domain. If the mail
server is ever hacked or spammers start posting to the lists themselves,
all that spam will be seen as originating from the listserv itself and the
reputation will be degraded. It can end with everyone's mail going to the
spam folder.
[-- Attachment #2: Type: text/html, Size: 1595 bytes --]
next prev parent reply other threads:[~2015-06-19 9:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-19 9:51 [Bitcoin-development] Mailman incompatibility with DKIM Warren Togami Jr.
2015-06-19 9:56 ` Mike Hearn [this message]
2015-06-19 10:10 ` Warren Togami Jr.
2015-06-19 10:24 ` Mike Hearn
2015-06-19 10:38 ` Warren Togami Jr.
2015-06-19 10:49 ` Mike Hearn
2015-06-19 19:47 ` Adam Weiss
2015-06-19 20:44 ` Jeff Garzik
2015-06-20 18:43 ` Adam Weiss
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=CANEZrP3vut8uYWeeynLdwvSM56eXZZdgidaEgcvg1FNMye6P9w@mail.gmail.com \
--to=mike@plan99.net \
--cc=bitcoin-development@lists.sourceforge.net \
--cc=wtogami@gmail.com \
/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