Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193] helo=mx.sourceforge.net) by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1Z2mEI-0003wp-DB for bitcoin-development@lists.sourceforge.net; Wed, 10 Jun 2015 20:04:06 +0000 X-ACL-Warn: Received: from uschroder.com ([74.142.93.202]) by sog-mx-3.v43.ch3.sourceforge.com with esmtp (Exim 4.76) id 1Z2mEH-00050j-AK for bitcoin-development@lists.sourceforge.net; Wed, 10 Jun 2015 20:04:06 +0000 Received: from [192.168.253.4] (cpe-74-132-161-228.kya.res.rr.com [74.132.161.228]) by uschroder.com (Postfix) with ESMTPSA id 6FA0622DF2057; Wed, 10 Jun 2015 16:04:00 -0400 (EDT) Message-ID: <5578982D.7010807@AndySchroder.com> Date: Wed, 10 Jun 2015 16:03:57 -0400 From: Andy Schroder User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0 MIME-Version: 1.0 To: Peter Todd References: <1943127.DBnVxmfOIh@1337h4x0r> <20150610093556.GA11409@amethyst.visucore.com> <557869F9.8030109@AndySchroder.com> <557883A7.7030906@sky-ip.org> <55788924.6090008@AndySchroder.com> <20150610190320.GA1229@savin.petertodd.org> <55788C02.1010105@AndySchroder.com> <20150610192004.GB21416@savin.petertodd.org> <557891CA.5010708@AndySchroder.com> <20150610194301.GC21416@savin.petertodd.org> In-Reply-To: <20150610194301.GC21416@savin.petertodd.org> X-Enigmail-Version: 1.6 OpenPGP: id=2D44186B; url=http://andyschroder.com/static/AndySchroder.asc Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="99I1925UhDmMkgvOooO5Lrc2901127kdr" X-Spam-Score: 0.1 (/) X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. See http://spamassassin.org/tag/ for more details. 0.1 AWL AWL: Adjusted score from AWL reputation of From: address X-Headers-End: 1Z2mEH-00050j-AK Cc: bitcoin-development@lists.sourceforge.net Subject: Re: [Bitcoin-development] Is SourceForge still trustworthy enough to host this list? X-BeenThere: bitcoin-development@lists.sourceforge.net X-Mailman-Version: 2.1.9 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Jun 2015 20:04:06 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --99I1925UhDmMkgvOooO5Lrc2901127kdr Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable 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=20 use is re-writing some parts of some plain text messages with some=20 special/alternate encoding characters (not sure what it really is).=20 Anyway, if I manually export/import a message from gmane (bypassing my=20 e-mail SPAM filter), thunderbird/enigmail is not having problems=20 verifying signatures. I guess I never realized this before because all=20 other signed messages I normally receive are encrypted and the SPAM=20 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. > --99I1925UhDmMkgvOooO5Lrc2901127kdr Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQEcBAEBAgAGBQJVeJgtAAoJEDT679stRBhr2qkIAKWJhkF8ssAHw1J2/4y+Mxkc Zr70nVjjiMQYSj9sI6wt981/IKUwHs9Y8h+o1cqZJas72KCDWc2u+RcGwPl90YoC 8FDvdNVLyzGyYtXN0THCGNiqXXM9wof94X6ndzZL2nPWEd4rn5GrvZcHHWyDvHUD TooK3pDbvEyjijMugwVxhsNqCoVn4+YD+2eq/jrAVfq0uqxQ6qNsmISm0fKo3Hos z1LMy/lm29dPUs8CpxHl5QBFvsIgpeUo8mHMx+fi44TIxUfaTNJ6KXDG9p3PI06x 6x9nlght0Iw5bKo2bzDoARSyVsuwUKclIY2AxSpgJIY5kM0XMLTZeH0EMyHfqOE= =BB7e -----END PGP SIGNATURE----- --99I1925UhDmMkgvOooO5Lrc2901127kdr--