The essential question is:
Does anyone know how to either parallelize the shunting, so mailman process multiple
messages and doesn't just stall at the shunting or make shunting at least a degree of
magnitude faster.
The full story:
So, the ValueError: Empty module name is still a pretty big
- Original Message -
From: sumeet
To: [EMAIL PROTECTED]
Sent: Friday, August 22, 2003 12:06 AM
Subject: Fw: further empty module name woes
I have a list that i created ages ago, then suddenly at 9:51am w/ no prompting from me
I started getting the error below. Previously
I have a list that i created ages ago, then suddenly at 9:51am w/ no prompting from me
I started getting the error below. Previously it was related to localization issues,
now even when i send a test message w or w/o text and/or subject from the mailman host
it gets shunted immediately. I'm
I went to Python 2.2.2 and got the same errors. I think the thing to note is
that i did patch my MailMan w/ the Scrubber.py patch from Tokio Kikuchi.
The header problem was getting to be too much. But i did not do this
recently and the problem just appeared. any other suggestions? thanks.
sumeet
my mail halts eniterly on what i think are rejection notices, until this
message is sent out, at which point mail starts flowing again:
[EMAIL PROTECTED] in]# Traceback (most recent call last):
File /list/bin/qrunner, line 270, in ?
main()
File /list/bin/qrunner, line 230, in main
I seem to be getting alot (about 700) of these all of the sudden w no
changes to my Rhat 8.0/MM2.1.1 and sendmail 8.11.6. Can someone please point
me in the right direction. thx, sumeet.
Mar 17 04:03:56 2003 (1735) Traceback (most recent call last):
File /list/Mailman/Queue/Runner.py, line 105
I tried to upgrade just python-devel
to 2.2.2 and mailman stopped sending messages for the duration that it was
the old version. I'll bite and upgrade to the newest available python and
see what is going on.
- Original Message -
From: Barry A. Warsaw [EMAIL PROTECTED]
To: Sumeet [EMAIL
Yeah, I've done this. Well the patch is pretty easy, patch against the files
listed and configure make make install and all is OK. The thing to note
is -- and i listed this in one of my archive messages is that it breaks the
spaces up in a different manner. it is not a complete fix and if your
rather than messing w/ all this python stuff that you don't know about
wouldn't it be better to place spamassassin on your MTA, add an improbable
subject tag, and use procmail to filter all that stuff out before it even
gets to mailman?
- Original Message -
From: Jonas Meurer [EMAIL
, but after it has already mangled the subject line?
thanks, sumeet.
- Original Message -
From: Sumeet Pannu [EMAIL PROTECTED]
To: [EMAIL PROTECTED]; Mitchell Marks [EMAIL PROTECTED]
Sent: Monday, February 24, 2003 12:52 AM
Subject: [Mailman-Users] Re: Example of bad line break in subject header
The biggest problem isn't really your particular email client, it's
procmail. I agree with you that it is not confined to any particular sort of
message plain text etc, all have subject wrapping turned on. I'm trying to
get around it by using some procmail magic, but the block format is really
this is a test
this is a test this is a test this is a test t his is a
test this is a test.
I replaced Header.py by cping it and placing your file in ~mailman/pythonlib/email/
and running patch headerpatch.diff which ran successfully. thx, sumeet.
- Original Message
'.
Alternatively a migration back to 2.0.13 would be acceptable if anyone has
done this. Thanks, sumeet.
- Original Message -
From: Mitchell Marks [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Sunday, February 23, 2003 3:48 PM
Subject: Example of bad line break in subject header was Re: [Mailman
imagine it being too much
better.
Thanks, sumeet.:
[EMAIL PROTECTED] root]# /usr/bin/python -S /var/mailman/cron/senddigests
Traceback (most recent call last):
File /var/mailman/cron/senddigests, line 94, in ?
main()
File /var/mailman/cron/senddigests, line 86, in main
: 'NoneType' object has no attribute 'endswith'
- Original Message -
From: Tokio Kikuchi [EMAIL PROTECTED]
To: Sumeet [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Sent: Sunday, February 23, 2003 4:07 PM
Subject: Re: [Mailman-Users] Upgrade from 2.0.x to 2.1.1-- incorrect
paddingerror.
Try
=42418aid=601117
Tokio
Mitchell Marks wrote:
I'm enclosing below the full headers from Sumeet P's recent message, as
they reached me. This shows the formatting problem discussed last week,
mentioned on the Mailman-Users list by Sarah from NOW and seconded by
me, and also turned over
. Alternatively does anyone
have info on migrating from 2.1 to 2.0?
thanks
sumeet.
example:
Subject: [build-notify]
This an example of broken subject headers.
It will break my procmail.
--
Mailman-Users mailing list
[EMAIL
17 matches
Mail list logo
