>>>>> "Santiago" == Santiago Vila <[EMAIL PROTECTED]> writes:
>> Note 4: To the best of my knowledge mbox mails should be split on the
>> "From " header, and what headers follow is completely irrelevant and
>> should not even be considered.
Santiago> That would be a possible way of doing it, yes, but apparently the
Santiago> author didn't consider that to be reliable in the general case
and at
Santiago> least *two* known headers are required.
Santiago> You can get the desired behaviour by using "formail -m 1 -s", so
I'm
Santiago> going to consider this report as a request to add User-Agent and
Santiago> NNTP-Posting-Date to the list of recognized headers, which is in
Santiago> src/header.h in the source code.
Hmmmm. I am not sure I agree with the upstream author... These are
standard mbox files, and my understanding is that any line prefixed
with "From " starts a new message. I think other programs like mutt do
too, being inconsistent is confusing.
However, I do agree with your solution.
I am not in a position (time-wise) to test out the patch, but I can't
imagine any problems.
My only other comment is the man page be updated to highlight the -m option:
--- cut ---
In the tradition of UN*X utilities, formail will do exactly what you
ask it to, even if it results in a non-RFC822 compliant message. In
particular, formail will let you generate header fields whose name ends
in a space instead of a colon. While this is correct for the leading
`From ' line, that line is not a header field so much as the message
separator for the mbox mailbox format. Multiple occurrences of such a
line or any other colonless header field will be considered by many
mail programs, including formail itself, as the beginning of a new mes-
sage. Others will consider the message to be corrupt. Because of
this, you should not use the -i option with the `From ' line as the re-
sulting renamed line, `Old-From ', will probably not do what you want
it to. If you want to save the original `From ' line, rename it with
the -R option to a legal header field such as `X-From_:'.
--- cut ---
In particular, the sentence "Multiple occurrences of such a line or
any other colonless header field will be considered by many mail
programs, including formail itself, as the beginning of a new mes-
sage." seems wrong, and based on the assumption that -m1 is used.
Thanks.
--
Brian May <[EMAIL PROTECTED]>
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
