From: deskpot@despammed.com (Vasily Korytov)
Subject: Re: Problems with PGG
Date: Tue, 01 Apr 2003 02:46:21 +0400 [thread overview]
Message-ID: <877kaf9mte.fsf@unix.home> (raw)
In-Reply-To: <plop8765pzci89.fsf@gnu-rox.org>
[-- Attachment #1: Type: text/plain, Size: 661 bytes --]
On 1 Apr 2003, Xavier Maillard wrote:
First, Xavier, your Reply-To header sucks. =((
> I using PGG for 1 month now and it seems that all signed/encrypted
> messages whose keys are not in my keyring are never checked/verified
> before being displaid to me. I don't think it is the normal
> behaviour. So I am asking why Gnus always fails silently when verifying
> messages and want to know how to correct this.
RTFM: it's not a Gnus problem, it's the default behavoiur of GnuPG now
(since 1.2, I guess).
--
I accept RFC3156 and RFC2440-compatible encrypted mail.
PGP key fingerprint: 123A 7CCE 6E26 6233 0D87 E01A A0F8 3524 FCD8 1841
[-- Attachment #2: Type: application/pgp-signature, Size: 188 bytes --]
next prev parent reply other threads:[~2003-03-31 22:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-31 21:57 Xavier Maillard
2003-03-31 22:46 ` Vasily Korytov [this message]
2003-03-31 23:16 ` Xavier Maillard
2003-03-31 23:29 ` Xavier Maillard
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=877kaf9mte.fsf@unix.home \
--to=deskpot@despammed.com \
/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).