Howdy all,

I have my mailman list set up as an E-Newsletter distribution list, i.e. only email that I approve goes out to the list.

I am seeing the following errors being repeated over and over in my /usr/local/mailman/logs/smtp-failure log

delivery to joe@domain.com failed with code -1: Server not connected

I found a possible solution to this in mailman-users list: Write this line in your mm_cfg.py MTA = 'Postfix' SMTPHOST = 'aa.bb.cc.dd'

I already had the MTA line correct, but didn't have the SMTPHOST line. I've added that line.

My questions: 1) do I need to do anything to get mailman to re-read mm_cfg.py? 2) Will mailman re-attempt to deliver the email to this user or will he have to wait for my next newsletter email? (remember this is an E-Newsletter type list)

Thanks, Mike

Ok, I think I've found the solution, I didn't need to mess with the SMTPHOST, since localhost works just fine. I commented that line out of my mm_cfg.py file.

The following was set in my Default.py file SMTPPORT = 0 I changed it to the following in my mm_cfg.py file SMTPPORT = 25

And now it looks as though it's working. Wonder why it was set to 0 in the Default file.

-----Original Message----- From: mailman-users-bounces+flakrat=yahoo.com@python.org [mailto:mailman-users-bounces+flakrat=yahoo.com@python.org] On Behalf Of Mike Hanby Sent: Tuesday, August 30, 2005 11:53 To: mailman-users@python.org Subject: Re: [Mailman-Users] "Server not connected" in smtp-failure log

Bah, ok, I'm still having trouble with this. Some of the people on the list get the emails from the list, but a bunch of others get this error in smtp-failure like

delivery to joe@domain.com failed with code -1: Server not connected delivery to jim@example.com failed with code -1: Server not connected delivery to dave@stuff.com failed with code -1: Server not connected delivery to amy@somesite.net failed with code -1: Server not connected ... and so on

I've tried that setting SMTPHOST '127.0.0.1' and SMTPHOST '10.0.0.1' and also it's MX ip address, and all result in the following error:

Low level smtp error: Server not connected, msgid: <20050829150816.EA2F933942@mail.mydomain.com>

Commenting out SMTPHOST gets rid of the above "Low level smtp" error, but the "Server not connected" errors continue.

My MTA is PostFix

-----Original Message----- From: mailman-users-bounces+flakrat=yahoo.com@python.org [mailto:mailman-users-bounces+flakrat=yahoo.com@python.org] On Behalf Of Mike Hanby Sent: Tuesday, August 30, 2005 10:52 To: mailman-users@python.org Subject: [Mailman-Users] "Server not connected" in smtp-failure log

Howdy all,

I have my mailman list set up as an E-Newsletter distribution list, i.e. only email that I approve goes out to the list.

I am seeing the following errors being repeated over and over in my /usr/local/mailman/logs/smtp-failure log

delivery to joe@domain.com failed with code -1: Server not connected

I found a possible solution to this in mailman-users list: Write this line in your mm_cfg.py MTA = 'Postfix' SMTPHOST = 'aa.bb.cc.dd'

I already had the MTA line correct, but didn't have the SMTPHOST line. I've added that line.

My questions: 1) do I need to do anything to get mailman to re-read mm_cfg.py? 2) Will mailman re-attempt to deliver the email to this user or will he have to wait for my next newsletter email? (remember this is an E-Newsletter type list)

Thanks, Mike

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/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/flakrat%40yahoo.com

Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq01.027.htp

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/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/flakrat%40yahoo.com

Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq01.027.htp

Damn, you are right. Although some of the emails did make it through after I restarted mailman, looking in the smtp-error log shows that I'm still getting "Server not connected" errors :-(

Shoot, anyone with Postfix (or another MTA) seen this problem?

-----Original Message----- From: Mark Sapiro [mailto:msapiro@value.net] Sent: Wednesday, August 31, 2005 11:11 To: Mike Hanby; mailman-users@python.org Subject: Re: [Mailman-Users] "Server not connected" in smtp-failure log

Mike Hanby wrote:

Ok, I think I've found the solution, I didn't need to mess with the SMTPHOST, since localhost works just fine. I commented that line out of my mm_cfg.py file.

The following was set in my Default.py file SMTPPORT = 0 I changed it to the following in my mm_cfg.py file SMTPPORT = 25

And now it looks as though it's working. Wonder why it was set to 0 in the Default file.

So in effect you've done nothing since SMTPPORT = 0 tells the python smtplib to use its default SMTP port which is port 25.

It may be that this is a transient issue between Mailman and the MTA causing the connection to drop.

-----Original Message-----

<snip>

My questions:

1. do I need to do anything to get mailman to re-read mm_cfg.py?

bin/mailmanctl restart

2. Will mailman re-attempt to deliver the email to this user or will he have to wait for my next newsletter email? (remember this is an E-Newsletter type list)

If the error is considered a "temporary" failure by SMTPDirect, it will be automatically retried. If it is considered "permanent", it is treated as a "bounce".

-- Mark Sapiro <msapiro@value.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan