Re: content-type: application/pgp
Andreas Metzler <[email protected]>
| Newsgroups | gmane.network.tin.devel,gmane.network.tin.user |
|---|---|
| Message-ID | <[email protected]> |
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Tue, Nov 11, 2003 at 11:23:40PM +0100, Dirk Nimmich wrote:
> Joshua Crawford wrote:
>> Attached is a little patch to handle articles with content-type:
>> application/pgp as though they are text/plain, which they are, being
>> clearsigned.
> According to RFC 3156 the proper Content-Type for signed data is
> multipart/signed with a normal text/plain part and an application/
> pgp-signature part, so this should be detected already by tin.
> application/pgp is also not listed at
> <http://www.iana.org/assignments/media-types/application/>, so I am
> curious why you thought it might be important.
> "Clearsigned" messages should probably just have text/plain as their
> Content-Type because they are just this. What user agents generate
> application/pgp instead?
mutt used it. (Afaict not any mor, see this mail.) Although mutt-users
normally just use PGP/MIME instead ;-)
cu andreas
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)
iD8DBQE/ses4HTOcZYuNdmMRAsXQAKCFX4aBTjwbb5rIoYiApovkY+y7rQCePXKF
OqE/5nG/6hABrEkta7kJ4XI=
=HqIj
-----END PGP SIGNATURE-----