unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Jan D." <jan.h.d@swipnet.se>
Cc: Simon Josefsson <jas@extundo.com>, rms@gnu.org, emacs-devel@gnu.org
Subject: Re: sendmail.el bug or expected behavior?
Date: Mon, 26 Jan 2004 14:28:29 +0100	[thread overview]
Message-ID: <876E93D9-5003-11D8-BC55-00039363E640@swipnet.se> (raw)
In-Reply-To: <16404.63472.223534.499091@chiark.greenend.org.uk>

> Jan D. writes ("Re: sendmail.el bug or expected behavior?"):
>> This may not do the right thing.  It is not uncommon to not run any
>> sendmail daemon, but just forward everything to another host.  If we
>> do it like this, the mail will never be delivered, but sit in the
>> queue forever.
>
> There is no reliable way for Emacs to prevent /usr/lib/sendmail from
> choosing to sit on the mail, if that's what it's configured by the
> sysadmin to do.  Consider an installation whose mail hub is
> temporarily down.

The point is if this is changed, there will be places where Emacs
previously did deliver mail, and now no longer does.  It is an
incompatible change, not to be made lightly IMHO.

	Jan D.

  reply	other threads:[~2004-01-26 13:28 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-20  6:14 sendmail.el bug or expected behavior? Rob Browning
2004-01-20 11:53 ` Simon Josefsson
2004-01-21  9:21 ` Richard Stallman
2004-01-21 18:28   ` Kevin Rodgers
2004-01-21 22:33   ` Simon Josefsson
2004-01-22 19:00     ` Richard Stallman
2004-01-22 19:09       ` Simon Josefsson
2004-01-23 12:29         ` Ian Jackson
2004-01-23 15:13           ` Jan D.
2004-01-26 11:20             ` Ian Jackson
2004-01-26 13:28               ` Jan D. [this message]
2004-01-26 13:40                 ` Ian Jackson
2004-01-26 13:50                   ` Jan D.
2004-01-26 14:10                     ` Ian Jackson
2004-01-26 14:25                       ` Jan D.
2004-01-26 14:29                         ` Ian Jackson
2004-01-26 14:35                           ` Jan D.
2004-01-26 14:42                             ` Ian Jackson
2004-01-27 18:49                   ` Richard Stallman
2004-01-27 21:03                     ` Stefan Monnier
2004-01-29 17:52                       ` Richard Stallman
2004-01-25 14:46           ` Richard Stallman
2004-01-23 18:25         ` Richard Stallman
2004-01-23 18:33           ` Eli Zaretskii
2004-01-23 18:38           ` Simon Josefsson
2004-01-26 14:09             ` Ian Jackson
2004-01-26 16:21               ` Simon Josefsson
2004-01-26 18:22                 ` Stefan Monnier
2004-01-26 19:26                   ` Simon Josefsson
2004-01-26 20:47                     ` Stefan Monnier
2004-01-27 18:50                 ` Richard Stallman
2004-01-30  4:27 ` Rob Browning
2004-01-30 14:45   ` Stefan Monnier
2004-01-30 14:46   ` Stefan Monnier
2004-01-30 14:46     ` David Kastrup
2004-01-30 16:14       ` Stefan Monnier
2004-01-31  7:51   ` Richard Stallman
2004-01-31 17:26     ` Rob Browning

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=876E93D9-5003-11D8-BC55-00039363E640@swipnet.se \
    --to=jan.h.d@swipnet.se \
    --cc=emacs-devel@gnu.org \
    --cc=jas@extundo.com \
    --cc=rms@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).