From mboxrd@z Thu Jan 1 00:00:00 1970 Received: by 10.204.137.132 with SMTP id w4cs177126bkt; Wed, 14 Apr 2010 18:01:42 -0700 (PDT) Received: by 10.216.88.143 with SMTP id a15mr5784132wef.6.1271293302492; Wed, 14 Apr 2010 18:01:42 -0700 (PDT) Return-Path: Received: from rubyforge.org (rubyforge.org [205.234.109.19]) by mx.google.com with ESMTP id v4si2508179wbb.103.2010.04.14.18.01.42; Wed, 14 Apr 2010 18:01:42 -0700 (PDT) Received-SPF: pass (google.com: domain of sup-talk-bounces@rubyforge.org designates 205.234.109.19 as permitted sender) client-ip=205.234.109.19; Authentication-Results: mx.google.com; spf=pass (google.com: domain of sup-talk-bounces@rubyforge.org designates 205.234.109.19 as permitted sender) smtp.mail=sup-talk-bounces@rubyforge.org Received: from rubyforge.org (rubyforge.org [127.0.0.1]) by rubyforge.org (Postfix) with ESMTP id 888C11D799BC; Wed, 14 Apr 2010 21:01:41 -0400 (EDT) Received: from dmz-mailsec-scanner-5.mit.edu (DMZ-MAILSEC-SCANNER-5.MIT.EDU [18.7.68.34]) by rubyforge.org (Postfix) with ESMTP id AC7AB1D78895 for ; Wed, 14 Apr 2010 21:00:46 -0400 (EDT) X-AuditID: 12074422-b7c13ae000003829-79-4bc6653ea70b Received: from mailhub-auth-1.mit.edu (MAILHUB-AUTH-1.MIT.EDU [18.9.21.35]) by dmz-mailsec-scanner-5.mit.edu (Symantec Brightmail Gateway) with SMTP id 86.16.14377.E3566CB4; Wed, 14 Apr 2010 21:00:46 -0400 (EDT) Received: from outgoing.mit.edu (OUTGOING-AUTH.MIT.EDU [18.7.22.103]) by mailhub-auth-1.mit.edu (8.13.8/8.9.2) with ESMTP id o3F10kRH019634 for ; Wed, 14 Apr 2010 21:00:46 -0400 Received: from localhost (XVM-242.MIT.EDU [18.181.2.242]) (authenticated bits=0) (User authenticated as ismith@ATHENA.MIT.EDU) by outgoing.mit.edu (8.13.6/8.12.4) with ESMTP id o3F10jMu016598 for ; Wed, 14 Apr 2010 21:00:45 -0400 (EDT) From: Ian Smith To: sup-talk In-reply-to: <1271251758-sup-5560@hysbald> References: <1270981813-sup-1681@baad> <1271251758-sup-5560@hysbald> Date: Wed, 14 Apr 2010 21:00:45 -0400 Message-Id: <1271293169-sup-4275@baad> User-Agent: Sup/git X-Brightmail-Tracker: AAAAAQCq+Kk= Subject: Re: [sup-talk] GPG (outgoing) X-BeenThere: sup-talk@rubyforge.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: User & developer discussion of Sup List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: sup-talk-bounces@rubyforge.org Errors-To: sup-talk-bounces@rubyforge.org On further testing, removing my signatures (the bit at the bottom of emails, not the digital type) makes Engimail happy. I'm still not sure what hushmail's problem is, but I'm working on that, as well. So my guess is that sup doesn't sign the signature of a message, just what it considers to be the body. Ian Excerpts from Sven Schober's message of Wed Apr 14 09:30:25 -0400 2010: > Hi! > > Excerpts from Ian Smith's message of 2010-04-11 12:30:59 +0200: > > In particular, I can sign (I've been testing mostly with signatures, not > > encryption) using GPG, and send a message successfully; however, while sup > > verifies that it thinks the signature is good, hushmail doesn't recognize the > > message as having a signature (it sees signature.asc as an attachment, but > > doesn't read the message as being signed), and correspondents tell me that > > Enigmail flags my message as having a bad signature. > > > +1 > > > Thanks, > > > > Ian > > > Ciao, > Sven _______________________________________________ sup-talk mailing list sup-talk@rubyforge.org http://rubyforge.org/mailman/listinfo/sup-talk