[Mailman-Users] "Server not connected" in smtp-failure log

[Mike Hanby]

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 at value.net] 
Sent: Wednesday, August 31, 2005 11:11
To: Mike Hanby; mailman-users at 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 at value.net>       The highway is for gamblers,
San Francisco Bay Area, California    better use your sense - B. Dylan