Hi y'all. Sorry if this is a little long.
The continuing problem is that 1) the "welcome to the mailman list" e-mail (in
German no less), 2) the first message I sent to the mailman list and then 3)
the administrative warning message from Maillman regarding a subsequent message
all go out to me time and again. A second e-mail account gets my first message
over and over.
Mailman doesn't know that I have received a welcome, confirmed I want to be on
the list by sending back an e-mail, started using the mailman list for testing
and I've attended to the administrative task by discarding the over 50kb
attachment-laden e-mail. All three e-mails go out every 5 minutes or so until I
stop the qrunner(s).
The second message I sent to the mailman list had attachments for testing
scrub; over 50 mb no doubt. That subsequent e-mail has never arrived, but a
Mailman message informing me that there is an administrative task arrived. I
went to the web admin and discarded the message, but the administrative warning
message continues to arrive every 5 minutes, just like freakin clockwork. Could
there be two identical cron entries causing this or what?
My set-up -
freeBSD 4.7 virtual server - (bigtuner dot com and uniconexed dot org)
mm-cfg.py has the unicon.org default and the add virtual host entry.
sendmail v 8.13.1 with
define(`confTRUSTED_USERS',`mailman'),
FEATURE(`smrsh') ( with soft link to usr/local/mailman/mail/mailman)
FEATURE(`greet_pause')
FEATURE(local_procmail)
MAILER(`local')
MAILER(`smtp')
Mailman v 2.1.6
In usr/local/mailman/locks, mailmanctl starts master-qrunner AND
master-qrunner.bigtxxxx dot com dot 17567 (or some other number) Is that
correct? In usr/local/mailman/data, I have one master-qrunner.pid.
Logs --
Mailman logs have 137KB of locks entries of the type
Jul 27 20:31:00 2005 (9701) mailman.lock unlocked
Jul 27 20:31:00 2005 (9701) File "/usr/local/mailman/Mailman/LockFile.py",
line 363, in __del__
Jul 27 20:31:00 2005 (9701) self.finalize()
Jul 27 20:31:00 2005 (9701) File "/usr/local/mailman/Mailman/LockFile.py",
line 359, in finalize
Jul 27 20:31:00 2005 (9701) self.unlock(unconditionally=True)
Jul 27 20:31:00 2005 (9701) File "/usr/local/mailman/Mailman/LockFile.py",
line 335, in unlock
Jul 27 20:31:00 2005 (9701) self.__writelog('unlocked')
Jul 27 20:31:00 2005 (9701) File "/usr/local/mailman/Mailman/LockFile.py",
line 416, in __writelog
Jul 27 20:31:00 2005 (9701) traceback.print_stack(file=logf)
mailman/logs post read
Jul 27 18:54:14 2005 (17583) post to mailman from [EMAIL PROTECTED], size=1783,
message-id=<[EMAIL PROTECTED]>, 1 failures
qrunner logs say
Jul 27 20:26:55 2005 (17567) Master watcher caught SIGTERM. Exiting.
Jul 27 20:26:55 2005 (17567) Master qrunner detected subprocess exit (pid:
17582, sig: None, sts: 15, class: NewsRunner, slice: 1/1)
Jul 27 20:26:55 2005 (17567) Master qrunner detected subprocess exit (pid:
17581, sig: None, sts: 15, class: IncomingRunner, slice: 1/1)
Jul 27 20:26:55 2005 (17567) Master qrunner detected subprocess exit (pid:
17579, sig: None, sts: 15, class: BounceRunner, slice: 1/1)
Jul 27 20:26:55 2005 (17567) Master qrunner detected subprocess exit (pid:
17578, sig: None, sts: 15, class: ArchRunner, slice: 1/1)
Jul 27 20:26:55 2005 (17567) Master qrunner detected subprocess exit (pid:
17580, sig: None, sts: 15, class: CommandRunner, slice: 1/1)
Jul 27 20:26:55 2005 (17567) Master qrunner detected subprocess exit (pid:
17584, sig: None, sts: 15, class: VirginRunner, slice: 1/1)
Jul 27 20:26:55 2005 (17567) Master qrunner detected subprocess exit (pid:
17583, sig: None, sts: 15, class: OutgoingRunner, slice: 1/1)
Jul 27 20:26:55 2005 (17585) RetryRunner qrunner exiting.
Jul 27 20:26:55 2005 (17567) Master qrunner detected subprocess exit (pid:
17585, sig: None, sts: 15, class: RetryRunner, slice: 1/1)
partial mailman/logs smtp say
Jul 27 20:10:10 2005 (17583) <[EMAIL PROTECTED]> smtp to mailman for 1 recips,
completed in 3.799 seconds
Jul 27 20:25:06 2005 (17583) <[EMAIL PROTECTED]> smtp to mailman for 1 recips,
completed in 1.167 seconds
Jul 27 20:25:07 2005 (17583) <[EMAIL PROTECTED]> smtp to mailman for 2 recips,
completed in 0.408 seconds
Jul 27 20:25:24 2005 (17583) <[EMAIL PROTECTED]> smtp to mailman for 1 recips,
completed in 6.489 seconds
partial smtp-failure logs say
Jul 27 20:25:06 2005 (17583) SMTP session failure: -1, es_setoptions(" debug,
msgid: <[EMAIL PROTECTED]>
Jul 27 20:25:06 2005 (17583) SMTP session failure: -1, es_setoptions(" debug,
msgid: <[EMAIL PROTECTED]>
vette logs say (regarding the subsequent message, no doubt)
Jul 27 18:18:22 2005 (32572) Mailman post from [EMAIL PROTECTED] held,
message-id=<[EMAIL PROTECTED]>: Message body is too big: 12472312 bytes with a
limit of 50 KB
Jul 27 18:46:20 2005 (7448) mailman: Discarded posting:
From: [EMAIL PROTECTED]
Subject: test wtih attachments
Reason: Your message was too big; please trim it to less than 50 KB in size.
Finally, in my var/mail logs, I get entries like
Jul 27 20:25:22 bigtuner sm-mta[3485]: j6RKPHh3003485: --- 221 2.0.0
bigtuner.com closing connection
Jul 27 20:25:22 bigtuner sm-mta[3543]: j6RKPHh1003485: --- 050 <[EMAIL
PROTECTED]>... Connecting to gateway-r.comcast.net. via esmtp...
Jul 27 20:25:22 bigtuner sm-mta[3543]: j6RKPHh1003485: SMTP outgoing connect on
bigtuner.com
Jul 27 20:25:54 bigtuner sm-mta[3543]: j6RKPHh1003485: --- 050 <[EMAIL
PROTECTED]>... Sent (ok ; id=20050727202522r2200og6ste)
Jul 27 20:25:54 bigtuner sm-mta[3543]: j6RKPHh1003485: to=<[EMAIL PROTECTED]>,
delay=00:00:37, xdelay=00:00:32, mailer=esmtp, pri=12615209,
relay=gateway-r.comcast.net.[216.148.227.126], dsn=2.0.0, stat=Sent (ok ;
id=20050727202522r2200og6ste)
Jul 27 20:25:54 bigtuner sm-mta[3543]: j6RKPHh1003485: done; delay=00:00:37,
ntries=1
Jul 27 20:25:55 bigtuner sm-mta[3543]: NOQUEUE: --- 050 Closing connection to
gateway-r.comcast.net.
In usr/local/mailman/data, I have one master-qrunner.pid. In
usr/local/mailman/locks, mailmanctl starts master-qrunner AND
master-qrunner.bigtxxxx dot com dot 17567 (or some other number) Is that
correct?
Could it be that the locks aren't staying alive long enough to process a
message?
Do I need to restart sendmail whenever I restart Mailman?
What's with the NOQUEUE mail log entry?
Is this a sendmail problem and not Mailman at all?
I'm just grabbing at straws. I've spent plenty of time researching this in the
four months since I first loaded the older 2.1.5 on my server; I'm not a
minute closer to have this resolved, so, help me if you can. My non-profit
guys are getting a little restless waiting for a stable list server.
Thank you every one for your input.
Dan
------------------------------------------------------
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/archive%40jab.org
Security Policy:
http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq01.027.htp
