[Fw: [OT] Content-Disposition: inline?]

[Justin R. Miller]

--1Y7d0dPL928TPQbc
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

Thus spake Michael H. Warfield (mhw@wittsend.com):

> 	That's funny...  I use Mutt (1.3.20 currently) with gpg (1.0.6
> with ldap patch currently) and I never have signed messages come out
> as multipart Mime.  I get one part and it's signed inline.  Mutt sends
> it and recognizes it. =20

Here's the line from my gpg.rc:=20

	set pgp_sign_command=3D"gpg --no-verbose --batch --output - --passphrase-f=
d 0 --armor --detach-sign --textmode %?a?-u %a? %f"

As opposed to this one, which doesn't seem to be used:=20

	set pgp_clearsign_command=3D"gpg --no-verbose --batch --output - --passphr=
ase-fd 0 --armor --textmode --clearsign %?a?-u %a? %f"

> 	Do you need to use Mime?  Is there any problem with using clearsign
> signatures on the message itself?

As I understand it, PGP/MIME is the new standard and inline signing
and/or encryption is considered to be deprecated. =20

--=20
| Justin R. Miller / justin@solidlinux.com / 0xC9C40C31
| Of all the things I've lost, I miss my pants the most.
----------------------------------------------------------

--1Y7d0dPL928TPQbc
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE7oSGS94d6K8nEDDERAkfKAJ4kacDoEs9SN9oGxIBqrN+V7F5eMQCfea5a
ecoaKitq8QI3n4i/hEgzzV0=
=AD3G
-----END PGP SIGNATURE-----

--1Y7d0dPL928TPQbc--