Gnus development mailing list
 help / color / mirror / Atom feed
From: Colin Marquardt <colin.marquardt@usa.alcatel.com>
Cc: ding@gnus.org
Subject: Re: Force Oort to verify sigs?
Date: 21 Mar 2001 18:10:55 -0800	[thread overview]
Message-ID: <ysd61yrqzh74.fsf@sol-cmarquar.pet.usa.alcatel.com> (raw)
In-Reply-To: <764rwm2274.fsf@newjersey.ppllc.com>

Jake Colman <colman@ppllc.com> writes:

> >>>>> "DP" == Daniel Pittman <daniel@rimspace.net> writes:
> 
>     DP> The easy way to deal with this, especially if you have 24/7 Internet,
>     DP> is to configure GPG to automatically fetch keys from one of the
>     DP> Internet PGP keyservers.
> 
> I have a permanent connection.  How do I go about doing this?

| `mm-verify-option' is a variable declared in Lisp.
|   -- loaded from "/home/sw/cmarquar/emacs/gnus/lisp/mm-decode.elc"
| 
| Value: known
| 
| Documentation:
| Option of verifying signed parts.
| `never', not verify; `always', always verify; 
| `known', only verify known protocols. Otherwise, ask user.


HTH,
  Colin


  reply	other threads:[~2001-03-22  2:10 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-03-17 16:44 Alan Shutko
2001-03-17 16:52 ` ShengHuo ZHU
2001-03-17 19:23   ` Shigeki Uno
2001-03-17 19:53     ` Shigeki Uno
2001-03-18  1:28     ` Daniel Pittman
2001-03-21 22:21       ` Jake Colman
2001-03-22  2:10         ` Colin Marquardt [this message]
2001-03-22  3:01         ` Daniel Pittman
2001-03-22 18:19           ` Jake Colman
2001-03-22 20:34             ` Paul Jarc
2001-03-22 21:47               ` Jake Colman
2001-03-22 22:47                 ` Paul Jarc
2001-03-23  1:39               ` Russ Allbery
2001-03-23 15:54                 ` Paul Jarc
2001-03-26 17:20                   ` Jake Colman
2001-03-26 17:56                     ` Josh Huber
2001-03-26 18:58                       ` Jake Colman
2001-03-18  2:07     ` Jack Twilley
2001-03-17 16:52 ` Karl Kleinpaste

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=ysd61yrqzh74.fsf@sol-cmarquar.pet.usa.alcatel.com \
    --to=colin.marquardt@usa.alcatel.com \
    --cc=ding@gnus.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.
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).