Re: [Mailman-Users] Low level smtp error: Server not connected
Thanks for your suggestion to read the FAQ and the associated list postings. I actually found those same postings and tried every suggestion in them that was relevant. Unfortunately nothing worked to resolve this annoying problem. There may be a setting that is incorrect and there may be something posted that explains this problem and provides a solution but so far I have not located anything that fixes it for me.
It is strange that a pretty vanilla installation, CentOS and Postfix with the latest Mailman version of 2.1.9 is so hard to configure and use. And this after using it on a CentOS 3 box but with frequent delays in sending and unusal errors. So moving the list was necessary but made the list totally unusable. I have heard from a few others with similar problems and no solution, so I know I am not the only user with these issues.
Any further suggestions would be appreciated.
mailman-users-request@python.org wrote:
Send Mailman-Users mailing list submissions to mailman-users@python.org
To subscribe or unsubscribe via the World Wide Web, visit http://mail.python.org/mailman/listinfo/mailman-users or, via email, send a message with subject or body 'help' to mailman-users-request@python.org
You can reach the person managing the list at mailman-users-owner@python.org
When replying, please edit your Subject line so it is more specific than "Re: Contents of Mailman-Users digest..."
Today's Topics:
- Re: Low level smtp error: Server not Connected (Leonard Jacobs)
- Re: Low level smtp error: Server not Connected (Brad Knowles)
Subject: Re: [Mailman-Users] Low level smtp error: Server not Connected From: Leonard Jacobs ljacobs@shambhala.com Date: Mon, 28 May 2007 10:06:37 -0400 To: mailman-users@python.org
To: mailman-users@python.org
Content-Transfer-Encoding: 7bit Precedence: list MIME-Version: 1.0 Message-ID: 465AE1ED.5020508@shambhala.com Content-Type: text/plain; charset=ISO-8859-1; format=flowed Message: 1
Today's Topics:
- Low level smtp error: Server not connected (Stephen J. Turnbull)
Subject: [Mailman-Users] Low level smtp error: Server not connected From: "Stephen J. Turnbull" stephen@xemacs.org Date: Sun, 27 May 2007 20:30:19 +0900 To: ljacobs@shambhala.com
To: ljacobs@shambhala.com CC: mailman-users@python.org
Precedence: list MIME-Version: 1.0 References: 7c5b3fd245874985b5fa1fa9049a7b2c@shambhala.com In-Reply-To: 7c5b3fd245874985b5fa1fa9049a7b2c@shambhala.com Message-ID: 871wh24i7o.fsf@uwakimon.sk.tsukuba.ac.jp Content-Type: text/plain; charset=us-ascii Message: 1
Leonard Jacobs writes:
"delivery to someone@gmail.com failed with code -1: (104, 'Connection reset by peer')" I am also seeing many " Low level smtp error: Server not connected, msgid" errors.
This seems likely to be either a Postfix problem, or maybe you've caught a social disease (ie, a bunch of big ISPs have decided you're a spammer). Either way, the first place to investigate is the Postfix logs.
Wish it were so simple. There are no obvious errors in the postfix maillog files. In fact postfix is receiving and sending messages fine, just no mailman messages are getting delivered except for the response to the list creator that the list was created and notifications to the list posters that there is a message waiting to be reviewed. Once the moderated poster's message is released from the queue, it triggers the "server not connected" errors and never actually delivers any messages.
Strange behavior and I would appreciate any other insights and suggestions.
[This E-mail scanned for viruses by Declude EVA]
Subject: Re: [Mailman-Users] Low level smtp error: Server not Connected From: Brad Knowles brad@shub-internet.org Date: Mon, 28 May 2007 17:57:41 -0500 To: Leonard Jacobs ljacobs@shambhala.com, mailman-users@python.org
To: Leonard Jacobs ljacobs@shambhala.com, mailman-users@python.org
Precedence: list MIME-Version: 1.0 References: 465AE1ED.5020508@shambhala.com In-Reply-To: 465AE1ED.5020508@shambhala.com Message-ID: <p06240800c2810d24bbae@[192.168.1.66]> Content-Type: text/plain; charset="us-ascii" ; format="flowed" Message: 2
On 5/28/07, Leonard Jacobs wrote:
Wish it were so simple. There are no obvious errors in the postfix maillog files. In fact postfix is receiving and sending messages fine, just no mailman messages are getting delivered except for the response to the list creator that the list was created and notifications to the list posters that there is a message waiting to be reviewed. Once the moderated poster's message is released from the queue, it triggers the "server not connected" errors and never actually delivers any messages.
Searching through the archives of the mailman-users list (in accordance with FAQ 1.18) turns up a number of hits. I did http://www.google.com/search?q=%22Server+not+connected%22+inurl:mail.python.org/pipermail/mailman-users/, but there are other searches that could also have been done.
In the article at http://mail.python.org/pipermail/mailman-users/2005-August/046366.html, the problem was an inappropriate setting for SMTPPORT that needed to be fixed in the mm_cfg.py file.
Then there's the article at http://mail.python.org/pipermail/mailman-users/2005-September/046418.html, where Mark Sapiro points out essentially the same search, and other issues that other people needed to resolve, in particular "setting SMTP_MAX_SESSIONS_PER_CONNECTION to 1 and/or setting SMTP_MAX_RCPTS to some small number."
Then there's the article at http://mail.python.org/pipermail/mailman-users/2004-July/038047.html, and more than sixty others.
Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
[This E-mail scanned for viruses by Declude EVA]
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On May 29, 2007, at 6:21 AM, Leonard Jacobs wrote:
Thanks for your suggestion to read the FAQ and the associated list postings. I actually found those same postings and tried every suggestion in them that was relevant. Unfortunately nothing worked to resolve this annoying problem. There may be a setting that is
incorrect and there may be something posted that explains this problem and provides a solution but so far I have not located anything that
fixes it for me.It is strange that a pretty vanilla installation, CentOS and Postfix with the latest Mailman version of 2.1.9 is so hard to configure and use. And this after using it on a CentOS 3 box but with frequent
delays in sending and unusal errors. So moving the list was necessary but
made the list totally unusable. I have heard from a few others with similar problems and no solution, so I know I am not the only user with these issues.Any further suggestions would be appreciated.
I don't have any idea what's going on, but here are some mostly
useless comments.
I'm personally still on Postfix 2.3.6, and you mentioned that you're
on Postfix 2.4.1. I wonder if there isn't some new feature, anti-
spam defense, or other setting that is tripping up Mailman. It's
also possible that Postfix 2.4.1 has some bug that's causing it to
reset the connection. I don't have time to slog through the Postfix
change logs, but I suggest you take a look to see if there's anything
relevant.
You might also try the Postfix 2.4.2 release candidate, and/or
grabbing Postfix 2.3.9 to see if that improves things. IME, Postfix
is pretty easy to build and install from source.
If I were debugging this, my next step would probably be to write
some sample Python applications that stress tested SMTP connections
from a Python program. Mailman uses Python's standard smtplib
module, so that's where I'd start. See if you can reproduce the
problem outside of Mailman.
I agree with previous posters that this is almost certainly a problem
with your Postfix installation. Mailman + Postfix has been a long-
term very stable combination, although as I said, it's possible
there's something in Postfix 2.4 that's tripping us up now.
Does anybody else use Postfix 2.4?
- -Barry
--On May 29, 2007 10:25:22 AM -0400 Barry Warsaw barry@python.org wrote:
Does anybody else use Postfix 2.4?
To which I reply:
For what it's worth, my (extremely small, low-traffic) home Mailman install (2.1.9) uses Postfix 2.4.1 with no problems.
On 5/29/07, Barry Warsaw wrote:
Does anybody else use Postfix 2.4?
Actually, I'm pretty sure we are currently using it on the NTP Public Services Project pages at ntp.isc.org, which is the project I had gotten involved in years ago, prior to getting involved in Mailman. I got on this mailing list in order to help me figure out if it would be a good idea to switch from Majordomo to Mailman, and I haven't looked back since.
Currently, these are the two primary open source projects where I spend most of my time.
If you want to give it a test, I could install the latest postfix 2.5 experimental or non-production patch releases on the python.org mail servers, so that we can give the newer code a try. ;)
Seriously, I am quite convinced that the problem here is a mis-configuration between Mailman and postfix, and that neither program is necessarily "at fault".
On 5/29/07, Leonard Jacobs wrote:
It is strange that a pretty vanilla installation, CentOS and Postfix with the latest Mailman version of 2.1.9 is so hard to configure and use.
Can you share with us the relevant portions of your mm_cfg.py file, and your postfix/main.cf file?
Also, you did stop and restart Mailman after making these changes, right? Have you tried stopping and restarting it again?
Brad Knowles wrote:
On 5/29/07, Leonard Jacobs wrote:
It is strange that a pretty vanilla installation, CentOS and Postfix with the latest Mailman version of 2.1.9 is so hard to configure and use.
Can you share with us the relevant portions of your mm_cfg.py file, and your postfix/main.cf file?
Also, you did stop and restart Mailman after making these changes, right? Have you tried stopping and restarting it again?
Just a guess, but have you looked for AVC denials or other messages if you have SELinux enabled Leonard?
participants (5)
-
Barry Warsaw -
Brad Knowles -
Leonard Jacobs -
Steve Burling -
Todd Zullinger