FWIW, I was having this problem today with mutt 1.7.2-1 from stretch,
and I was not able to get around the delay. Sometimes I see some
full-screen dialog, possibly made with ncurses, asking about if I should
accept a (self-signed?) certificate, but I was not able to interact with
it. I didn't wait for the delay, but killed the gpgsm process from a
different terminal to get back to mutt. Mutt then says "S/MIME signature
could NOT be verified", and shows "Error: verification failed: End of
file" in the mail body:
[-- Attachment #1 --]
[-- Type: multipart/signed, Encoding: 7bit, Size: 45K --]
[-- Begin signature information --]
Error: verification failed: End of file
[-- End signature information --]
[-- The following data is signed --]
[-- Attachment #1 --]
[-- Type: text/plain, Encoding: quoted-printable, Size: 2.6K --]
Given that the mutt package in stretch is really a mutt with neomutt
patches, I tried the neomutt 20180512+dfsg.1-1 from unstable, which
works better. There is no delay, but it also says "S/MIME signature
could NOT be verified". However, it shows openssl output in the mail
body instead:
[-- Attachment #1 --]
[-- Type: multipart/signed, Encoding: 7bit, Size: 45K --]
[-- OpenSSL output follows (current time: Mo 11 Jun 2018 12:56:04 CEST) --]
Verification failure
139830712489216:error:21075075:PKCS7 routines:PKCS7_verify:certificate
verify error:../crypto/pkcs7/pk7_smime.c:285:Verify error:self signed
certificate in
certificate chain
[-- End of OpenSSL output --]
[-- The following data is signed --]
[-- Attachment #1 --]
[-- Type: text/plain; charset=utf-8, Encoding: quoted-printable, Size: 2.6K
--]
I also tried setting "pinentry-program /usr/bin/pinentry-tty" in my
~/.gnupg/gpg-agent.conf, but that didn't change the behaviour in
strech-mutt. Neither did setting "set smime_ask_cert_label = no" in my
muttrc.
- Roland
