From mboxrd@z Thu Jan 1 00:00:00 1970 Received: by 10.86.59.13 with SMTP id h13cs419532fga; Tue, 2 Mar 2010 05:46:31 -0800 (PST) Received: by 10.224.123.228 with SMTP id q36mr3283443qar.106.1267537590404; Tue, 02 Mar 2010 05:46:30 -0800 (PST) Return-Path: Received: from rubyforge.org (rubyforge.org [205.234.109.19]) by mx.google.com with ESMTP id 26si13129105qwa.28.2010.03.02.05.46.28; Tue, 02 Mar 2010 05:46:28 -0800 (PST) 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 C4D591588033; Tue, 2 Mar 2010 08:46:27 -0500 (EST) X-Greylist: delayed 393 seconds by postgrey-1.31 at rubyforge.org; Tue, 02 Mar 2010 05:56:42 EST Received: from m157.home.net.pl (m157.home.net.pl [62.129.253.157]) by rubyforge.org (Postfix) with SMTP id AC91C185830B for ; Tue, 2 Mar 2010 05:56:42 -0500 (EST) Received: from 217.98.91.13 (217.98.91.13) (HELO pk-laptop.localnet) by sigarden.home.pl (79.96.31.244) with SMTP (IdeaSmtpServer v0.70) id 099433b9a187f614; Tue, 2 Mar 2010 11:50:00 +0100 From: piotr.kempa@wp.eu To: sup-talk@rubyforge.org Date: Tue, 2 Mar 2010 11:49:59 +0100 User-Agent: KMail/1.13.0 (Linux/2.6.32-ck; KDE/4.4.0; x86_64; ; ) References: <201002261808.36354.kosmici-atakuja@wp.pl> <1267205858-sup-7113@hysbald> In-Reply-To: <1267205858-sup-7113@hysbald> MIME-Version: 1.0 Message-Id: <201003021149.59760.piotr.kempa@wp.eu> X-Mailman-Approved-At: Tue, 02 Mar 2010 08:45:07 -0500 Subject: Re: [sup-talk] PGP INLINE - can't make it work 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: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: sup-talk-bounces@rubyforge.org Errors-To: sup-talk-bounces@rubyforge.org I digged a bit further, trying to decode the emails from commandline with "gpg --decode". For some of the inline GPG emails the commandline version fails, but for some other it works. Even for those that it works, sup just shows undecoded version which leads me to believe it doesn't even try to decode, which means it doesn't recognize the email as encrypted at all. As far as I can deduct, sup only recognizes encrypted emails if they have something like this inside: Content-Type: multipart/encrypted; boundary="nextPart15239034.i9UOPnLxZ9"; protocol="application/pgp-encrypted" Or similar. Which is a reasonable behaviour. On the other hand, if the damned enigmail creates an email with "Content-Type: text/plain;" and then proceeds to include "-----BEGIN PGP MESSAGE-----" in the body, sup treats this as (no surprise) text/plain and doesn't decode. If it tried, it would succeed since this message passed through gpg --decode is decoded okay. So, I guess if this functionality is to be included in sup (and I think it doesn't have to be since enigmail just makes broken messages and there's no reason why anybody should put up with that:) it should not be in crypto.rb but somewhere else, where the decision is made to even use functions from crypto.rb (like decrypt) on a message. I'm no programmer but I guess it should be something like this: if payload contains "BEGIN PGP MESSAGE" then run the decrypt function from crypto.rb on it. For now - does anybody know a way to mass decrypt all messages in my mailbox so I can keep them in plain text and use sup anyway? That would be ideal solution but I just can't find a program to do that. And gpg itself isn't helpful since it just prints decoded payload on --output, without the headers, so it's no use in batch. I can try to code this in bash but maybe there's something out there already? Thank you Piotr On Friday 26 February 2010 18:43:04 Sven Schober wrote: > Excerpts from kosmici-atakuja's message of Fri Feb 26 18:08:36 +0100 2010: > > First of wall I want to say I absolutely love sup! I used all the major mail > > clients like mutt, claws, thunderbird, kmail. All mail clients just fail (mutt > > was the closest though...). Sup so far has the potential to be the best of > > them. If only I can get it to read the inline gpg that enigmail makes... > > > +1 > > > Is there anything I can do to get this working? This is a crucial feature for > > me... > > > +1 > > Moreover, I searched the list archives and it looks like some people have got > > it working as there have been patches to make it work a couple of months ago. > > And my version is recent (January) so those patches should be in it. It just > > doesn't for me for some reason :( > > > I think there was a (preliminary) patch from Michael Stapelberg > floating around, but somehow that didn't make it into next? > > > I know I should read crypto.rb and figure it out from there. I tried, I just > > can't understand it, as I'm not experienced in ruby, or email clients code for > > that matter. > > > +1 > > > Please help! > +1 > > > Thank you > > Piotr > > Ciao, > Sven > -- > Sven Schober, sven.schober@uni-ulm.de |UNI ULM > http://www-vs.informatik.uni-ulm.de/dept/staff/schober/ |DISTRIBUTED > Room O27-346, Phone: +49-731-5024146 [+49-179-5060182] |SYSTEMS LAB > _______________________________________________ sup-talk mailing list sup-talk@rubyforge.org http://rubyforge.org/mailman/listinfo/sup-talk