unofficial mirror of notmuch@notmuchmail.org
 help / color / mirror / code / Atom feed
* Sending mail succeeded but signaled failure
@ 2022-07-26 10:40 Justus Winter
  2022-07-26 14:07 ` David Bremner
  2022-07-26 17:18 ` Dan Čermák
  0 siblings, 2 replies; 8+ messages in thread
From: Justus Winter @ 2022-07-26 10:40 UTC (permalink / raw)
  To: notmuch

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

^ permalink raw reply	[flat|nested] 8+ messages in thread
* Sending mail succeeded but signaled failure
@ 2022-07-26 10:34 Justus Winter
  0 siblings, 0 replies; 8+ messages in thread
From: Justus Winter @ 2022-07-26 10:34 UTC (permalink / raw)
  To: notmuch

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

^ permalink raw reply	[flat|nested] 8+ messages in thread

end of thread, other threads:[~2022-08-01  9:22 UTC | newest]

Thread overview: 8+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
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
  -- strict thread matches above, loose matches on Subject: below --
2022-07-26 10:34 Justus Winter

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).