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:
[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:
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
-----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (Darwin)
iQCVAwUBRlw303EjvBPtnXfVAQJzkQP/aOE2ajjFTZMOV2WKJ0qyg3HWw/qNpSRb P4+E3pxe8XG+lbI9+rVO0vmDkMlr2llrKGao9URc5CNMKUKHZNw9ECxP+NOnKhDu auyQQYZc6axxq3Ny7YMcalB1fbhgpj2Rj6rycowb188JadQLaQNy4unjciBe+z6F fh3vwvpbPB4= =uJ5O -----END PGP SIGNATURE-----
--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.
-- Steve Burling <mailto:srb@umich.edu> University of Michigan, ICPSR Voice: +1 734 615.3779 330 Packard Street FAX: +1 734 647.8700 Ann Arbor, MI 48104-2910
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".
-- Brad Knowles <brad@shub-internet.org>, Consultant & Author LinkedIn Profile: <http://tinyurl.com/y8kpxu> Slides from Invited Talks: <http://tinyurl.com/tj6q4>
09 F9 11 02 9D 74 E3 5B D8 41 56 C5 63 56 88 C0
On 5/29/07, Leonard Jacobs wrote:
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 <brad@shub-internet.org>, Consultant & Author LinkedIn Profile: <http://tinyurl.com/y8kpxu> Slides from Invited Talks: <http://tinyurl.com/tj6q4>
09 F9 11 02 9D 74 E3 5B D8 41 56 C5 63 56 88 C0
Brad Knowles wrote:
Just a guess, but have you looked for AVC denials or other messages if you have SELinux enabled Leonard?
-- Todd OpenPGP -> KeyID: 0xBEAF0CE3 | URL: www.pobox.com/~tmz/pgp
A diplomat is a person who can tell you to go to Hell in such a way
that you actually look forward to the trip.
-- Anonymous
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On May 29, 2007, at 6:21 AM, Leonard Jacobs wrote:
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
-----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (Darwin)
iQCVAwUBRlw303EjvBPtnXfVAQJzkQP/aOE2ajjFTZMOV2WKJ0qyg3HWw/qNpSRb P4+E3pxe8XG+lbI9+rVO0vmDkMlr2llrKGao9URc5CNMKUKHZNw9ECxP+NOnKhDu auyQQYZc6axxq3Ny7YMcalB1fbhgpj2Rj6rycowb188JadQLaQNy4unjciBe+z6F fh3vwvpbPB4= =uJ5O -----END PGP SIGNATURE-----
--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.
-- Steve Burling <mailto:srb@umich.edu> University of Michigan, ICPSR Voice: +1 734 615.3779 330 Packard Street FAX: +1 734 647.8700 Ann Arbor, MI 48104-2910
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".
-- Brad Knowles <brad@shub-internet.org>, Consultant & Author LinkedIn Profile: <http://tinyurl.com/y8kpxu> Slides from Invited Talks: <http://tinyurl.com/tj6q4>
09 F9 11 02 9D 74 E3 5B D8 41 56 C5 63 56 88 C0
On 5/29/07, Leonard Jacobs wrote:
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 <brad@shub-internet.org>, Consultant & Author LinkedIn Profile: <http://tinyurl.com/y8kpxu> Slides from Invited Talks: <http://tinyurl.com/tj6q4>
09 F9 11 02 9D 74 E3 5B D8 41 56 C5 63 56 88 C0
Brad Knowles wrote:
Just a guess, but have you looked for AVC denials or other messages if you have SELinux enabled Leonard?
-- Todd OpenPGP -> KeyID: 0xBEAF0CE3 | URL: www.pobox.com/~tmz/pgp
A diplomat is a person who can tell you to go to Hell in such a way
that you actually look forward to the trip.
-- Anonymous
participants (5)
-
Barry Warsaw -
Brad Knowles -
Leonard Jacobs -
Steve Burling -
Todd Zullinger