Option to disable S/MIME signature check?

[W. Martin Borgert]

Hi,

once in a while I get emails with S/MIME signatures. This is on
public mailing lists, where I seldomly care about signatures,
and I open the email only to read one or two lines to be sure I
can actually press 'd' :~)

Mutt says "Invoking S/MIME..." which takes too long for my taste
(some seconds just to open one email which I will delete anyway)
and then usually: "S/MIME signature could NOT be verified."

I would like to disable this signature check altogether, because
all my real contacts use either PGP or no signature at all.

Is there an option in mutt to do this? Hopefully a run time
option, not a compile time option...

Many TIA & Cheers

[Kevin J. McCarthy]

Post by W. Martin Borgert
Is there an option in mutt to do this? Hopefully a run time
option, not a compile time option...

The compile-time configuration is the cleanest way to turn it off.
However, you could try set smime_verify_command="" (along with
smime_verify_opaque_command and smime_decrypt_command).

Alternatively, you could set crypt_verify_sig=ask-yes, but that affects
both PGP and S/MIME.

[Todd Zullinger]

Post by Kevin J. McCarthy

Post by W. Martin Borgert
Is there an option in mutt to do this? Hopefully a run time
option, not a compile time option...

The compile-time configuration is the cleanest way to turn it off.
However, you could try set smime_verify_command="" (along with
smime_verify_opaque_command and smime_decrypt_command).

Out of curiosity, is it correct that --disable-smime only
applies when building without gpgme? It looks like with
--enable-gpgme, smime will be available via gpgme?

Thanks,

[Kevin J. McCarthy]

Post by Todd Zullinger

Post by Kevin J. McCarthy

Post by W. Martin Borgert
Is there an option in mutt to do this? Hopefully a run time
option, not a compile time option...

The compile-time configuration is the cleanest way to turn it off.
However, you could try set smime_verify_command="" (along with
smime_verify_opaque_command and smime_decrypt_command).

Out of curiosity, is it correct that --disable-smime only
applies when building without gpgme? It looks like with
--enable-gpgme, smime will be available via gpgme?

Yes, if you turn on gpgme it will be available through that.

[W. Martin Borgert]

Post by Kevin J. McCarthy
However, you could try set smime_verify_command="" (along with
smime_verify_opaque_command and smime_decrypt_command).

Thanks, but unfortunately, this did not help. I found that

set crypt_use_gpgme=no

helps however (source: https://bugs.debian.org/838361).