[Mailman-Users] RE;Cron/senddigests bug
dhphllps at memphis.edu
Mon Feb 3 01:59:00 CET 2003
Thanks. I've done that once before, and as you said, the problem was
obvious. My difficulty this time is that every message in the box went
out just fine as individual emails. There were a couple that were
content-transfer-encoding: quoted-printable, which on my old system
caused multiple problems, and always look bad in the digest, with lines
truncated with =20 mid-word, etc. I already removed two of them and
retried to send the digest without success.
Incidentally, as I mentioned in the first message, I cleaned up the
headers within digests by commenting out some lines in
/handlers/ToDigest.py, excluding everything but date, to, from and
subject. Is that likely to gum up the works somewhere along the line? I
suppose that breaks rfc1153 by excluding message-id and keywords, but
does that have any effect at all within a digest?
On Sunday, February 2, 2003, at 06:36 PM, Jon Carnes wrote:
> I've had to go into Mbox before and delete a few messages that were
> gumming up the works. What I normally do is simply look at the last
> message to be processed and then delete the next message from the Mbox.
> At that point it normally becomes obvious what the problem with the
> offending mail message was - its always easier once you know which
> message it is.
> Good Luck - Jon Carnes
> On Sun, 2003-02-02 at 19:06, Dan Phillips wrote:
>> Tried that and it reported no problems. The problem definitely seems
>> be in digest.mbox, although I can't see anything wrong. I renamed it
>> and sent a test message to create a new one, the ran cron/senddigests
>> -l, and it went out fine. when I moved the original mbox back it
>> generated the same error. I also ran bin/cleanarch on it and it
>> reported no problems and the correct number of messages.
>> Where's the best documentation on the structure of an mbox file?
>> On Sunday, February 2, 2003, at 06:00 PM, Jon Carnes wrote:
>>> Run a check_db on the offending list and see if the problem lays in
>>> Database for the list...
>>> On Sun, 2003-02-02 at 17:54, Dan Phillips wrote:
>>>> Any idea where this error is coming from? This error is coming from
>>>> only one list; a manual running of senddigests -l on other lists
>>>> functions perfectly. /lists/problemlist/digest.mbox appears to be
>>>> fine. Any ideas? anyone? what else should I be checking?
>>>>> Traceback (most recent call last):
>>>>> File "/Users/mailman/cron/senddigests", line 94, in ?
>>>>> File "/Users/mailman/cron/senddigests", line 86, in main
>>>>> File "/Users/mailman/Mailman/Digester.py", line 60, in
>>>>> ToDigest.send_digests(self, mboxfp)
>>>>> File "/Users/mailman/Mailman/Handlers/ToDigest.py", line 129, in
>>>>> send_i18n_digests(mlist, mboxfp)
>>>>> File "/Users/mailman/Mailman/Handlers/ToDigest.py", line 290, in
>>>>> g(msg, unixfrom=0)
>>>>> File "/Users/mailman/pythonlib/email/Generator.py", line 100, in
>>>>> File "/Users/mailman/pythonlib/email/Generator.py", line 128, in
>>>>> File "/Users/mailman/pythonlib/email/Generator.py", line 154, in
>>>>> File "/Users/mailman/pythonlib/email/Generator.py", line 212, in
>>>>> raise TypeError, 'string payload expected: %s' % type(payload)
>>>>> TypeError: string payload expected: <type 'list'>
>> Mailman-Users mailing list
>> Mailman-Users at python.org
>> Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
>> Searchable Archives:
>> This message was sent to: jonc at nc.rr.com
>> Unsubscribe or change your options at
More information about the Mailman-Users