On 19-03-17 11:40 AM, Kevin J. McCarthy wrote: > On Sat, Mar 16, 2019 at 11:12:22PM -0400, Farhan Khan wrote: > > On 19-03-17 11:02 AM, Kevin J. McCarthy wrote: > > > > What does `gpg --list-keys --list-options show-usage` show for the > > > key? Is the encryption flag [E] present? > > > Yes, one of the subkeys is listed with [E]. > > > > pub rsa2048 2017-09-10 [SC] [expires: 2019-09-10] > > XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX > > uid [ultimate] Username <user@domain> > > sub rsa2048 2017-09-10 [E] [expires: 2019-09-10] > > > > Notice that its listed as ultimate. This is only because it used to be > > my key before switching emails, so I specifically changed the trust. > > Please reply to the list, not me personally, so that others can contribute. > I've redirected my reply back to the list. > > Off the top of my head, I'm not sure what the problem is. Perhaps try the > classic gpg interface instead (turn off $crypt_use_gpgme and source the > sample gpg.rc that comes with mutt). > > Alternatively, check the output of > gpg --no-verbose --batch --quiet --with-colons --with-fingerprint > --with-fingerprint --list-keys <keyid> > > I don't think gpg --list-keys would include disabled keys, but perhaps one > of the flags in that output will make things clearer. > > -- > Kevin J. McCarthy > GPG Fingerprint: 8975 A9B3 3AA3 7910 385C 5308 ADEF 7684 8031 6BDA
I have searched all over Google/Duck with no luck. However, a lot of people are reporting the same issue. I suspect this is a bug in Mutt. --- Farhan Khan PGP Fingerprint: 1312 89CE 663E 1EB2 179C 1C83 C41D 2281 F8DA C0DE
signature.asc
Description: PGP signature