Almost a year ago, in
http://mail.python.org/pipermail/mailman-users/2005-April/043992.html,
Mark Sapiro wrote (in response to a question about this error):
This error caused the message to be shunted (placed in the shunt
queue). You can run bin/unshunt to reprocess the message, but unless
Steve Burling wrote:
Almost a year ago, in
http://mail.python.org/pipermail/mailman-users/2005-April/043992.html,
Mark Sapiro wrote (in response to a question about this error):
This error caused the message to be shunted (placed in the shunt
queue). You can run bin/unshunt to reprocess the
--On March 21, 2007 7:07:04 AM -0700 Mark Sapiro [EMAIL PROTECTED] wrote:
However, that response was to a specific occurrence of this exception
in Decorate.py. If you are seeing this exception with a different
traceback, changing the language character set won't eliminate the
exception.
A
Hi,
I am importing some old mail into a list and I get the following exception:
Updating HTML for article 292
Updating HTML for article 293
Pickling archive state into
/usr/local/mailman/archives/private/support/pipermail.pck
Traceback (most recent call last):
File bin/arch, line
Kevin McNamee wrote:
I am importing some old mail into a list and I get the following exception:
snip
File /usr/local/mailman/Mailman/Archiver/HyperArch.py, line 579, in
as_text
'\g1' + _(' at ') + '\g2', body)
File /usr/sfw/lib/python2.3/sre.py, line 143, in sub
return
I'm seeing a problem where messages get in to mailman, and into
the archives, but never get sent. When this happens I see this
in the error log:
Apr 07 22:14:30 2005 (2477) Uncaught runner exception: 'ascii'
codec can't decode byte 0x92 in position 291: ordinal not in
range(128)
Apr 07
Richard Pyne wrote:
I'm seeing a problem where messages get in to mailman, and into
the archives, but never get sent. When this happens I see this
in the error log:
snip
File /usr/local/mailman/Mailman/Handlers/Decorate.py, line
95, in process
payload = header + frontsep + oldpayload +
