Hi Mutt & PGP users, hello to the Mutt developers, nobody seems to notice that not only Outlook gets confused by application/pgp messages -- Pine cannot handle them, too!
That means that with an unpatched Mutt it is impossible to create
PGP signed or encrypted emails for Outlook or Pine users, even if you
set pgp_create_traditional.
So why does Pine fail? As has been noted, application/pgp has not
become a standard MIME type. Anyway, Pine proper has never been
PGP-aware, so all it can do is to show this instead of the mail body:
------------------8<---------------------------------------------------
[ Part 1, Application/PGP 5KB. ]
[ Cannot display this part. Press "V" then "S" to save in a file. ]
------------------8<---------------------------------------------------
All the ways I know to integrate PGP/GnuPG into Pine make use of the
display filter facility is triggered my matching text that would be
shown on the screen, so the condition part looks like this:
display-filters=_BEGINNING("-----BEGIN PGP")
For this to work, however, the MIME type needs to be something
displayable, preferably text/plain.
I think this issue is a strong point in favour of ME's suggestion:
On Tue, Jan 08, 2002 at 10:40:53AM -0800, Michael Elkins wrote:
> At this point I have to agree with this sentiment. After six years, we are
> really no furthur to the point of OpenPGP/MIME acceptance. I've personally
> taken to just using a macro in VIM to invoke gpg messages because I have
> to deal with a large number of Outlook users. I endorse changing
> pgp_create_traditional such that for text/plain messages it doesn't alter
> the content-type.
All PGP users I know either use Pine or Outlook, so as far as I am
concerned, (unpatched) Mutt's PGP support is currently only usable for
the Mutt mailing lists -- no matter how pgp_create_traditional is set.
Time for a change of policy (or religion), right?
Cheers,
Cristian
--
}{ Cristian Pietsch
}{ http://www.interling.de
msg22683/pgp00000.pgp
Description: PGP signature
