[Mailman-Users] Mailman getting stuck while trying to send a message

Stephen J. Turnbull stephen at xemacs.org
Wed Apr 27 13:55:20 CEST 2005

>>>>> "Remi" == Remi Delon <remi at cherrypy.org> writes:

    Remi> Thanks for the insight Michael... If a junk address is
    Remi> indeed all it takes to cause Mailman to hang then it's quite
    Remi> disapointing ...

It's not.  I've never seen Mailman hang like that in more than 4
years, with versions 2.0.13 and 2.1.5.

    Remi> How would I go about finding that junk address (there are
    Remi> more than 200 in that list) ?

It's probably the one listed in smtp-failure, see below.

    Remi> Isn't it true that all addresses must have been valid at
    Remi> some point ? (otherwise people wouldn't have been able to
    Remi> confirm their subscription).

True.  But that's not the kind of "junk" that causes problems for
Mailman; Mailman will disable delivery or unsubscribe addresses that
become invalid.  The "junk" that causes Mailman to blow up are
syntactically invalid (eg, contain illegal characters) and must be
introduced by the list admin using "mass subscribe" or a command line
tool.  If you've never done that, ie, all your users subscribed
themselves, then you will have no problematic junk addresses, just
undeliverable ones that will be automatically weeded out.

In your earlier message you provided this log:

smtp-failure:Apr 24 07:39:11 2005 (26501) delivery to
<removed-email-address> failed with code -1: please run connect() first

While it's possible that there's a connect() function in Mailman that
Mailman is failing to run, that seems very unlikely ... we would have
heard about it by now.  There is a connect() function in many OSes,
for the "socket" interface layered over raw Internet connections.  It
seems quite possible to me that your OS or network is hosed, resulting
socket connections appearing to be internally broken, and Mailman
being unable to connect to a remote host for long periods of time.  In
that case, it might very well hang assuming that it should keep trying
until the network admin fixes whatever the problem is.

As far as I can tell, Mac OS X sometimes wedges itself in this way.
An SSH connection will simply go away ... until I connect to the same
host in a separate connection.  Then the shell will come back up, the
X tunnel will start working again, etc, etc.

    Remi> I'm currently running version 2.1.4. Could this be fixed by
    Remi> upgrading to the latest version ?

Waiting a bit and upgrading to 2.1.6 (due out real soon) might (or
might not) be a good idea.

However, if my guess that the smtp-failure message is coming from the
OS is correct, upgrading Mailman is not very likely to fix it.

School of Systems and Information Engineering http://turnbull.sk.tsukuba.ac.jp
University of Tsukuba                    Tennodai 1-1-1 Tsukuba 305-8573 JAPAN
               Ask not how you can "do" free software business;
              ask what your business can "do for" free software.

More information about the Mailman-Users mailing list