From: Justus Winter <justus@sequoia-pgp.org>
To: navse@mailbox.org, "notmuch@notmuchmail.org" <notmuch@notmuchmail.org>
Subject: Re: Emacs lagging for ~4min when opening from certain email.
Date: Mon, 24 Jan 2022 14:02:33 +0100 [thread overview]
Message-ID: <8735ldxp5i.fsf@europ.lan> (raw)
In-Reply-To: <404620549.699733.1642996721419@office.mailbox.org>
[-- Attachment #1.1: Type: text/plain, Size: 944 bytes --]
Hi,
navse@mailbox.org writes:
> I have been using Notmuch with Emacs for a couple of days and it has
> been working great, except for when I open mails from a certain sender
> with S/MIME signed messages, Emacs will freeze up for about 4 minutes.
> Opening the expandable signature inside of the Email repeats the lag.
Just to point you into the right direction, I'm pretty sure that this is
gpgsm reaching out to a network server, maybe to fetch certificate
revocation lists or something. I'm not too familiar with gpgsm.
Depending on your needs, there are several things to do.
If you don't need S/MIME at all, uninstall or chmod 0 gpgsm. That is
what I do :D
If you need S/MIME, consult man gpgsm, there are switches that turn off
certain things involving network services (e.g. disable-crl-checks), or
all network services (disable-dirmngr). Beware, this may change
semantics or weaken the S/MIME support.
Hope that helps,
Justus
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 519 bytes --]
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
next prev parent reply other threads:[~2022-01-24 13:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-24 3:58 Emacs lagging for ~4min when opening from certain email navse
2022-01-24 12:58 ` David Bremner
2022-01-24 13:16 ` David Bremner
2022-01-24 13:02 ` Justus Winter [this message]
2022-01-28 0:13 ` certificate revocation checking for signed e-mail [was: Re: Emacs lagging for ~4min when opening from certain email.] Daniel Kahn Gillmor
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://notmuchmail.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8735ldxp5i.fsf@europ.lan \
--to=justus@sequoia-pgp.org \
--cc=navse@mailbox.org \
--cc=notmuch@notmuchmail.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://yhetil.org/notmuch.git/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).