-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Is there anything wrong with hitting F in the compose menu and filtering the message through the "gpg --clearsign" command?
- -R On Thu, Apr 04, 2002 at 01:50:25PM -0800, Will Yardley wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Peter T. Abplanalp wrote: > > > > given the above, i know mutt handles pgp/mime natively and that it can > > do application/pgp with the pgp_create_traditional. my problem is > > that neither of these formats appears to work if the recipient is > > using outlook. btw - the outlook is set up to use the g-data > > gnu-plugin. is there a way to get mutt to use ascii armor and will > > that be viewable by my outlook user? will the ascii armor work for > > encryption as well? > > you want to use pgp_create_traditional, but you want the content type to > be set as ascii text. > > so basically, you would need to run either 1.2.5 or 1.3.x with the > pgp_outlook_compat patch (i think there's a version for 1.2.5, which it > looks like you're running currently), or the cvs version, which (as you > can see) can create a traditional message in a way that will be read by > MUAs other than mutt. > > - -- > Will Yardley > input: william < @ hq . newdream . net . > > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.0.6 (GNU/Linux) > Comment: public key: http://infinitejazz.net/will/pgp/gpg.asc > > iD8DBQE8rMqhswHW5vg5XAIRAi87AJ0TfPST/Tb/iXZEpBJ4Wm92HHF+kACfXoZG > E07ZQlgV/QHK3uAjv77xpms= > =a01s > -----END PGP SIGNATURE----- - -- Robert S Conde PGP Key: 0xE94C96E3 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.1 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE8rPilRDpbEulMluMRAp1NAJ4naWeX6TL3N1I6vxKb20YlACGe5wCeJEjT T3hU6C3hTefMrffq2xjhQpE= =NeCV -----END PGP SIGNATURE-----
