unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: Justus Winter <justus@sequoia-pgp.org>
Cc: Matt Armstrong <matt@rfc20.org>, 56855@debbugs.gnu.org
Subject: bug#56855: 27.1; sendmail-send-it considers it an error if sendmail wrote to stdout/stderr
Date: Tue, 02 Aug 2022 12:44:08 +0200	[thread overview]
Message-ID: <87h72vylfr.fsf@gnus.org> (raw)
In-Reply-To: <875yjbi3th.fsf@thinkbox> (Justus Winter's message of "Tue, 02 Aug 2022 07:59:06 +0200")

Justus Winter <justus@sequoia-pgp.org> writes:

> In fact, I think we should ask what the best thing is for the user.  I
> think that (a) emacs should correctly indicate whether sending the mail
> succeeded or not, and (b) any warnings should be presented to the user.

Your argument makes sense, but there's a lot of systems out there, and
there's a lot of different things people use in place of
`sendmail-program'.  Emacs' contract with the user here has been (for 35
years) to consider any output from these programs as an error condition,
and changing that will inevitably lead to people losing mail, because
they're using that contract.

As a practical matter, accepting a SUCCESS exit code as a success, but
then showing the extra text isn't much friendlier than signalling an
error -- users don't want to see warnings every time they send a mail,
so they'll have to fix whatever program they're using for
`sendmail-program'.

So I think the fix here is to just document that output is considered
failure, and I've now done this in Emacs 29, and is therefore closing
this bug report.






      reply	other threads:[~2022-08-02 10:44 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-31 13:08 bug#56855: 27.1; sendmail-send-it considers it an error if sendmail wrote to stdout/stderr Justus Winter
2022-08-01 20:46 ` Matt Armstrong
2022-08-02  5:59   ` Justus Winter
2022-08-02 10:44     ` Lars Ingebrigtsen [this message]

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=87h72vylfr.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=56855@debbugs.gnu.org \
    --cc=justus@sequoia-pgp.org \
    --cc=matt@rfc20.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).