[Mailman-Developers] digest problems (anyone seen this?)

[Chuq Von Rospach]

Hey, all. Anyone else run into this? I'm getting corrupted digests.

> Today's Topics:
>
>    1. Re: Trade Rumor! (CA94NHL at aol.com)
>    2. Re: Trade Rumor! (Yvonne Smead)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Tue, 5 Aug 2003 17:03:32 EDT
>

[stuff deleted]

>
> Message: 2
> Date: Tue, 5 Aug 2003 14:21:44 -0700
> From: xxx
> Subject: Re: Trade Rumor!
>

[stuff deleted]

>
> Sharks aren't gonna let go of Marco either with the about-to-happen new
> influx of Germans!From simutis at tsoft.com Tue Aug  5 17:08:27 2003
> Received: from mail0.rawbw.com (mail0.rawbw.com [198.144.192.41])
> 	by plaidworks.com (8.12.9/8.12.9) with ESMTP id h7608Cvj012823
> 	for <sharks at plaidworks.com>; Tue, 5 Aug 2003 17:08:13 -0700 (PDT)
> Received: from tsoft.com (m208-174.dsl.rawbw.com [198.144.208.174])
> 	by mail0.rawbw.com (8.11.6p2/8.11.6) with ESMTP id h7608AD87787
> 	for <sharks at plaidworks.com>; Tue, 5 Aug 2003 17:08:10 -0700 (PDT)
> Date: Tue, 5 Aug 2003 17:09:05 -0700
> Content-Type: text/plain; charset=WINDOWS-1252; format=flowed
> Mime-Version: 1.0 (Apple Message framework v552)
> From: xxxx
> To: sharks at plaidworks.com
> In-Reply-To: <200308052035.h75KZEde009556 at plaidworks.com>
> Message-Id: <31757AF5-C7A2-11D7-B5A7-00039390D592 at tsoft.com>
> X-Mailer: Apple Mail (2.552)
> Content-Transfer-Encoding: 8bit
> X-MIME-Autoconverted: from quoted-printable to 8bit by plaidworks.com 
> id
> 	h7608Cvj012823
> Subject: Re: migratory moose
> X-BeenThere: sharks at plaidworks.com
>

It seems that some messages aren't written to the digest mbox properly 
(I *think* the routine assumes the message ends with a blank line, and 
if it doesn't, the digester can't handle the mbox properly -- but I 
haven't proven that yet). It's always the same small set of users 
e-mail that causes this, so it's clearly something about their 
messages, but since I can only see stuff after it's converted to mbox, 
it's hard to tell (but whatever procmail does for local delivery fixes 
this, while Mailman doesn't)

Any thoughts? I've been told by users this has been going on since I 
upgraded to 2.1, but in all honesty, I just noticed...