On Tue, 29 Aug 2006, Andy Spiegl wrote:
> > Well, formail was never designed to do the kind of miracles you expect
> > from it, so this is not really a bug. The algorithm to split messages
> > expects *known* header fields (which KFrom: is not). See src/header.h
> > in the source code to see what I mean.
>
> Okay, but I don't think I expected miracles. :-)
> But it is not logical that formail chokes on an unknown header
> only in the first line. It doesn't seem to mind it at any other place in
> the mail. Doesn't that sound like a bug?
> And if it's so fault tolerant why can't it be with the first line?
Because it expects (by default) two consecutive known headers before
it decides it found the start of a new email message.
Try "formail -m 1". From the manpage:
-m minfields
Allows you to specify the number of consecutive headerfields for-
mail needs to find before it decides it found the start of a new
message, it defaults to 2.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
