unofficial mirror of notmuch@notmuchmail.org
 help / color / mirror / code / Atom feed
From: Justus Winter <justus@sequoia-pgp.org>
To: notmuch@notmuchmail.org
Subject: Sending mail succeeded but signaled failure
Date: Tue, 26 Jul 2022 12:34:05 +0200	[thread overview]
Message-ID: <87sfmojh7m.fsf@thinkbox> (raw)

Hello,

I just embarrassed myself a little by sending the same mail over and
over again.  The reason for that is that notmuch-emacs signaled failure,
i.e. it displayed an error message in the status buffer and didn't close
the compose buffer, yet it did in fact send the mail.

I suspect that my configuration has to do with that and someone is
trying to be helpful.  So I use msmtp with the authentication password
encrypted using OpenPGP.  Then, I use 'gpg --no-tty -q -d ...' as
msmtp's passwordeval function.  Now, my OpenPGP key has expired, but
that doesn't stop GnuPG from decrypting the secret, and in fact it
returns the status code 0.  It also prints

  gpg: Note: secret key 08CC70F8D8CC765A expired at Mon 25 Jul 2022 05:31:26 PM CEST

to stderr, which is picked up by notmuch-emacs, it says

  sending...failed to gpg: Note: secret key 08CC70F8D8CC765A expired at Mon 25 Jul 2022 05:31:26 PM CEST

in the status buffer while the compose buffer stays open.

I suspect that this is not notmuch's fault, but I don't know where else
to turn to with this bug report.

Best,
Justus

             reply	other threads:[~2022-07-26 10:40 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-26 10:34 Justus Winter [this message]
  -- strict thread matches above, loose matches on Subject: below --
2022-07-26 10:40 Sending mail succeeded but signaled failure Justus Winter
2022-07-26 14:07 ` David Bremner
2022-07-30 21:06   ` Justus Winter
2022-08-01  8:17     ` Dan Čermák
2022-08-01  9:21       ` Justus Winter
2022-07-26 17:18 ` Dan Čermák
2022-07-30 14:53   ` Justus Winter

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

  List information: https://notmuchmail.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87sfmojh7m.fsf@thinkbox \
    --to=justus@sequoia-pgp.org \
    --cc=notmuch@notmuchmail.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.
Code repositories for project(s) associated with this public inbox

	https://yhetil.org/notmuch.git/

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 read-only IMAP folder(s) and NNTP newsgroup(s).