[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [bug-mailutils] Unfolding header value
From: |
Sergey Poznyakoff |
Subject: |
Re: [bug-mailutils] Unfolding header value |
Date: |
Wed, 02 Jul 2003 19:33:18 +0300 |
Bonjour Alain,
> (1) in this case:
> Received: [...]
> What should header_get_value return ?
Hmm, I guess it should return unfolded strings. By the way, I've got
an interesting obsevation:
$ mail
1 "Alexander E. Pat Sat Jun 28 14:46 [bug-inetutils] [BUG] talk (part of i
& p
[...]
& h
1 "Alexander E. Pat Sat Jun 28 14:46 [bug-inetutils] [BUG]
talk (part of i
Notice newline after [BUG] in the 'h' output. That's because
the first listing was produced right after scanning the mailbox,
and mboxscan.c *always unfolds* the header values. The 'h' command
involved getting the header_t structure, filling in its blurb, etc.,
and the functions from header.c *do not* unfold any headers. Thus,
we have an inconsistency between the different parts of the library...
> (2) header_get_value() is also used in imap4d etc ... to return header field
> values.
> If we fold and collapse headers, how to unfold and unduplicate(see the
> "Received:" case)
I believe it is not that critical. The newlines may be inserted at
every whitespace character. For several headers (like Received), we may
implement the widely accepted ways of folding.
> (3) maybe an approach is to add new methods/API to header_t to
> handle the cases.
That's possible too.
Regards,
Sergey