public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Oliver Egginger <bitcoin@olivere.de>
To: bitcoin-development@lists.sourceforge.net
Subject: Re: [Bitcoin-development] BIP process
Date: Thu, 16 Oct 2014 16:19:37 +0200	[thread overview]
Message-ID: <543FD3F9.8040105@olivere.de> (raw)
In-Reply-To: <CANEZrP0-Rnoe2GzvTs4nztbTMWKVxxuW=qMMwtcgoQJCvRkosA@mail.gmail.com>

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



  parent reply	other threads:[~2014-10-16 14:41 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-15  8:29 [Bitcoin-development] BIP process Wladimir
2014-10-15  9:22 ` Gregory Maxwell
2014-10-15  9:36   ` Wladimir
2014-10-15 18:58     ` Cory Fields
2014-10-16  7:50     ` Thomas Zander
2014-10-15 15:37 ` Gavin Andresen
2014-10-15 15:46   ` Mike Hearn
2014-10-15 15:54     ` Adam Back
2014-10-15 16:47       ` Peter Todd
2014-10-15 18:13       ` Mike Hearn
2014-10-16  7:38         ` Thomas Zander
2014-10-16 14:19         ` Oliver Egginger [this message]
2014-10-15 19:00       ` Btc Drak
2014-10-15 19:40         ` Peter Todd
2014-10-16  4:41           ` Luke Dashjr
2014-10-19  7:17 ` xor
2014-10-19  9:42   ` Btc Drak
2014-10-19  9:49   ` Wladimir
2014-10-19 18:58   ` Thomas Zander
2014-10-20  0:33   ` odinn
  -- strict thread matches above, loose matches on Subject: below --
2011-10-18 19:17 Gavin Andresen
2011-10-18 21:26 ` Nils Schneider
2011-10-20  5:02 ` Alex Waters
2011-10-20 11:27   ` Christian Decker

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=543FD3F9.8040105@olivere.de \
    --to=bitcoin@olivere.de \
    --cc=bitcoin-development@lists.sourceforge.net \
    /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