Re: [bug-mailutils] Unfolding header value

[Alain Magloire]

> 
> Hi Sergey,
> 
> On Fri, Jun 20, 2003 at 11:31:55AM +0300, Sergey Poznyakoff wrote:
> > Hi Kidong,
> > 
> > > According to RFC2822, header_get_value() and header_aget_value()
> > > should unfold the value, shouldn't it?
> > 
> > You are right, it should. Are you going to implement it? 
> > 
> 
> I took a look at above function, but it's a little bit complicate
> for me to understand. I think it's better that there's a "big picture"
> describing internal of mailutils.
> I'll fix it when I'll have spare time but don't know when I will do. =)
> I don't care for someone to fix it before me.
> 

In general, what is the best policy?

(1) in this case:

 Received: from hub.ott.qnx.com (address@hidden [192.168.2.2]) by 
smtp.ott.qnx.com (8.8.8/8.6.12) with ESMTP id LAA10830 for <address@hidden>; 
Fri, 13 Sep 2002 11:56:09 -0400
 Received: from luna.pizzashack.org (h52544c185a20.ne.client2.attbi.com 
[24.147.42.69])
        by hub.ott.qnx.com (8.9.3/8.9.3) with ESMTP id LAA15686
        for <address@hidden>; Fri, 13 Sep 2002 11:55:21 -0400
 Received: (from address@hidden)
        by luna.pizzashack.org (8.11.6/8.11.2) id g8DFuj220932;
        Fri, 13 Sep 2002 11:56:45 -0400

What should header_get_value return ?

(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)

(3) maybe an approach is to add new methods/API to header_t to handle the cases.

What solution would make things easier in dealing with your problem ?