begin quoting what Thomas Roessler said on Tue, Apr 02, 2002 at 05:59:32PM +0200:
OpenPGP specifies application/pgp, but that breaks some MUAs that
don't follow the OpenPGP RFC.
Where does the OpenPGP RFC specify that?
Sorry, I mispoke; it was another standard that specified that, and it
Will --
...and then Will Yardley said...
%
% -BEGIN PGP SIGNED MESSAGE-
% Hash: SHA1
%
% for those not on the mutt dev list, pgp_create_traditional works again
% in 1.5.0 (cvs version - a patch from Armin Wolfermann), and the behavior
Yay. That's always nice.
% has been changed so
begin quoting what David T-G said on Wed, Mar 27, 2002 at 07:55:08AM -0500:
% has been changed so that application/pgp is no longer used (although
% there's an x-mutt-action=pgp-sign flag in the content/type so that mutt
% knows it's signed). those changes are from Thomas Roessler.
I
Shawn --
...and then Shawn McMahon said...
%
% begin quoting what David T-G said on Wed, Mar 27, 2002 at 07:55:08AM -0500:
%
% % has been changed so that application/pgp is no longer used (although
% % there's an x-mutt-action=pgp-sign flag in the content/type so that mutt
% % knows it's
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
for those not on the mutt dev list, pgp_create_traditional works again
in 1.5.0 (cvs version - a patch from Armin Wolfermann), and the behavior
has been changed so that application/pgp is no longer used (although
there's an x-mutt-action=pgp-sign
