From: Lars Magne Ingebrigtsen <larsi@gnus.org>
To: Stefan Monnier <monnier@IRO.UMontreal.CA>
Cc: rms@gnu.org, emacs-devel@gnu.org
Subject: Re: `send-mail-function' default change
Date: Thu, 07 Jul 2011 22:56:11 +0200 [thread overview]
Message-ID: <m3sjqhn72s.fsf@quimbies.gnus.org> (raw)
In-Reply-To: <jwvfwmh4yup.fsf-monnier+emacs@gnu.org> (Stefan Monnier's message of "Thu, 07 Jul 2011 16:31:34 -0400")
Stefan Monnier <monnier@IRO.UMontreal.CA> writes:
> This can't be done, because there's no reliable way to check whether
> sendmail does work.
One thing that I don't think has been discussed in this area (yay!
another sub-thread in an unending thread) is the issue of failing early
versus retrying.
Here's the issue:
You're using a laptop at home, and you've got exim configured to (for
instance) send mail directly (because your ISP does not block port 25),
and things work fine.
Then you bring the laptop with you while going on holiday. You read
your email, as usual, from imap.example.com, and you're replying as
usual. But the hotel you're at is blocking port 25.
exim will then queue up the messages, and after a certain time period,
it'll send you a (local) message saying that it couldn't send the
emails. (If I recall correctly, the default is one day.) It will retry
sending for four days, so if you go home before that time, it will send
all the messages when you get home.
Now, you won't see any error messages in this period. You most likely
aren't reading the local /var/mail/spool/. So if this is something
you're not familiar with, you'll wonder where the emails went. If you
are familiar with this situation, you'll figure it out after a while,
reconfigure, and flush the queue.
If Emacs talks SMTP directly, you will get an error message immediately
at the hotel, and can choose to reconf, or you can choose to queue the
mail in Emacs.
Now, some people will prefer different behaviours. Some people probably
use the let-exim-queue-locally-until-I-get-home behaviour, and find that
it suits their needs.
But I have a suspicion that most people would like to get an error
message as early as possible.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog http://lars.ingebrigtsen.no/
next prev parent reply other threads:[~2011-07-07 20:56 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-06 15:38 `send-mail-function' default change Lars Magne Ingebrigtsen
2011-07-06 17:26 ` Eli Zaretskii
2011-07-06 17:36 ` Lars Magne Ingebrigtsen
2011-07-06 17:56 ` Eli Zaretskii
2011-07-06 20:13 ` Stefan Monnier
2011-07-07 11:19 ` Lars Magne Ingebrigtsen
2011-07-07 0:33 ` Richard Stallman
2011-07-07 20:31 ` Stefan Monnier
2011-07-07 20:56 ` Lars Magne Ingebrigtsen [this message]
2011-07-07 21:24 ` Stefan Monnier
2011-07-09 3:26 ` Tim Cross
2011-07-10 5:01 ` Tim Cross
2011-07-08 0:07 ` Richard Stallman
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=m3sjqhn72s.fsf@quimbies.gnus.org \
--to=larsi@gnus.org \
--cc=emacs-devel@gnu.org \
--cc=monnier@IRO.UMontreal.CA \
--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).