Hi Ken,
> You'd have to deal with a header that would take up a lot of space.
Vertically? Otherwise "<foo> <bar>" and "<foo>\n <bar>" isn't a lot
different.
> Also, if you want 'nice' formatting, you need something smarter that
> knows about the length of the header (like what formataddr does).
> Really, I think you could adapt most of the formataddr code, except
> for splitting at commas. It may be that my concerns about "nice"
> header formatting are not worthwhile.
Things that might complicate the code... I've come across Reference
headers in the past where the message IDs have been truncated by
something so they're '<foo@ba'. Not everything in the References header
is necessarily a simple message ID, e.g.
To: [email protected]
From: Paul Fox <[email protected]>
In-reply-to: <[email protected]>
(sfid-20140323_063434_994284_B0C77B71)
References: <[email protected]>
<[email protected]>
(sfid-20140323_063434_994284_B0C77B71)
Message-Id: <[email protected]>
Subject: Re: [Nmh-workers] mhshow flag: -combined ?
Date: Sun, 23 Mar 2014 15:01:21 -0400
I guess those "sfid"s are comments and legally OK?
--
Cheers, Ralph.
https://plus.google.com/+RalphCorderoy
_______________________________________________
Nmh-workers mailing list
[email protected]
https://lists.nongnu.org/mailman/listinfo/nmh-workers
