From: Eli Zaretskii <eliz@gnu.org>
To: "Stephen J. Turnbull" <stephen@xemacs.org>
Cc: emacs-devel@gnu.org
Subject: Re: SMTP server error message
Date: Sat, 31 May 2014 21:43:51 +0300 [thread overview]
Message-ID: <83zjhxbxg8.fsf@gnu.org> (raw)
In-Reply-To: <87egz96cd8.fsf@uwakimon.sk.tsukuba.ac.jp>
> From: "Stephen J. Turnbull" <stephen@xemacs.org>
> Cc: emacs-devel@gnu.org
> Date: Sun, 01 Jun 2014 03:18:11 +0900
>
> 451 means an intermittent problem at your ISP. The "one broken node
> in the cluster" hypothesis sounds plausible to me, but in any case
> since the server is at your ISP, they should fix their server. It's
> not smtpmail, since the transaction is completing with a proper
> response code, it's the server.
OK, I guess I'll collect the names of the servers that return this
error, and if they are the same every time, will send a note to
postmaster.
> To save you (and maybe others) some grief, smtpmail could retry on any
> status code matching "4[0-9][0-9]", that's what an SMTP client is
> supposed to do. Probably in most cases waiting a few seconds and
> trying once should be enough when you're talking only to your ISP.
I will try that as well. Are all 4XX codes indeed of this nature?
next prev parent reply other threads:[~2014-05-31 18:43 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-31 13:34 SMTP server error message Eli Zaretskii
2014-05-31 14:16 ` Achim Gratz
2014-05-31 15:51 ` Stefan Monnier
2014-05-31 16:59 ` Achim Gratz
2014-05-31 16:28 ` Eli Zaretskii
2014-05-31 17:02 ` Achim Gratz
2014-05-31 14:27 ` Florian Weimer
2014-05-31 16:29 ` Eli Zaretskii
2014-05-31 14:47 ` Stephen J. Turnbull
2014-05-31 16:27 ` Eli Zaretskii
2014-05-31 18:18 ` Stephen J. Turnbull
2014-05-31 18:43 ` Eli Zaretskii [this message]
2014-05-31 19:55 ` Stephen J. Turnbull
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=83zjhxbxg8.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=stephen@xemacs.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).