From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191]
	helo=mx.sourceforge.net)
	by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
	(envelope-from <bitcoin@olivere.de>) id 1XemFA-0004Cy-Jl
	for bitcoin-development@lists.sourceforge.net;
	Thu, 16 Oct 2014 14:41:32 +0000
X-ACL-Warn: 
Received: from olivere.de ([85.214.144.153] helo=mail.olivere.de)
	by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:AES256-SHA:256)
	(Exim 4.76) id 1XemF8-0001Ug-Lc
	for bitcoin-development@lists.sourceforge.net;
	Thu, 16 Oct 2014 14:41:32 +0000
Received: from nat6-182.its.fh-giessen.de ([212.201.18.182]:1103
	helo=[192.168.192.85])
	by mail.olivere.de with esmtpsa (TLS1.0:DHE_RSA_AES_128_CBC_SHA1:16)
	(Exim 4.72) (envelope-from <bitcoin@olivere.de>)
	id 1Xeltv-00005E-Vc; Thu, 16 Oct 2014 16:19:36 +0200
Message-ID: <543FD3F9.8040105@olivere.de>
Date: Thu, 16 Oct 2014 16:19:37 +0200
From: Oliver Egginger <bitcoin@olivere.de>
User-Agent: Mozilla/5.0 (X11; Linux x86_64;
	rv:31.0) Gecko/20100101 Thunderbird/31.2.0
MIME-Version: 1.0
To: bitcoin-development@lists.sourceforge.net
References: <CA+s+GJCAWXgpzyQnAar6ecKdcci+tdR8yJjCOUpB=xmj-ytZZQ@mail.gmail.com>	<CABsx9T1U10R4t9NNO9rSSfBxcpOLQNvKFC=7fRKa5Tq41+67cQ@mail.gmail.com>	<CANEZrP1yFOWcJUr+ML73Eoqa=EvYRZivkogdrFdww+5QsOXhBw@mail.gmail.com>	<CALqxMTErVtN2bj7s=DiX4ajzMtQ=M+_DCFQ0=jT6QWUVaXwY_w@mail.gmail.com>
	<CANEZrP0-Rnoe2GzvTs4nztbTMWKVxxuW=qMMwtcgoQJCvRkosA@mail.gmail.com>
In-Reply-To: <CANEZrP0-Rnoe2GzvTs4nztbTMWKVxxuW=qMMwtcgoQJCvRkosA@mail.gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-Spam-Score: -0.0 (/)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
	See http://spamassassin.org/tag/ for more details.
	-0.0 T_RP_MATCHES_RCVD Envelope sender domain matches handover relay
	domain
X-Headers-End: 1XemF8-0001Ug-Lc
Subject: Re: [Bitcoin-development] BIP process
X-BeenThere: bitcoin-development@lists.sourceforge.net
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <bitcoin-development.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
	<mailto:bitcoin-development-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum_name=bitcoin-development>
List-Post: <mailto:bitcoin-development@lists.sourceforge.net>
List-Help: <mailto:bitcoin-development-request@lists.sourceforge.net?subject=help>
List-Subscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
	<mailto:bitcoin-development-request@lists.sourceforge.net?subject=subscribe>
X-List-Received-Date: Thu, 16 Oct 2014 14:41:32 -0000

15.10.2014 at 20:13 Mike Hearn wrote:
> For a project that is based on digital signatures, it's really
> bad that the mailing list is incompatible with Yahoo's "mail signatures
> must be valid" policy.

# Mailman: Do not break existing DKIM signatures
DEFAULT_SUBJECT_PREFIX  = ""
DEFAULT_MSG_HEADER = ""
DEFAULT_MSG_FOOTER = ""

Maybe you should remove these settings. They make little sense and cause
apparently problems for some recipients.

Also the mail body must not be altered through advertising or something
else.

- oliver