From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: "Stephen J. Turnbull" Newsgroups: gmane.emacs.devel Subject: Re: SMTP server error message Date: Sun, 01 Jun 2014 03:18:11 +0900 Message-ID: <87egz96cd8.fsf@uwakimon.sk.tsukuba.ac.jp> References: <83mwdydqcs.fsf@gnu.org> <87oaye57kk.fsf@uwakimon.sk.tsukuba.ac.jp> <83ha45ewx0.fsf@gnu.org> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 X-Trace: ger.gmane.org 1401560325 16768 80.91.229.3 (31 May 2014 18:18:45 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sat, 31 May 2014 18:18:45 +0000 (UTC) Cc: emacs-devel@gnu.org To: Eli Zaretskii Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sat May 31 20:18:37 2014 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1WqnrW-0008Vq-QG for ged-emacs-devel@m.gmane.org; Sat, 31 May 2014 20:18:34 +0200 Original-Received: from localhost ([::1]:60800 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WqnrV-0006a6-NM for ged-emacs-devel@m.gmane.org; Sat, 31 May 2014 14:18:33 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:54695) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WqnrN-0006Zn-GX for emacs-devel@gnu.org; Sat, 31 May 2014 14:18:30 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1WqnrI-0002fp-CB for emacs-devel@gnu.org; Sat, 31 May 2014 14:18:25 -0400 Original-Received: from mgmt2.sk.tsukuba.ac.jp ([130.158.97.224]:49406) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WqnrC-0002dd-Jl; Sat, 31 May 2014 14:18:14 -0400 Original-Received: from uwakimon.sk.tsukuba.ac.jp (uwakimon.sk.tsukuba.ac.jp [130.158.99.156]) by mgmt2.sk.tsukuba.ac.jp (Postfix) with ESMTP id 9447C970B29; Sun, 1 Jun 2014 03:18:11 +0900 (JST) Original-Received: by uwakimon.sk.tsukuba.ac.jp (Postfix, from userid 1000) id 865E711F235; Sun, 1 Jun 2014 03:18:11 +0900 (JST) In-Reply-To: <83ha45ewx0.fsf@gnu.org> X-Mailer: VM undefined under 21.5 (beta34) "kale" 2a0f42961ed4 XEmacs Lucid (x86_64-unknown-linux) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.6.x X-Received-From: 130.158.97.224 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:172228 Archived-At: Eli Zaretskii writes: > > From: "Stephen J. Turnbull" > > Cc: emacs-devel@gnu.org > > Date: Sat, 31 May 2014 23:47:07 +0900 > > > > Eli Zaretskii writes: > > > > > 451 4.0.0 Spam filter end message failed - server - license [slot 1] Oops, should have investigated more carefully instead of going by memory. Here's the RFC 5321 definition of status code 451: 451 Requested action aborted: local error in processing > It's not coming from the list, though. It comes from the SMTP server > my Emacs is talking to in order to send email. Sorry, I shouldn't have mentioned the MTA policy or emacs-devel. They're irrelevant since you're using smtpmail. > Are you saying that the SMTP server is trying to greylist me > personally? Why would it want to do that? Greylisting affects all incoming calls to the server, not just you. If it's just you, it's not greylisting. > [greylisting timing] doesn't seem to match what I see: > It's my ISP's SMTP server. OK, I just guessed entirely wrong. Very sorry! Between the definition of 451, and those two facts, we can rule out greylisting. 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. 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.