From: Lloyd Zusman <ljz@asfast.com>
Subject: Gnus not recognizing encrypted message
Date: Sun, 07 Dec 2003 16:44:59 -0500 [thread overview]
Message-ID: <m3brqkwbdw.fsf@asfast.com> (raw)
Normally, if someone sends me an encrypted message, Gnus recognizes the
fact when I try to read the message, and it prompts me, asking me if I
want to decrypt it. If so, I get prompted for my passphrase and if the
message was properly encrypted with my public key, I can then read it.
However, today I received an encrypted message, and Gnus didn't
recognize it as being something to decrypt.
The message arrived as a single-part multipart/mixed message, with both
the encrypted message and the user's public key that part.
If I copy that part to a separate file and run `pgg-decrypt' on it, I
get prompted for my passphrase, and it decrypts with no trouble. So I
know that the encryption block itself is OK.
Here's the structure of the information inside of that single part
of the multipart/mixed message:
-----BEGIN PGP MESSAGE-----
Version: MailVault 2.2 from MailVault Corporation http://www.mailvault.com
... base 64 stuff ...
-----END PGP MESSAGE-----
PGP Public Key for Sender <sender@sendingdomain.tld>:
-----BEGIN PGP PUBLIC KEY BLOCK-----
Version: MailVault 2.2 from MailVault Corporation http://www.mailvault.com
... more base 64 stuff ...
-----END PGP PUBLIC KEY BLOCK----
Could it be that Gnus doesn't recognize this block because it's within a
part of a multipart/mixed message? Or perhaps could the extra public
key block be confusing things?
Whatever the case, is there a way to set up Gnus so that it recognizes
the encrypted message within the message part and then runs me through
the standard decryption dialog?
Thanks in advance.
--
Lloyd Zusman
ljz@asfast.com
next reply other threads:[~2003-12-07 21:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-07 21:44 Lloyd Zusman [this message]
2003-12-07 23:57 ` Simon Josefsson
2003-12-08 13:32 ` Lloyd Zusman
2003-12-31 3:02 ` 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=m3brqkwbdw.fsf@asfast.com \
--to=ljz@asfast.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).