Just a guess, but it looks like the next message in line to be
"digested" has some malformed header info (and Mailman/Python doesn't
check for that condition).
I suggest that you move the next message in your digest queue out of the
queue and see if that gets things moving again.
Jon Carnes
On F
A couple days ago our digests stopped going out automatically. I forced it
to run this morning via a special cron entry and received the following
report. Can anyone give me a clue as to where to go find out what's
happening?Thanks.
Traceback (most recent call last):
File "/usr/home/circle
