Re: content-type: application/pgp

 --- Dirk Nimmich <[email protected]> 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.

It's passed to metamail. See
<news:[email protected]> in 
alt.os.linux.slackware for an example of that.

> application/pgp is also not listed at
> <http://www.iana.org/assignments/media-types/application/>,

RFC 3156 refers to "the since withdrawn 'application/pgp' content type."

> so I am
> curious why you thought it might be important.

I don't. Just a while back I saw a message with that content-type, and 
added a note to my TODO list. If I really thought it important, I'd write
automatic pgp verification/signing support.

> "Clearsigned" messages should probably just have text/plain as their
> Content-Type because they are just this. What user agents generate
> application/pgp instead?

I don't know about any specific news user agents, though as I said I've seen it
used in the past. I know (since I used it with tin's MH Maildir support to test
the patch) that Mutt creates application/pgp when $pgp_create_traditional is
set. Its manual also contains a procmail recipe to change clearsigned messages
to application/pgp.


=====
-- 
Joshua 'bruce' Crawford ... http://www.geocities.com/mortarn

http://personals.yahoo.com.au - Yahoo! Personals
New people, new possibilities. FREE for a limited time.