I have never used "message-hook" before. That looks like a workable
workaround.
I have also never used "spam" before. I wonder if this feature is really
correct for my use-case, which has nothing to do with spam. It might do
the job, but it doesn't feel clean.
There seem to be quite a few users with this issue. Do you think a
boolean option like "crypt_verify_smime" that explicitly works even with
GPGME would be feasible? From a user POV, it sure sounds logical and
useful.
Also, is there a way to shorten the time that SMIME signature
verification needs before timing out? 25 seconds sounds much too long to
me.
Thanks a lot!
Kevin J. McCarthy:
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'
--
ilf
If you upload your address book to "the cloud", I don't want to be in it.
