From: Greg Troxel <gdt@work.lexort.com>
To: ding@gnus.org
Subject: "Sign failed" but mail sent
Date: Wed, 02 Mar 2011 11:29:42 -0500 [thread overview]
Message-ID: <smutyflpjt5.fsf@linuxpal.mit.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 698 bytes --]
I am using no gnus master on emacs23, with up to date gnupg1 and
gpg-agent, on NetBSD/i386 5.1ish. I sign messages via:
LT HASH secure method=pgpmime mode=sign RT
Usually all is well, but sometimes when I send a message I get "Sign
failed" and am left in the message buffer. I then hit ^C^C again, don't
get warned about "already sent, resend?" and sending happens normally.
However, two signed copies of the mail go out.
So it seems like there is incorrect reading of status (or incorrect
status), but also that the marking of the buffer that the mail is sent
is more disconnected from sending than I would expect.
I'll look into this, but I wonder if anyone else is having this problem?
[-- Attachment #2: Type: application/pgp-signature, Size: 194 bytes --]
next reply other threads:[~2011-03-02 16:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-02 16:29 Greg Troxel [this message]
2011-03-05 10:40 ` Lars Magne Ingebrigtsen
2011-03-05 11:09 ` Julien Danjou
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=smutyflpjt5.fsf@linuxpal.mit.edu \
--to=gdt@work.lexort.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).