From: Simon Josefsson <jas@extundo.com>
Cc: ding@gnus.org
Subject: Re: mailcrypt/PGG woes
Date: Thu, 24 Apr 2003 15:28:11 +0200 [thread overview]
Message-ID: <iluhe8oowic.fsf@latte.josefsson.org> (raw)
In-Reply-To: <m3wuhl3y1t.fsf@merlin.emma.line.org> (Matthias Andree's message of "Wed, 23 Apr 2003 19:48:14 +0200")
Matthias Andree <ma@dt.e-technik.uni-dortmund.de> writes:
> Hi,
>
> I'm using Gnus from CVS (freshly pulled, built and installed) with GNU
> emacs 21.3.1. I have some issues with traditional GPG signatures in some
> groups, say, gmane.network.leafnode.announce on news.gmane.org (NNTP
> access). The articles are traditional gpg --clearsign format.
>
> When I choose any article of mine and type C-c / v (Mailcrypt
> verify), I'm getting "bad signature, doesn't match file contents."
This sounds like a mailcrypt problem, not PGG.
> pgg-verify brabbles something about NODATA and seems not to find the
> signature, but marking just the signed part and then doing
> "pgg-verify-region" tells me the signature is intact.
How did you invoke pgg-verify? The recommended way is to invoke it
via Gnus with, e.g., `W s'. What happens if you do this? (Make sure
you haven't changed mml1991-use from its default value.)
next prev parent reply other threads:[~2003-04-24 13:28 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-23 17:48 Matthias Andree
2003-04-23 21:55 ` Reiner Steib
2003-04-25 10:02 ` Matthias Andree
2003-04-24 13:28 ` Simon Josefsson [this message]
2003-04-25 9:47 ` Matthias Andree
2003-04-25 11:36 ` Simon Josefsson
2003-04-27 10:46 ` Matthias Andree
2003-04-27 11:04 ` Matthias Andree
2003-04-27 11:11 ` Matthias Andree
2003-04-27 16:32 ` Simon Josefsson
-- strict thread matches above, loose matches on Subject: below --
2003-04-23 17:48 Matthias Andree
2003-04-25 9:48 ` Matthias Andree
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=iluhe8oowic.fsf@latte.josefsson.org \
--to=jas@extundo.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).