Cristian <[EMAIL PROTECTED]> [10 Jan 2002 00:04 +0100]: > On Wed, Jan 09, 2002 at 02:47:50PM -0800, Jonathan Irving wrote: > > Yes, but as has been pointed out a number of times, the patch > > does not cause the MIME type to be set to text/plain. > > This is just wrong. Setting the mime type to text/plain instead of > application/pgp is the very purpose of the ``PGP Outlook compatibility > patch'' (which I call ``PGP compatibility patch''). > > What has confused a few people is the fact that the patch is effective > only if both pgp_outlook_compat and pgp_create_traditional are set.
You're right. My bad. In fact, I had been using both of these. I believe the problem is actually the Content-Disposition header, which is "inline; filename=msg.pgp" Is this just an artifact of pgp_create_traditional? Without the filename=msg.pgp, I guess the other-MUA-sees-only- attachments problem that Nick described, and I've experienced, would go away. > > The proposal is to dump application/pgp, and make p_c_t result in > > a plain text MIME type for clearsigned messages. > > That's right. This can be achieved by integrating the patch into the > next full release of Mutt. With the above fix? Or am I missing something. -- http://www.epic.org - Electronic Privacy Information Center
msg22739/pgp00000.pgp
Description: PGP signature
