From: Rob French <fulcrum99@earthlink.net>
Subject: GPG signatures not working on quoted printable messages?
Date: Sat, 05 Apr 2003 21:14:13 GMT [thread overview]
Message-ID: <87r88gbq7y.fsf@earthlink.net> (raw)
Hello!
I recently converted over from kmail to gnus. I find that when I write a
message with gnus and sign it with gpg (via mailcrypt), I can check the
signature just fine. However, when I try to verify the signatures on
messages that I moved over from my kmail setup, I get a warning that no
signed message was found in the buffer. This is despite the fact that
down in the modeline there is the "p" for PGP message.
I tried looking for differences between the two e-mails. E-mails sent
with kmail all have a Content-Transfer-Encoding: quoted-printable.
Additionally, they have all the quoted-printable characters.
So for example, a message from kmail has =2D----BEGIN PGP etc, while a
message from gnus has -----BEGIN PGP etc. I don't know if that should
make a difference.
Interestingly, if I try to decrypt the message (never mind that it's not
encrypted) of course I get an error, and then gnus displays the raw
unformatted message. At that point, if I try to verify the signature, it
works.
Any thoughts? Thanks.
-Rob
reply other threads:[~2003-04-05 21:14 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=87r88gbq7y.fsf@earthlink.net \
--to=fulcrum99@earthlink.net \
/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).