[prev in list] [next in list] [prev in thread] [next in thread] 

List:       sylpheed
Subject:    [sylpheed:14682] Re: Sylpheed and gnupg
From:       Michael Sharp <freebsd () ec ! rr ! com>
Date:       2002-06-30 18:21:45
[Download RAW message or body]

yep, cleared things up, thx Bill. I'll just encrypt and paste/attach the ASCII portion into the body.  I figured it was something to do with Outlook.  Gotta love em.

michael

On Sun, 30 Jun 2002 11:12:36 -0700
Bill Thompson <Billt@Mahagonny.com> wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> On Sun, 30 Jun 2002 13:19:16 -0300
> Cesar Santos <zincum@myrealbox.com> wrote:
> 
> > On Sat, 29 Jun 2002 23:58:15 -0400
> > Michael Sharp <freebsd@ec.rr.com> wrote:
> > 
> > MS> When sending mail to a user that I encrypt and sign using gnupg, the
> > MS> message is received as two .dat attachments and nothing in the
> > MS> message body.
> > MS> 
> > MS> Is there a way to have the encrypted message shown in the message
> > MS> body instead of the user having to save 2 .dat files ?
> > 
> > 
> > I can only do that using Sylpheed version 0.7.2claws plus gpgme and
> > choosing Privacy/Plain ASCII armored, but got a warning to not do this
> > because it doesn't comply with RFC 3156.  I have tried different methods
> > of configuration with 0.7.8claws without any success.
> > 
> > -- 
> > Cesar Santos
> > zincum@myrealbox.com
> > SuSE 8.0 GnuPG 1.0.7
> > 
> 
> This comes up quite often. I'm not sure if it in in an FAQ somewhere or
> not.
> 
> The first problem that Michael Sharp is having is that his recipient is
> using g Outlook. Sylpheed does comply with RFC 3156 for handling PGP/MIME,
> but Outlook does not. M$ in their infinite wisdom chose not to add
> PGP/MIME to the recognized MIME types for Outlook, and for some reason did
> not give the user a method to add unknown MIME types. The best way to
> handle PGP and Outlook is with ASCII armored PGP signatures.
> 
> The issues that Cesar Santos is having relates to GPGME. The setting in
> the account preferences for Plain ASCII is valid and complies with RFC
> 2440 which is the OpenPGP standard. I believe the warning is set to
> encourage users to use the PGP/MIME standard instead. The holy war between
> the two standards is not something I want to get into here.
> 
> As I understand it, GPGME handles Plain ASCII encryption very well, but
> not Plan ASCII signatures. It is because of this that the setting in the
> account preferences for Plain ASCII only works for fully encrypted
> messages. Signatures are still send as PGP/MIME even if this is selected.
> Hopefully a future version of GPGME will support Plain ASCII signatures as
> well.
> 
> In the mean time, the good folks who put Sylpheed-Claws together have
> included a perl script called "gpg-sign". This should be included in the
> tools directory of the Sylpheed-Claws source and can be called from inside
> claws with the Actions feature with "|gpg-sign|". The only trick I have
> found in using it is to make sure you word wrap your message before using
> the script.
> 
> I hope that clears things up for you. If I got anything wrong here, I hope
> that someone will feel free to correct me. I'll try to compile all this
> information into a coherent document for claws in the near future.
> 
> - -- 
> BillT@Mahagonny.com - PGP KeyID#: 0xFB966670
> 
> "Crappy old OSes have value in the basically negative sense that 
> changing to new ones makes us wish we'd never been born."
>                                 -Neal Stephenson 1999
> 
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.0.6 (GNU/Linux)
> Comment: For info see http://www.gnupg.org
> 
> iD8DBQE9H0kiuLPldPuWZnARAnSsAKCqWcBiFQHNs97JSDtBHKllYY217ACg97qO
> ENygw+FcXk+mJWJW60/K5ec=
> =+85e
> -----END PGP SIGNATURE-----
[prev in list] [next in list] [prev in thread] [next in thread]