On Tue, Jul 25, 2023 at 12:32:40PM +0200, ilf wrote:
I do use OpenPGP. So disabling "crypt_use_gpgme" is not an option for me, same for changing "crypt_verify_sig".In the old thread from 2018, Kevin J. McCarthy proposed this:However, you could try set smime_verify_command="" (along with smime_verify_opaque_command and smime_decrypt_command).But this does not work. According to muttrc(5) the default value for these three options is already "", and I am not setting them anywhere.
That option only works when $crypt_use_gpgme is unset.
So: How can I disable the S/MIME signature check while still using GPGME for OpenPGP?
The option $crypt_verify_sig is shared between PGP and S/MIME, so you'll have to be creative if you are using GPGME. Maybe something like: spam content-type:.*pkcs7 smime message-hook ~A 'set crypt_verify_sig=yes' message-hook '~H smime' 'set crypt_verify_sig=no' # or '=ask-no' -- Kevin J. McCarthy GPG Fingerprint: 8975 A9B3 3AA3 7910 385C 5308 ADEF 7684 8031 6BDA
signature.asc
Description: PGP signature
