From: Matt Whitlock <bip@mattwhitlock.name>
To: bitcoin-development@lists.sourceforge.net
Subject: Re: [Bitcoin-development] Membership disabled due to bounces
Date: Sun, 21 Jun 2015 07:00:36 -0400 [thread overview]
Message-ID: <2467323.XhrBp4ES7N@crushinator> (raw)
In-Reply-To: <CAJ2OvpjqmVDamKsUvunOkSoLutk3i2TqXwVUJs_zfxWYgCz+2A@mail.gmail.com>
I too got this message and had to re-enable my membership on the list. There's no reason why messages sent by the list to my address would be bouncing.
On Sunday, 21 June 2015, at 9:06 am, Braun Brelin wrote:
> Hi all,
>
> I got a message saying that my membership in the list was disabled due to
> excessive bounces. As far as I can remember, I've only ever sent out one
> e-mail on the list (not including this one) and that was a few weeks ago.
> Has anyone else seen this problem? Could this be related in some way to
> the issues regarding source forge and the mail list hosting issue?
>
> Braun Brelin
next prev parent reply other threads:[~2015-06-21 11:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-21 7:06 [Bitcoin-development] Membership disabled due to bounces Braun Brelin
2015-06-21 11:00 ` Matt Whitlock [this message]
2015-06-21 15:14 ` Laszlo Hanyecz
2015-06-21 19:17 ` Warren Togami Jr.
2015-06-21 19:17 ` Trevin Hofmann
2015-06-21 19:07 Warren Togami Jr.
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=2467323.XhrBp4ES7N@crushinator \
--to=bip@mattwhitlock.name \
--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