I asked on gnupg-users. Adding "disable-dirmngr" to gpgsm.conf disbles
the use of the Dirmngr and thus expensive online checks that can take a
long time to timeout. This is a viable workaround.
I still believe it would be great to have an option in Mutt not to use
GPGME for S/MIME in the
Done, thanks: https://gitlab.com/muttmua/mutt/-/issues/450
Kevin J. McCarthy:
Yes, please go ahead. I don't have a current timeline for starting
master development again, but when I do, it will be good to have the
request there.
--
ilf
If you upload your address book to "the cloud", I
On Mon, Jul 31, 2023 at 08:43:22PM +0200, ilf wrote:
Do you think I should file a feature request for this in the tracker?
Yes, please go ahead. I don't have a current timeline for starting
master development again, but when I do, it will be good to have the
request there.
Thank you.
--
Do you think I should file a feature request for this in the tracker?
Kevin J. McCarthy:
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
On Sat, Jul 29, 2023 at 02:48:56PM +0200, ilf wrote:
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.
It _is_ a "creative" use of the spam command. I think if
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
On Wed, Jul 26, 2023 at 09:37:34AM +0800, Kevin J. McCarthy wrote:
spam content-type:.*pkcs7 smime
Sorry, it's a good idea to root the regexp above:
spam ^content-type:.*pkcs7 smime
--
Kevin J. McCarthy
GPG Fingerprint: 8975 A9B3 3AA3 7910 385C 5308 ADEF 7684 8031 6BDA
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
Hi
I would also like to disable the S/MIME signature check. I have no use
for it. And "Invoking S/MIME..." takes 25 seconds before failing with
"S/MIME signature could NOT be verified."
I do use OpenPGP. So disabling "crypt_use_gpgme" is not an option for
me, same for changing
On Tue, May 15, 2018 at 03:27:15PM -0400, Todd Zullinger wrote:
> Kevin J. McCarthy wrote:
> > On Tue, May 15, 2018 at 09:40:38AM +0200, W. Martin Borgert wrote:
> >> Is there an option in mutt to do this? Hopefully a run time
> >> option, not a compile time option...
> >
> > The compile-time
On 2018-05-15 09:06, Kevin J. McCarthy wrote:
> 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:
Kevin J. McCarthy wrote:
> On Tue, May 15, 2018 at 09:40:38AM +0200, W. Martin Borgert wrote:
>> 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
On Tue, May 15, 2018 at 09:40:38AM +0200, W. Martin Borgert wrote:
> 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
13 matches
Mail list logo
