Mutt's GNUpg signing.

[Theo v. Werkhoven]

* Wed, 12 Nov 2003, jas at extundo.com:

> "Theo v. Werkhoven" <twe-gpg at ferrets4me.xs4all.nl> writes:
> 
> > # Mime-Version: 1.0
> > # Content-Type: application/pgp; x-action=sign; format=text
> > # Content-Disposition: inline; filename="msg.pgp"
> 
> What is 'format=text'?  RFC 2646 only describe 'flowed' and 'fixed' as
> values for the 'format' variable.
> 
> I believe using either PGP/MIME (RFC 3156), or inline PGP within
> text/plain parts, is more likely to work, than (like your MUA does)
> using inline PGP within application/pgp.  The content type
> application/pgp is not even registered with IANA, as far as I can
> tell.

I believe you. I wouldn't have a clue where mutt 1.4.1 gets the settings to
use these headers. But in the mean time I installed 1.5.5, which does
what the doctor ordered:
Content-Type: text/plain; charset=us-ascii; x-action=pgp-signed
Content-Disposition: inline

Problem solved afaik.
Thanks.

Theo
-- 
Theo v. Werkhoven    Registered Linux user# 99872 http://counter.li.org
ICBM 52 13 27N , 4 29 45E.
See headers for PGP/GPG info.
gpg-1.2.2rc1
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 198 bytes
Desc: not available
Url : /pipermail/attachments/20031112/bc62e7f2/attachment.bin