From: Graham Murray <graham@gmurray.org.uk>
Subject: Re: PGG and ding list
Date: Tue, 13 May 2003 06:54:04 +0100 [thread overview]
Message-ID: <m38ytbxugz.fsf@home.gmurray.org.uk> (raw)
In-Reply-To: <plop87el331yns.fsf@gnu-rox.org> (Xavier Maillard's message of "Tue, 13 May 2003 02:24:39 +0200")
[-- Attachment #1: Type: text/plain, Size: 493 bytes --]
Xavier Maillard <zedek@gnu-rox.org> writes:
> Whenever I sign a message to the ding list and then read, it shows me
> it failed verifying the sign. What it is really weird is that it *ONLY*
> happens in this group but I can easily verify any "self" signed message
> in other groups.
This has been discussed before and is related to the way that the
mailing list software encodes the '---' lines into QP.
I believe that the answer is to sign using PGP/MIME rather than
inline.
[-- Attachment #2: Type: application/pgp-signature, Size: 188 bytes --]
next prev parent reply other threads:[~2003-05-13 5:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-13 0:24 Xavier Maillard
2003-05-13 1:26 ` Jorge Godoy
2003-05-13 1:40 ` Jorge Godoy
2003-05-13 11:53 ` Xavier Maillard
2003-05-13 5:54 ` Graham Murray [this message]
2003-05-13 11:54 ` Xavier Maillard
2003-05-13 16:34 ` Zack Weinberg
2003-05-13 16:43 ` Xavier Maillard
2003-05-13 17:02 ` Zack Weinberg
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=m38ytbxugz.fsf@home.gmurray.org.uk \
--to=graham@gmurray.org.uk \
/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).