Re: [Mailman-Users] RE;Cron/senddigests bug

2003-02-06 Thread Barry A. Warsaw
> "DP" == Dan Phillips <[EMAIL PROTECTED]> writes: DP> Tried that and it reported no problems. The problem definitely DP> seems to be in digest.mbox, although I can't see anything DP> wrong. If it isn't too late, can you submit a bug report with the mbox file attached? If you do

Re: [Mailman-Users] RE;Cron/senddigests bug

2003-02-02 Thread Tokio Kikuchi
Dan, 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 rfc115

Re: [Mailman-Users] RE;Cron/senddigests bug

2003-02-02 Thread Dan Phillips
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 probl

Re: [Mailman-Users] RE;Cron/senddigests bug

2003-02-02 Thread Jon Carnes
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

[Mailman-Users] RE;Cron/senddigests bug

2003-02-02 Thread Dan Phillips
Tried that and it reported no problems. The problem definitely seems to 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