[Mailman-Users] Low level smtp error: Server not connected

Mon Jun 4 07:21:33 CEST 2007

>
> ubject:
> Re: [Mailman-Users] Low level smtp error: Server not connected
> From:
> Leonard Jacobs <ljacobs at shambhala.com>
> Date:
> Mon, 04 Jun 2007 00:31:01 -0400
> To:
> mailman-users at python.org
>
> To:
> mailman-users at python.org
>
> Content-Transfer-Encoding:
> 7bit
> Precedence:
> list
> MIME-Version:
> 1.0
> References:
> <mailman.28142.1180752435.32030.mailman-users at python.org>
> In-Reply-To:
> <mailman.28142.1180752435.32030.mailman-users at python.org>
> Message-ID:
> <46639585.6060800 at shambhala.com>
> Content-Type:
> text/plain; charset=ISO-8859-1; format=flowed
> Message:
> 5
>
>
>>
>> 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 at shub-internet.org 
>> <http://mail.python.org/mailman/listinfo/mailman-users>>, Consultant 
>> & Author
>> LinkedIn Profile: <http://tinyurl.com/y8kpxu>
>> Slides from Invited Talks: <http://tinyurl.com/tj6q4>
>
>
> Still having problems with Maioman via Postfix 2.4, so I just upgraded 
> to the stable patch 2.4.3. My edited mm_cfg.py file:
> MTA = 'Postfix'
> DEFAULT_URL_HOST = 'lists.shambhala.com'
> DEFAULT_EMAIL_HOST = 'lists.shambhala.com'
> add_virtualhost(DEFAULT_URL_HOST, DEFAULT_EMAIL_HOST)
> OWNERS_CAN_ENABLE_PERSONALIZATION = 1
> SMTPPORT = 25
> SMTPHOST = '192.168.1.130'
>
> [user]# ifconfig | grep 130
>          inet addr:192.168.1.130  Bcast:192.168.1.255  Mask:255.255.255.0
>
> [user]# postconf | grep version
> mail_version = 2.4.3
>
> Yes, I have stopped & restarted Mailman after each mm_cfg.py change 
> and no, there are no anti-virus or other rejections with postfix. 
> Additionally I am not running SELinux on this box.
>
> After my recent Postfix upgrade to 2.4.3, my logs/smtp-failure contains:
> Jun 03 23:54:13 2007 (29345) Low level smtp error: (4, 'Interrupted 
> system call'), msgid: <46591BE4.3030308 at shambhala.com>
> Jun 03 23:54:19 2007 (29345) Low level smtp error: (4, 'Interrupted 
> system call'), msgid: <46591BE4.3030308 at shambhala.com>
> Jun 03 23:54:20 2007 (29345) Low level smtp error: (4, 'Interrupted 
> system call'), msgid: <46591BE4.3030308 at shambhala.com>
> Jun 03 23:54:21 2007 (29345) Low level smtp error: (4, 'Interrupted 
> system call'), msgid: <46591BE4.3030308 at shambhala.com>
>
> Now one clue that might be relevant is that when creating test lists 
> and testing sending messages to beta users of these lists, all works 
> fine. But as soon as the list contains the actual number of users, in 
> one case 5,100 members, in another 350 members, the mailings to the 
> subscribers fail with the error as listed above. And there is no 
> obvious throttling on the Postfix MTA.
>
> Think I should try downgrading to an earlier version of Postfix? It 
> does seem like a recent upgrade of Postfix may have broken the 
> connection that once did exist. Any other thoughts or suggestions 
> would be appreciated.
>
> Thanks.
>
> ---
> [This E-mail scanned for viruses by Declude EVA]
>
>
>
>
> ------------------------------------------------------------------------
>
> Subject:
> Re: [Mailman-Users] Low level smtp error: Server not connected
> From:
> Brad Knowles <brad at shub-internet.org>
> Date:
> Sun, 3 Jun 2007 23:55:46 -0500
> To:
> Leonard Jacobs <ljacobs at shambhala.com>, mailman-users at python.org
>
> To:
> Leonard Jacobs <ljacobs at shambhala.com>, mailman-users at python.org
>
> Precedence:
> list
> MIME-Version:
> 1.0
> References:
> <mailman.28142.1180752435.32030.mailman-users at python.org> 
> <46639585.6060800 at shambhala.com>
> In-Reply-To:
> <46639585.6060800 at shambhala.com>
> Message-ID:
> <p06240803c289499ad787@[192.168.1.66]>
> Content-Type:
> text/plain; charset="us-ascii" ; format="flowed"
> Message:
> 6
>
>
> On 6/4/07, Leonard Jacobs wrote:
>
>>  Yes, I have stopped & restarted Mailman after each mm_cfg.py change and
>>  no, there are no anti-virus or other rejections with postfix.
>>  Additionally I am not running SELinux on this box.
>
> I haven't checked the earlier messages in this thread -- I'm assuming 
> you have also done the stuff mentioned in FAQ 4.73 and 6.14?
>
>>  Now one clue that might be relevant is that when creating test lists 
>> and
>>  testing sending messages to beta users of these lists, all works fine.
>>  But as soon as the list contains the actual number of users, in one 
>> case
>>  5,100 members, in another 350 members, the mailings to the subscribers
>>  fail with the error as listed above. And there is no obvious throttling
>>  on the Postfix MTA.
>
> What is your "SMTP_MAX_RCPTS" setting?  Check both Defaults.py and 
> mm_cfg.py.  Also check the value of 
> "SMTP_MAX_SESSIONS_PER_CONNECTION".  Then compare against their 
> companion values in your postfix configuration.  If you don't define 
> the specific companion values in your /etc/postfix/main.cf, then you 
> may need to take a look at the output of "postconf -d" and look for them.
>
> See also the postfix documentation on these values, especially 
> <http://www.postfix.org/rate.html>.
>
> ------------------------------------------------------------------------
>
> ------------------------------------------------------
> Mailman-Users mailing list
> Mailman-Users at 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/
Yes, I have tried all the suggestions provided earlier in FAQ 4.73 & 6.14.
I don't have any adjustments to the defaukt settings you mentioned in my 
mm_cfg.py file, but Defaults.py state:

[user]# grep SESSIONS Mailman/Defaults.py
SMTP_MAX_SESSIONS_PER_CONNECTION = 0
[root at tao mailman]# grep RCPTS Mailman/Defaults.py
SMTP_MAX_RCPTS = 500

In /etc/postfix/main.cf I have the following settings:
smtpd_client_connection_limit_exceptions = $mynetworks
local_destination_concurrency_limit = 2
default_destination_concurrency_limit = 100
default_destination_recipient_limit = 50
maximal_backoff_time = 1000s
minimal_backoff_time = 300s

Think these need tweaking?

Which other postfix settings are the "companion values" to those Mailman 
ones?

Thanks.
---
[This E-mail scanned for viruses by Declude EVA]