From: Kevin Falcone <kevinfal@seas.upenn.edu>
Subject: gpgp verification fails without gpg.el
Date: 03 Dec 2000 17:55:55 -0500 [thread overview]
Message-ID: <m3zoidm7wk.fsf@bowline.jibsheet.com> (raw)
I have gpg signing/verification etc set up to use mailcrypt, and it
was working fine with gnus for both plain text and pgp/mime
verifications, but it has started failing for plain-text signings in
the last few days.
When I click on the button, I get
[[PGP Signed Part:Failed]
Autoloading failed to define function gpg-verify-cleartext]
M-x load-library ~/cvs/gnus/contrib/gpg
makes everything happy
[[PGP Signed Part:OK]
gpg: armor header: Hash: SHA1
gpg: armor header: Version: PGPfreeware 5.0i for non-commercial use
gpg: armor header: Comment: Processed by Mailcrypt 3.5.5, an Emacs/PGP interface
gpg: armor header: Charset: noconv
gpg: original file name=''
gpg: Signature made Sun Jul 16 21:48:47 2000 EDT using DSA key ID 4E31A819
gpg: Good signature from "Robert Spier <rspier@seas.upenn.edu>"
So, do I need to use gpg.el instead of mailcrypt now?
-kevin
--
Usenet is no longer a quiet place of valued information. You prospect
and sometimes you get lucky. It's not a classroom and you cannot save
lemmings in search of an ocean. --Elaine Ashton
next reply other threads:[~2000-12-03 22:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-03 22:55 Kevin Falcone [this message]
2000-12-03 23:10 ` Simon Josefsson
2000-12-03 23:23 ` Kevin Falcone
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=m3zoidm7wk.fsf@bowline.jibsheet.com \
--to=kevinfal@seas.upenn.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).