From: grarpamp <grarpamp@gmail•com>
To: bitcoin-dev@lists•linuxfoundation.org
Subject: Re: [bitcoin-dev] Mailing List Administrivia - GPG, Archives, Breakage, TODO, mirrors, etc
Date: Thu, 16 Jul 2015 00:57:19 -0400 [thread overview]
Message-ID: <CAD2Ti2_xmrrL=pgEz=VDJz1QZ3NU17h+1mbW2FGynGwRpnye1A@mail.gmail.com> (raw)
In-Reply-To: <CAEz79Pp7XyAjdN_e7BnwJfqp=ZaSk7hQSwMJiev-9R5orKyUew@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 837 bytes --]
On Sun, Jun 28, 2015 at 10:27 PM, Warren Togami Jr. <wtogami@gmail•com> wrote:
> Mailman's obscure_addresses option is now disabled. It has been pretty
> useless as a spam mitigation measure anyway.
>
> This is a test message to see if mailman continues to break --clearsign GPG
> signatures for messages that contain an e-mail address like
> test@example•com.
Still broken, in both the web "archives" and the "mbox" archives.
http://lists.linuxfoundation.org/pipermail/bitcoin-dev/2015-June/009252.html
http://lists.linuxfoundation.org/pipermail/bitcoin-dev/2015-June.txt.gz
Note also, as outlined with other issues in the OP, the below attachment
will not appear in the "mbox" archives, thus becoming lost to mirrors and
users rightly attempting to use the "mbox" archives as their canonical source
for local seeding or MUA access.
[-- Attachment #2: lost.c --]
[-- Type: text/x-csrc, Size: 224 bytes --]
#include <stdio.h>
#include <stdlib.h>
int main () {
printf("Hello World, this valuable bit of example code ends up @lost from the \"mbox\" archives.\n");
/* A strudel was placed in the above string too. */
exit(1);
}
next prev parent reply other threads:[~2015-07-16 4:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-27 22:21 grarpamp
2015-06-27 23:54 ` Jeff Garzik
2015-06-29 2:27 ` Warren Togami Jr.
2015-07-16 4:57 ` grarpamp [this message]
2015-07-16 5:08 ` grarpamp
2015-07-03 22:07 ` Peter Todd
2015-06-29 1:49 ` Andy Schroder
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='CAD2Ti2_xmrrL=pgEz=VDJz1QZ3NU17h+1mbW2FGynGwRpnye1A@mail.gmail.com' \
--to=grarpamp@gmail$(echo .)com \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
/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