From: Paul Stodghill <stodghil@CS.Cornell.EDU>
Subject: Re: PGP verifying NoCeM messages
Date: 15 Jan 1997 09:58:31 -0500 [thread overview]
Message-ID: <mlwwtfugrs.fsf@hoho.cs.cornell.edu> (raw)
In-Reply-To: "Lance A. Brown"'s message of Wed, 15 Jan 1997 09:14:23 -0500
>>>>> "Lance" == Lance A Brown <labrown@splat.niehs.nih.gov> writes:
Lance> My concern now is that there are a LOT of NoCeM messages waiting
Lance> to be processed in the morning and it often take 5+ minutes for
Lance> all the PGP verification to occur. This is on an R4000 100Mhz
Lance> SGI Indy. Is there a significant risk of NoCeM spoofing?
If you can leave yourself logged in overnight, I _strongly_ recommend using
the demon for doing stuff like this when your Emacs is idle.
Here's what I have in my .gnus:
(gnus-demon-add-nocem)
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;; Redefine some functions from gnus-demon.el
;; 1 min idle time isn't enough. Wait for 5 mins.
(defun gnus-demon-add-nocem ()
"Add daemonic NoCeM handling to Gnus."
(gnus-demon-add-handler 'gnus-demon-scan-nocem 60 5))
;; Don't try to fetch pgp keys when verifying in the demon.
;; Emacs is idle! There's noone to answer Mailcrypt's prompts!
(defun gnus-demon-scan-nocem ()
"Scan NoCeM groups for NoCeM messages."
(save-window-excursion
(let ((mc-pgp-always-fetch 'never))
(gnus-nocem-scan-groups))))
--
Paul Stodghill <stodghil@cs.cornell.edu>
http://www.cs.cornell.edu/home/stodghil/home.html
next prev parent reply other threads:[~1997-01-15 14:58 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-01-10 17:16 Lance A. Brown
1997-01-14 23:32 ` Lars Magne Ingebrigtsen
1997-01-15 4:25 ` Mark Eichin
1997-01-15 5:29 ` David Moore
1997-01-15 14:35 ` Alan Shutko
1997-01-15 14:48 ` Paul Stodghill
1997-01-15 14:14 ` Lance A. Brown
1997-01-15 14:58 ` Paul Stodghill [this message]
1997-01-15 15:55 ` Lance A. Brown
1997-01-16 23:05 ` Lars Magne Ingebrigtsen
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=mlwwtfugrs.fsf@hoho.cs.cornell.edu \
--to=stodghil@cs.cornell.edu \
/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.
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 NNTP newsgroup(s).