From: Justus Winter <justus@sequoia-pgp.org>
To: 56855@debbugs.gnu.org
Subject: bug#56855: 27.1; sendmail-send-it considers it an error if sendmail wrote to stdout/stderr
Date: Sun, 31 Jul 2022 15:08:28 +0200 [thread overview]
Message-ID: <87wnbtig4z.fsf@thinkbox> (raw)
sendmail-send-it considers it an error if sendmail wrote to
stdout/stderr, despite the fact that the process returned success.
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 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. Note that
despite this, the message has been sent successfully, while emacs
indicates that the sending has failed.
I wrote to the notmuch mailing list before investigating further, and at
least one other person hat a similar problem. The thread is here:
https://nmbug.notmuchmail.org/nmweb/show/87k080jgx8.fsf%40thinkbox
I dug into emacs, and discovered that indeed sendmail-send-it considers
any output from the sendmail process to be an indication of an error,
even if the process returned 0. I read documentation of various
sendmail implementations, and all agreed that returning success meant
that the operation succeeded. I found no justification for emacs
thinking that the operation failed if the process printed to stdout or
stderr.
Best,
Justus
next reply other threads:[~2022-07-31 13:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-31 13:08 Justus Winter [this message]
2022-08-01 20:46 ` bug#56855: 27.1; sendmail-send-it considers it an error if sendmail wrote to stdout/stderr Matt Armstrong
2022-08-02 5:59 ` Justus Winter
2022-08-02 10:44 ` Lars Ingebrigtsen
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://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87wnbtig4z.fsf@thinkbox \
--to=justus@sequoia-pgp.org \
--cc=56855@debbugs.gnu.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://git.savannah.gnu.org/cgit/emacs.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).