On Sun, Mar 24, 2013 at 02:29:09PM -0500, Will Fiveash wrote: > On Sun, Mar 24, 2013 at 06:48:25PM +0000, Chris Green wrote: > > On Sun, Mar 24, 2013 at 11:09:31AM +0000, James Griffin wrote: > > > > > > It looks as though your python delivery program might be doing this? > > > Have you tried taking the python program out of the process to test, to > > > see if the messages are being appended to the mbox correctly? I know > > > you've looked at it again and maybe made some changes to it. > > > > > How could the python delivery program have anything to do with it? > > > > I simply s[aved] three messages using the mutt save command, no other > > program is involved, mutt is simply writing three messages to the same > > mbox. > > > > Are you all sure that mutt isn't simply saving what it's provided with > > by the incoming MDA? > > > > If the *delivered* message ends with a blank line (i.e. what's in the > > inbox) then what mutt saves will end with a blank line. > > > > To do exactly what I did:- > > > > Deliver some messages to a mbox file. > > > > Check that there is *no* blank line at the end of these messages. > > > > Use mutt to s[ave] (or c[opy]) the messages to another mbox. > > > > Look at the new mbox file. > > > > I think you'll find there's no added blank line. > > When I use the mutt (on Solaris 11) copy function to copy three messages > in an existing mbox file to an new mbox file I see a blank line before > each new message's "From " line except for the first message. Maybe > it's time to break out the debugging tools on your end? > Yes, but did you look in the "existing mbox file" to see if there were blank lines betweeen the messages there?
-- Chris Green
