public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Andy Schroder <info@AndySchroder.com>
To: Peter Todd <pete@petertodd.org>
Cc: bitcoin-development@lists.sourceforge.net
Subject: Re: [Bitcoin-development] Is SourceForge still trustworthy enough to host this list?
Date: Wed, 10 Jun 2015 16:03:57 -0400	[thread overview]
Message-ID: <5578982D.7010807@AndySchroder.com> (raw)
In-Reply-To: <20150610194301.GC21416@savin.petertodd.org>

[-- Attachment #1: Type: text/plain, Size: 2042 bytes --]

Hello,

Thanks for testing this clarifying things about PGP/MIME and I apologize 
for wasting your time with it. It looks like a SPAM filtering service I 
use is re-writing some parts of some plain text messages with some 
special/alternate encoding characters (not sure what it really is). 
Anyway, if I manually export/import a message from gmane (bypassing my 
e-mail SPAM filter), thunderbird/enigmail is not having problems 
verifying signatures. I guess I never realized this before because all 
other signed messages I normally receive are encrypted and the SPAM 
filter does not mess with non plain text data.



Andy Schroder

On 06/10/2015 03:43 PM, Peter Todd wrote:
> On Wed, Jun 10, 2015 at 03:36:42PM -0400, Andy Schroder wrote:
>> It's possible that the enigmail extension is not working right, but
>> I was under the impression that it is just feeding data to gpg and
>> then receiving the response back. It's possible that your e-mail you
>> just checked was not sent through mailman since I also replied
>> directly to you explicitly (in which case the message has not been
>> modified) and you probably have the setting in the mailing list set
>> to not send duplicate messages if you are an explicit TO. I just
>> deleted all explicit TOs for this message, so everyone should be
>> receiving it through the mailing list and not directly. Is the
>> signature still valid for you now? I think enigmail can handle
> It has perfectly valid signatures, as do your earlier messages to the
> list.
>
>> messages with some signed and unsigned content, and maybe PGP/MIME
>> inherently does not support this and a mailing list re-writing parts
>> of messages is an expected action? If this message re-writing is an
>> expected action and I'm correct that PGP/MIME does not support
>> partially signed content, then maybe it is just a recommendation for
>> this mailing list to not use PGP/MIME for messages sent to the list?
> PGP/MIME definitely does support partially signed content.
>



[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 555 bytes --]

  reply	other threads:[~2015-06-10 20:04 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-10  8:25 [Bitcoin-development] Is SourceForge still trustworthy enough to host this list? xor
2015-06-10  9:35 ` Wladimir J. van der Laan
2015-06-10 16:46   ` Andy Schroder
2015-06-10 18:02     ` Troy Benjegerdes
2015-06-10 18:41       ` Andy Schroder
     [not found]       ` <DB12E925-11C6-4A82-BC81-FB3DA26BC5B3@newcastle.ac.uk>
     [not found]         ` <20150610185810.GQ27932@nl.grid.coop>
     [not found]           ` <DB5PR07MB091974E06974EA88136F60C2B5BD0@DB5PR07MB0919.eurprd07.prod.outlook.com>
2015-06-11  1:46             ` Troy Benjegerdes
2015-06-10 18:28     ` Ivan Brightly
2015-06-10 18:47       ` Troy Benjegerdes
2015-06-10 19:13         ` Ivan Brightly
2015-06-10 18:36     ` s7r
2015-06-10 18:59       ` Andy Schroder
2015-06-10 19:03         ` Peter Todd
2015-06-10 19:12           ` Andy Schroder
2015-06-10 19:20             ` Peter Todd
2015-06-10 19:36               ` Andy Schroder
2015-06-10 19:43                 ` Peter Todd
2015-06-10 20:03                   ` Andy Schroder [this message]
2015-06-10 19:54         ` Jeff Garzik
2015-06-11  9:27       ` Wladimir J. van der Laan

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=5578982D.7010807@AndySchroder.com \
    --to=info@andyschroder.com \
    --cc=bitcoin-development@lists.sourceforge.net \
    --cc=pete@petertodd.org \
    /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