[Mailman-Users] shunt messages
Hello, We are having some serious problem with a 2.1.2 mailman install. Some messages get transferred to qfiles/shunt and stay there forever. I am calling on your help on this one. I understand from previous mailing list posts that the shunt directory is used by mailman if: o messages are too large to get delivered o bug in mailman o problem with python installation The original error message (in logs/error) was indicating some problem with the 'strptime' module: This was confirmed: python Python 2.2 (#1, Aug 4 2003, 14:00:57) [GCC 2.95.2 19991024 (release)] on darwin Type help, copyright, credits or license for more information. import time time.strptime Traceback (most recent call last): File stdin, line 1, in ? AttributeError: 'module' object has no attribute 'strptime' In the hope of remedying this, I have installed python 2.3 Python 2.3 (#1, Sep 17 2003, 21:23:32) [GCC 2.95.2 19991024 (release)] on darwin Type help, copyright, credits or license for more information. import time time.strptime built-in function strptime As you can see python is now happy with the time.strptime module. I then proceeded to reinstall mailman. All seemed fine. I then proceeded to unshunt the messages... In vain. They come back to the shunt directory. However, the error is different: Sep 18 08:42:40 2003 (15588) Uncaught runner exception: Empty module name Sep 18 08:42:40 2003 (15588) Traceback (most recent call last): File /Users/mailman/Mailman/Queue/Runner.py, line 105, in _oneloop self._onefile(msg, msgdata) File /Users/mailman/Mailman/Queue/Runner.py, line 155, in _onefile keepqueued = self._dispose(mlist, msg, msgdata) File /Users/mailman/Mailman/Queue/IncomingRunner.py, line 130, in _dispose more = self._dopipeline(mlist, msg, msgdata, pipeline) File /Users/mailman/Mailman/Queue/IncomingRunner.py, line 153, in _dopipelin e sys.modules[modname].process(mlist, msg, msgdata) File /Users/mailman/Mailman/Handlers/ToDigest.py, line 89, in process send_digests(mlist, mboxfp) File /Users/mailman/Mailman/Handlers/ToDigest.py, line 130, in send_digests send_i18n_digests(mlist, mboxfp) File /Users/mailman/Mailman/Handlers/ToDigest.py, line 303, in send_i18n_dig ests msg = scrubber(mlist, msg) File /Users/mailman/Mailman/Handlers/Scrubber.py, line 308, in process t = t.encode(charset, 'replace') File /usr/local/lib/python2.3/encodings/__init__.py, line 84, in search_func tion globals(), locals(), _import_tail) ValueError: Empty module name Sep 18 08:42:40 2003 (15588) SHUNTING: 1063634404.28272+cdaf6755ebc39a35d78f 3db0024abd9cce07 Any ideas? Nic CEH Oxford -- Mailman-Users mailing list [EMAIL PROTECTED] 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/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: Fwd: [Mailman-Users] shunt messages
OK... Just found that post in the mailman-developers list that did the
trick:
http://www.mail-archive.com/[EMAIL PROTECTED]/msg06317.html
Barry, as was noted in a private email to ya - the problem was solved
with
the following patch (courtesy of Mohammed Elzubeir),
--- Scrubber.py.orig 2003-08-13 23:19:19.0 -0700
+++ Scrubber.py 2003-08-14 00:23:47.0 -0700
@@ -305,6 +305,8 @@
t = unicode(t, 'ascii',
'replace').encode('ascii')
try:
# Should use HTML-Escape, or try generalizing to
UTF-8
+ if len(charset) == 0:
+ charset = 'us-ascii'
t = t.encode(charset, 'replace')
except (UnicodeError, LookupError):
t = t.encode(lcset, 'replace')
once we applied the patch and 'unshunt'ed everything went through. We
did have a couple of messages with no Mime and Content-Type headers
(which are legal to have) and those seemed to have caused the problem.
A null charset within mailman caused our problems it seems and that
potential corner-case needs to be designed for. As for a sample - I
tried mailing the affected list a simple test from this yahoo
account and it got shunted (as noted there is nothing peculiar about
the messages - mailman simply got into a state/setting where it
started
shunting everything -- Larry Price notes a possible means to get into
the 'state' above). And again, I really don't think it was/is a
configuration/installation issue since the other 12 lists work without
any complaints and/or problems.
Cheers,
Nic
Nicolas Bertrand 09/18/03 09:14am
Nicolas Bertrand [EMAIL PROTECTED] 09/18/03 08:57am
Hello,
We are having some serious problem with a 2.1.2 mailman install. Some
messages get transferred to qfiles/shunt and stay there forever. I am
calling on your help on this one.
I understand from previous mailing list posts that the shunt directory
is used by mailman if:
o messages are too large to get delivered
o bug in mailman
o problem with python installation
The original error message (in logs/error) was indicating some problem
with the 'strptime' module:
This was confirmed:
python
Python 2.2 (#1, Aug 4 2003, 14:00:57)
[GCC 2.95.2 19991024 (release)] on darwin
Type help, copyright, credits or license for more information.
import time
time.strptime
Traceback (most recent call last):
File stdin, line 1, in ?
AttributeError: 'module' object has no attribute 'strptime'
In the hope of remedying this, I have installed python 2.3
Python 2.3 (#1, Sep 17 2003, 21:23:32)
[GCC 2.95.2 19991024 (release)] on darwin
Type help, copyright, credits or license for more information.
import time
time.strptime
built-in function strptime
As you can see python is now happy with the time.strptime module.
I then proceeded to reinstall mailman. All seemed fine. I then
proceeded to unshunt the messages... In vain. They come back to the
shunt directory.
However, the error is different:
Sep 18 08:42:40 2003 (15588) Uncaught runner exception: Empty module
name
Sep 18 08:42:40 2003 (15588) Traceback (most recent call last):
File /Users/mailman/Mailman/Queue/Runner.py, line 105, in _oneloop
self._onefile(msg, msgdata)
File /Users/mailman/Mailman/Queue/Runner.py, line 155, in _onefile
keepqueued = self._dispose(mlist, msg, msgdata)
File /Users/mailman/Mailman/Queue/IncomingRunner.py, line 130, in
_dispose
more = self._dopipeline(mlist, msg, msgdata, pipeline)
File /Users/mailman/Mailman/Queue/IncomingRunner.py, line 153, in
_dopipelin
e
sys.modules[modname].process(mlist, msg, msgdata)
File /Users/mailman/Mailman/Handlers/ToDigest.py, line 89, in
process
send_digests(mlist, mboxfp)
File /Users/mailman/Mailman/Handlers/ToDigest.py, line 130, in
send_digests
send_i18n_digests(mlist, mboxfp)
File /Users/mailman/Mailman/Handlers/ToDigest.py, line 303, in
send_i18n_dig
ests
msg = scrubber(mlist, msg)
File /Users/mailman/Mailman/Handlers/Scrubber.py, line 308, in
process
t = t.encode(charset, 'replace')
File /usr/local/lib/python2.3/encodings/__init__.py, line 84, in
search_func
tion
globals(), locals(), _import_tail)
ValueError: Empty module name
Sep 18 08:42:40 2003 (15588) SHUNTING:
1063634404.28272+cdaf6755ebc39a35d78f
3db0024abd9cce07
Any ideas?
Nic
CEH Oxford
--
Mailman-Users mailing list
[EMAIL PROTECTED]
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/
This message was sent to: [EMAIL PROTECTED]
Unsubscribe or change your options at
http://mail.python.org/mailman/options/mailman-users/nsb%40ceh.ac.uk
--
Mailman-Users mailing list
[EMAIL PROTECTED]
http://mail.python.org/mailman/listinfo/mailman-users
Mailman
Re: [Mailman-Users] Big delays wrapper to delivery
Thanks for the reply. The time between does indeed equates to the time between the message arrives to mailman and seen going to the subscribers (i.e. accepted by their relays/MTAs). This totally independent to the size of the list. f time (1) to time (2) is where the 8 to 12 hours is going, are you saying nothing is showing in the qfiles directory during that time? *** This is correct Assume you are using MM 2.0.x; which value of x? *** 2.0.9 Which MTA? *** Postfix Nic Richard Barrett [EMAIL PROTECTED] 07/26/03 23:35 PM On Saturday, July 26, 2003, at 08:09 PM, Nicolas Bertrand wrote: Hello We have a few low volume mailing lists . We have been been happy with the performance since instigating these (about a year and half ago) and these mailing lists have become quite important. However, suddenly, delivery times to subscribers have increased to 8-12 hours and cannot figure out what has gone wrong... Info: 1.MTA is postfix. 2.Mail gets received by the email server which then triggers 'wrapper post' Then it takes 8-12 hours to get the mail delivered. 3.This problem is specific to mailing lists (all the other mail is fine) 4. The load on the server is minimal 5. no locks 6. nothing in qfiles 7. no errors in ~mailman/logs 8. no error in maillog 9. qrunner is executed by cron every minute, no error is being generated. Same thing, with running qrunner manually from the command line. Any ideas? Nic Is that 8 to 12 hours for a message between the following times: 1. from the time the MTA's log records as delivering the message to the Mailman 2. to the time logged by MM in post and smtp logs for the message going out to the subscribers. Does time (2) fit with the MTA's log showing the time it got the outgoing message from MM? What time does the MTA show handing off the message to the next MTA? If time (1) to time (2) is where the 8 to 12 hours is going, are you saying nothing is showing in the qfiles directory during that time? *** This is correct Assume you are using MM 2.0.x; which value of x? *** 2.0.9 Which MTA? *** Postfix -- Mailman-Users mailing list [EMAIL PROTECTED] 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/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Big delays wrapper to delivery
Richard, Thanks for that. I have now enabled the more verbose logging option for the SMTPDirect.py module. I have noticed that a few qrunner processed are currently running on the machine... Should these quit as soon are they are done? mailman 8270 11.2 0.8 8068 3288 ?? Us 0:00.47 /sw/bin/python -S /home/mailman/cron/gate_news mailman 4284 3.2 20.3 377864 79996 ?? Us 128:07.89 /sw/bin/python -S /home/mailman/cron/qrunner mailman 8269 0.7 0.8 7832 3092 ?? Ss 0:00.48 /sw/bin/python -S /home/mailman/cron/qrunner mailman 2731 0.4 20.4 388516 80132 ?? Us 203:00.31 /sw/bin/python -S /home/mailman/cron/qrunner mailman 6059 0.2 20.4 381572 80156 ?? Us 100:16.76 /sw/bin/python -S/home/mailman/cron/qrunner mailman 7700 0.0 20.5 380876 80692 ?? Us80:53.90 /sw/bin/python -S /home/mailman/cron/qrunner mailman 7872 0.0 0.2 8052720 ?? Ss 0:11.59 /sw/bin/python -S /home/mailman/cron/senddigests Nic Richard Barrett [EMAIL PROTECTED] 07/27/03 13:21 PM Nicolas This is rather mysterious. I cannot offer a solution but I think it might be an idea to try and get more information about what is happening. I am assuming you have your DELIVERY_MODULE = 'SMTPDirect' in Defaults.py/mm_cfg.py There are some statements in the $prefix/Mailman/Handlers/SMTPDirect.py module which log more detail about Mailman's interaction with the SMTP server but which are commented out as standard. Uncommenting these lines [deleting the # character(s) from the start of the lines] might get some useful information logged. Looking at a copy of the SMTPDirect.py file from a freshly unpacked mailman-2.0.6.tgz, I am referring to lines 204, 212, 213 and 214. In the absence of a flash of insight it might be worth trying. Let me know how you get on Richard On Sunday, July 27, 2003, at 11:47 AM, Nicolas Bertrand wrote: Thanks for the reply. The time between does indeed equates to the time between the message arrives to mailman and seen going to the subscribers (i.e. accepted by their relays/MTAs). This totally independent to the size of the list. f time (1) to time (2) is where the 8 to 12 hours is going, are you saying nothing is showing in the qfiles directory during that time? *** This is correct Assume you are using MM 2.0.x; which value of x? *** 2.0.9 Which MTA? *** Postfix Nic Richard Barrett [EMAIL PROTECTED] 07/26/03 23:35 PM On Saturday, July 26, 2003, at 08:09 PM, Nicolas Bertrand wrote: Hello We have a few low volume mailing lists . We have been been happy with the performance since instigating these (about a year and half ago) and these mailing lists have become quite important. However, suddenly, delivery times to subscribers have increased to 8-12 hours and cannot figure out what has gone wrong... Info: 1.MTA is postfix. 2.Mail gets received by the email server which then triggers 'wrapper post' Then it takes 8-12 hours to get the mail delivered. 3.This problem is specific to mailing lists (all the other mail is fine) 4. The load on the server is minimal 5. no locks 6. nothing in qfiles 7. no errors in ~mailman/logs 8. no error in maillog 9. qrunner is executed by cron every minute, no error is being generated. Same thing, with running qrunner manually from the command line. Any ideas? Nic Is that 8 to 12 hours for a message between the following times: 1. from the time the MTA's log records as delivering the message to the Mailman 2. to the time logged by MM in post and smtp logs for the message going out to the subscribers. Does time (2) fit with the MTA's log showing the time it got the outgoing message from MM? What time does the MTA show handing off the message to the next MTA? If time (1) to time (2) is where the 8 to 12 hours is going, are you saying nothing is showing in the qfiles directory during that time? *** This is correct Assume you are using MM 2.0.x; which value of x? *** 2.0.9 Which MTA? *** Postfix - Richard Barrett http://www.openinfo.co.uk -- Mailman-Users mailing list [EMAIL PROTECTED] 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/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
[Mailman-Users] Big delays wrapper to delivery
Hello We have a few low volume mailing lists . We have been been happy with the performance since instigating these (about a year and half ago) and these mailing lists have become quite important. However, suddenly, delivery times to subscribers have increased to 8-12 hours and cannot figure out what has gone wrong... Info: 1.MTA is postfix. 2.Mail gets received by the email server which then triggers 'wrapper post' Then it takes 8-12 hours to get the mail delivered. 3.This problem is specific to mailing lists (all the other mail is fine) 4. The load on the server is minimal 5. no locks 6. nothing in qfiles 7. no errors in ~mailman/logs 8. no error in maillog 9. qrunner is executed by cron every minute, no error is being generated. Same thing, with running qrunner manually from the command line. Any ideas? Nic -- Mailman-Users mailing list [EMAIL PROTECTED] 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/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
