On Wed, Dec 22, 2010 at 04:27:38PM -0500, Ed Blackman wrote: > On Mon, Dec 20, 2010 at 01:23:06PM -0700, Aaron Toponce wrote: > >However, after viewing a message that is signed, when going back to the > >index, the 's' flag will show, even though it didn't show before reading > >the mail. PGP/GPG is working fine, as far as I can tell. I can send > >encrypted mail, decrypt mail, sign and verify signatures. > [...] > There are two kinds of PGP encrypted or signed messages: PGP/MIME > and traditional inline. But only PGP/MIME can be detected in the > headers of the message. My guess is that mutt shows the flags for > the more common PGP/MIME messages all the time, because mutt has to > parse the header for the fields that show up in the index. For > traditional inline PGP, mutt only shows the flags after it's had to > parse the body to display it in the pager.
I believe that this is both correct, and the appropriate explanation. In the past I've done some work on the code that deals with traditional PGP handling, and my recollection matches what you've said. However this particular memory is an old one, and my memory is not what it used to be, so I may be mistaken. =8^) -- Derek D. Martin http://www.pizzashack.org/ GPG Key ID: 0xDFBEAD02 -=-=-=-=- This message is posted from an invalid address. Replying to it will result in undeliverable mail due to spam prevention. Sorry for the inconvenience.
pgpgXv0lySG0u.pgp
Description: PGP signature
