From: Adam Weiss <adam@signal11•com>
To: Mike Hearn <mike@plan99•net>
Cc: Bitcoin Dev <bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] Proposal: Move Bitcoin Dev List to a Neutral Competent Entity
Date: Mon, 15 Jun 2015 15:45:38 -0400 [thread overview]
Message-ID: <CAFVoEQQvs2e8qNDudNb_10UAHfkMEN5JDhG4HaD4Q-CvCKncHg@mail.gmail.com> (raw)
In-Reply-To: <CANEZrP3uF7AfcH__zHjSUt=RWXG4RfPup=zwnLf_G1_1_oMvmA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2476 bytes --]
Recent versions of mailman strip DKIM signatures, rewrite the envelope-from
to use an address at the list's domain and set reply-to to the original
authors address to resolve the DMARC issue. I'm on several lists that do
this and it works just fine.
+1 on moving the list. Given the fact that the mails are archived in
public, it's not really a huge deal how it takes place. One month sounds
reasonable (although I think it could be done on a shorter timescale). I'd
setup the new list to allow subscriptions, but keep it moderated to keep
discussion from moving until the cut, send lots of warnings and then on the
big day unmoderate one and moderate the other.
It's a great opportunity to hardfork something in Bitcoin without risk of
breakage, losses or entertaining melodrama. : )
--adam
ps. I think SF will let project admins download mbox archives of the list,
the new admins should be able to import them to keep archive consistency in
one place.
On Mon, Jun 15, 2015 at 6:13 AM, Mike Hearn <mike@plan99•net> wrote:
> Bear in mind the problem that stops Jeff's messages getting through is
> that mailman 1.0 doesn't know how to handle DKIM properly. Switching to a
> different mailman provider won't fix that.
>
> Does mailman 3.0 even fix this? I found it difficult to tell from their
> website. There's a big page on the mailman wiki that suggests they "fixed"
> it by simply deleting the signatures entirely, which won't work. DMARC
> policies state that mail *must* be signed and unsigned/incorrectly signed
> message should be discarded.
>
> The user documentation for mailman 3 doesn't seem to exist? The links on
> the website are docs for 2.1, perhaps they released mailman 3 without
> refreshing the docs.
>
> Google Groups may be "controversial" but if I recall correctly the main
> issue was the question of whether you needed a Google account or not. I'm
> pretty sure you can just send an email to
> groupname+subscribe@googlegroups•com even if you don't have a Google
> account. But of course this is a bizarre standard to hold mailing list
> software to: mailman asks users to create an account for each listserv in
> order to manage a subscription too!
>
>
>
> ------------------------------------------------------------------------------
>
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development@lists•sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>
>
[-- Attachment #2: Type: text/html, Size: 3480 bytes --]
next prev parent reply other threads:[~2015-06-15 19:45 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-14 10:12 Warren Togami Jr.
2015-06-14 15:15 ` Jeff Garzik
2015-06-14 16:56 ` Peter Todd
2015-06-15 3:19 ` Warren Togami Jr.
2015-06-15 5:50 ` Andy Schroder
2015-06-15 9:13 ` odinn
2015-06-17 0:19 ` Warren Togami Jr.
2015-06-17 1:59 ` grarpamp
2015-06-14 20:55 ` Andy Schroder
2015-06-14 21:59 ` Adam Back
2015-06-14 22:14 ` Davide Cavion
2015-06-14 21:54 ` odinn
2015-06-14 22:38 ` Gregory Maxwell
2015-06-15 10:13 ` Mike Hearn
2015-06-15 19:45 ` Adam Weiss [this message]
2015-06-15 20:50 ` Pieter Wuille
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=CAFVoEQQvs2e8qNDudNb_10UAHfkMEN5JDhG4HaD4Q-CvCKncHg@mail.gmail.com \
--to=adam@signal11$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=mike@plan99$(echo .)net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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