On Sun, Mar 17, 2019 at 04:05:38PM -0400, Farhan Khan wrote: > On 19-03-17 11:08 AM, Ian Zimmerman wrote: > > On 2019-03-17 11:40, Kevin J. McCarthy wrote: > > > > > Perhaps try the classic gpg interface instead (turn off > > > $crypt_use_gpgme and source the sample gpg.rc that comes with mutt). > > > > s/Perhaps /Be sure to / > > > > -- > > Please don't Cc: me privately on mailing lists and Usenet, > > if you also post the followup to the list or newsgroup. > > To reply privately _only_ on Usenet and on broken lists > > which rewrite From, fetch the TXT record for no-use.mooo.com. > > I just want to make sure I did this correctly. in gpg.rc, I did this: > set crypt_use_gpgme=no > This does not change the behavior. >
Hi all, I have tried: A. Deleting ~/.gnupg and starting over B. Killing gpg-agent and restarting C. Having an essentially blank .muttrc except for imap/smtps and ~/.gpg.rc D. Adding in set crypt_use_gpgme=no E. Using the 16-character KeyID F. Using the 16-character KeyID prefixed with 0x G. Using the 8-character keyID H. Using the 8-character KeyID prefixed with 0x I. Using the full keyID J. Using the full keyID prefixed with 0x K. I have tried this on FreeBSD 12.0 L. I have tried this on Linux (Mint/Ubuntu) As I said earlier, this seems to be affecting others on the internet. Is it safe to say this is a bug in mutt? --- Farhan Khan PGP Fingerprint: 1312 89CE 663E 1EB2 179C 1C83 C41D 2281 F8DA C0DE