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] Proposal: Move Bitcoin Dev List to a Neutral Competent Entity
Date: Mon, 15 Jun 2015 12:13:32 +0200 [thread overview]
Message-ID: <CANEZrP3uF7AfcH__zHjSUt=RWXG4RfPup=zwnLf_G1_1_oMvmA@mail.gmail.com> (raw)
In-Reply-To: <CAEz79Pp_6FhDjtR6emBcXf_WT14MbDaTxMbeAo=QAfhS-ihFCQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1114 bytes --]
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!
[-- Attachment #2: Type: text/html, Size: 1512 bytes --]
next prev parent reply other threads:[~2015-06-15 10:13 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 [this message]
2015-06-15 19:45 ` Adam Weiss
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='CANEZrP3uF7AfcH__zHjSUt=RWXG4RfPup=zwnLf_G1_1_oMvmA@mail.gmail.com' \
--to=mike@plan99$(echo .)net \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=wtogami@gmail$(echo .)com \
/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