> Well, the mailbox is not valid. The reason appears to be that antispam.rc > has truncated the mailbox in an invalid way. Namely, the multipart > boundaries have been ignored, so that the ending for: > > ----=_NextPart_000_0008_01C684B1.30F8FE30 > > Is no longer there.
Ah yes, good point. ;) > I assume that pine and mutt are doing my previous incorrect behavior. (I > just checked with pine, and it breaks the email even if I put the ending > boundary marker *after* the next email.) No. Mutt uses content-length: when it exists, which fixes all the problems for separating messages, and allows trivially to not scan any msg past its end without incurring a performance penalty for scanning to the end of the mbox file. It also doesn't trip up on un-escaped "^From ". Pine ITA is politically anal and doesn't work either. Is the RFC written for mbox files, or does it implicitly assume you know when to stop looking when you reach EOF? > - If a "^From " appears Is it possible this should be "\n\nFrom " (unless at BOF)? I.e. preceeding empty line is required? Thanks + greetings, Volker -- Volker Kuhlmann <[EMAIL PROTECTED]>, http://volker.dnsalias.net/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
