-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Mon, Feb 29, 2016 at 12:32:31AM -1000, Joel Roth wrote: > tomás wrote: > > > On Sun, Feb 28, 2016 at 10:21:43PM -1000, Joel Roth wrote: > > > Hi, > > > > > > I have gpg installed (package gpgv). > > > > > > I tried putting "source /etc/Muttrc.d/gpg.rc" at the end of > > > ~/.muttrc, and also putting "source /etc/Muttrc" at the > > > beginning. > > > > (1) Does it ask you for a passphrase -- or does it fail right away? > > (2) I'm assuming that you are looking at one message encrypted to > > you. What happens if you > > - copy this message to a file on its own (in mutt's index, > > type "C" and give it a file name say "foo") > > - from a shell, do "gpg -d foo"? > > Hi Tomás, > > I noticed that it is signed messages, like yours, that cause the > hiccup. I can't view them with the space bar (could not copy > message), but I can see them (including the signature text) > with the 'v' key.
Is it only *some* signed messages? I'm asking because my messages are signed using the somewhat antiquated "traditional PGP" (or some such) scheme[1]. The message from Nicolas George in this thread is more "modern": does this one also trigger your problem? [1] I know, I know. I'm fixing that Real Soon Now(TM) regards - -- t -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (GNU/Linux) iEYEARECAAYFAlbUGrsACgkQBcgs9XrR2kbJ2gCfcCmidG4cctkl6lfmWfyb+NOh K9QAn1NItTAdwV6zznjLxqZ330GCXplr =fxTT -----END PGP SIGNATURE-----
