At 05:34 PM 2/10/03 -0800, you wrote:
Yesterday we upgraded from Mailman 2.0.x to 2.1.1. All of the lists
except for one transfered over flawlessly, but any mail sent to that one
particular list causes errors like this to be dumped into
~mailman/logs/error:
Yea, I've got a sourceforge bug open
Yesterday we upgraded from Mailman 2.0.x to 2.1.1. All of the lists
except for one transfered over flawlessly, but any mail sent to that one
particular list causes errors like this to be dumped into
~mailman/logs/error:
Feb 10 17:05:20 2003 (453) Uncaught runner exception: Incorrect padding
Feb
DG == David Gibbs [EMAIL PROTECTED] writes:
DG I'm getting a huge amount of these messages ... any ideas?
Not off hand, but I have an idea. Can you please submit a bug report
and include one of the shunted messages?
Thanks,
-Barry
--
I'm getting a huge amount of these messages ... any ideas?
Jan 30 12:47:18 2003 (9406) Uncaught runner exception: Incorrect padding
Jan 30 12:47:18 2003 (9406) Traceback (most recent call last):
File /usr/local/mailman/Mailman/Queue/Runner.py, line 105, in _oneloop
self._onefile(msg,
