Gnus development mailing list
 help / color / mirror / Atom feed
From: Daiki Ueno <ueno@unixuser.org>
To: Ashish SHUKLA <wahjava@members.fsf.org>
Cc: ding@gnus.org, bugs@gnus.org
Subject: Re: Issues sending GPG-signed mails.
Date: Sun, 19 Jul 2009 21:29:00 +0900	[thread overview]
Message-ID: <87hbx8yhyr.fsf@broken.deisui.org> (raw)
In-Reply-To: <87tz1aqp1p.fsf@marauder.physik.uni-ulm.de> (Reiner Steib's message of "Sat, 18 Jul 2009 12:10:58 +0200")

>> Gnus v5.13
>> GNU Emacs 23.1.50.1 (x86_64-unknown-linux-gnu, GTK+ Version 2.16.2)

>> I get this error sometimes, whenever I try to send any GPG-signed mail.
>>
>> Debugger entered--Lisp error: (error "Sign failed")
>>   signal(error ("Sign failed"))

>> I've masked the mail message and binary byte code in above
>> stacktrace. As soon as I press C-c C-c, I'm prompted for my GPG key's
>> password and then mail gets sent, and I get this error. If I press C-c
>> C-c again in that mail buffer I get this message 'mail already sent.'.
>>
>> I originally noticed this issue in Emacs 23.0.50.x but before I'm able
>> to report in later versions it went away. And now since few days, it
>> started to show up again.

I remember I addressed this issue before:

http://emacsbugs.donarmstrong.com/cgi-bin/bugreport.cgi?bug=2412

Can you provide debugging information with epg-debug?

Regards,
-- 
Daiki Ueno



  reply	other threads:[~2009-07-19 12:29 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <87vdltc7ut.fsf@chateau.d.lf>
2009-07-18 10:10 ` Reiner Steib
2009-07-19 12:29   ` Daiki Ueno [this message]
2009-07-19 15:00     ` Ashish SHUKLA
2009-07-19 16:03       ` Greg Troxel
2009-07-21 10:56         ` Daiki Ueno
2009-07-28  2:15           ` Ashish SHUKLA
2009-07-29  8:36             ` Daiki Ueno
2009-07-29 11:19               ` Ashish SHUKLA
2009-07-29 13:31                 ` Daiki Ueno

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=87hbx8yhyr.fsf@broken.deisui.org \
    --to=ueno@unixuser.org \
    --cc=bugs@gnus.org \
    --cc=ding@gnus.org \
    --cc=wahjava@members.fsf.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).