Mailman and SMTPDirect stop talking, mailing totally fails
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
GNU Mailman |
Fix Released
|
High
|
Barry Warsaw |
Bug Description
I'm using Mailman 2.1 and Mac OS X 10.2.5.
When I send my message (a personalized, announce-only list),
after the first 150 or so deliveries (out of 19640), Mailman
suddenly seems to stop communicating to the SMTP server, and
all remaining recipients fail.
There are no real good clues in /var/log/mail.log as to why SMTP
is getting grumpy. These are the interesting parts of mail.log that
appear around the time of failure -- everything else looks fine.
-- /var/log/mail.log:
Apr 23 15:06:39 newposh sendmail[5928]: h3NM4o0o005928:
SYSERR(root): Cannot create ./dfh3NM4o0o005928: File exists
[..]
Apr 23 15:06:40 newposh sendmail[6251]: h3NM4o0j005928:
to=<email address hidden>, delay=00:00:01, xdelay=00:00:01,
mailer=esmtp, pri=85368, relay=vm4-
[207.115.63.115], dsn=5.3.0, stat=User unknown
Apr 23 15:06:40 newposh sendmail[6251]: h3NM4o0j005928:
h3NM6ewS006251: DSN: User unknown.
-- logs/smtp:
Apr 23 15:08:25 2003 (663) All recipients refused: please run
connect() first
Apr 23 15:08:25 2003 (663) All recipients refused: please run
connect() first
Apr 23 15:08:25 2003 (663) All recipients refused: please run
connect() first
Apr 23 15:08:25 2003 (663) All recipients refused: please run
connect() first
[..etc..]
-- logs/error:
Apr 23 15:08:25 2003 (663) Uncaught runner exception: please
run connect() first
Apr 23 15:08:25 2003 (663) Traceback (most recent call last):
File "/usr/local/
in _oneloop
self.
File "/usr/local/
in _onefile
keepqueued = self._dispose(
File "/usr/local/
line 61, in _dispose
self.
File "/usr/local/
150, in process
conn.quit()
File "/usr/local/
80, in quit
self.
File "/BinaryCache/
python2.
self.
File "/BinaryCache/
python2.
self.
File "/BinaryCache/
python2.
self.send(str)
File "/BinaryCache/
python2.
raise SMTPServerDisco
SMTPServerDisco
Apr 23 15:08:25 2003 (663) SHUNTING:
1051135414.
f273a
--
Please let me know if there's anything I can do to help you find
the cause of this problem.
Thanks!
[http://
I believe I fixed this for Mailman 2.1.2. If after that's
release (RSN, I promise!) if this bug recurs, please reopen
this bug report.