Re: pgp encoding was Re: Apache / php-cgi
Well with you it's not a problem!
Your whole message has appeared as the body in my client, but in the case of
Tom, for example, and Claudio too now, I get the message body as a text file
attachment, and a PGP key as another attachment, and it makes reading the
list.. A pain.
I'm not even going to tell you what client I use because I'll be flamed to
pieces :P
Although, I suspect it's telling you all in the headers :)
/Phil
----- Original Message -----
From: "Geoff Crompton" <geoff.crompton@bjhcontrols.com.au>
To: <debian-user@lists.debian.org>
Sent: Wednesday, July 31, 2002 6:12 AM
Subject: pgp encoding was Re: Apache / php-cgi
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On Wed, 31 Jul 2002 14:56, Tom Cook wrote:
> > On 0, Phillip Baker <phil@lchost.co.uk> wrote:
> > > Cheers for your reply (although confusingly my mail client has
> > > inexplicably munged it and your PGP key into attachments - probably
> > > thanks to your mail client labelling it multipart)
> >
> > *shrug* isn't that how it's supposed to be?
>
> That is something I have been wondering about recently. I have noticed
that
> KMail (1.3.2) just puts PGP stuff inline. But mutt (1.3.28i) does
multipart
> mime attachements for pgp signatures. And each program doesn't understand
the
> others way of doing it.
>
> So which is the 'proper' way. Do later versions of mutt/Kmail do it the
> 'proper' way?
>
> Cheers
> Geoff Crompton
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.0.6 (GNU/Linux)
> Comment: For info see http://www.gnupg.org
>
> iD8DBQE9R3HKx8QbdaYmRS8RAsRaAJ0ZQA5VO4k7luVOgWw/CksarCR/HACghSy9
> /zWR2Kf9hZWV+du3xPqtYrs=
> =VbvG
> -----END PGP SIGNATURE-----
>
>
> --
> To UNSUBSCRIBE, email to debian-user-request@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact
listmaster@lists.debian.org
>
>
Reply to: