Bug 221644 - references header line is too long
Summary: references header line is too long
Status: RESOLVED DUPLICATE of bug 187345
Alias: None
Product: knode
Classification: Miscellaneous
Component: general (show other bugs)
Version: unspecified
Platform: unspecified Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-01-07 13:41 UTC by peter_s_d
Modified: 2010-01-23 20:53 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description peter_s_d 2010-01-07 13:41:19 UTC
Version:           0.99.01 (using 4.2.4 (KDE 4.2.4), Mandriva Linux release 2009.1 (Official) for i586)
Compiler:          gcc
OS:                Linux (i686) release 2.6.29.6-3mnbcustom

When replying to a very deeply nested thread the references header line can grow to an unacceptable length.  

Knode does not seem to have any configuration or editing capability to trim that line.  

Here is a cut and paste from a post about the problem...  

On Mon, 04 Jan 2010, in the Usenet newsgroup alt.os.linux.mandriva, in article
<l5g817-nr.ln1@psd.motzarella.org>, Peter D. wrote:

>I just tried to post a wise-crack to that venerable thread,
>"Re: OT: Time Zones and Medicine" with knode via LeafNode and
>Eternal September.

>It seems that Eternal September objects to very long headers.
>The references line is several hundred characters long.

Are you sure it's Eternal September and not your news tool[s]?

RFC 5536 Section 2.2   page 9

   o  Compliant software MUST NOT generate (but MAY accept) header field
      lines of more than 998 octets.

RFC 5322 Section 2.2.3

RFC 2822 Section 2.2.3

>What is the standard way to deal with this?

If your news tool is generating headers longer than 998 octets (about
12 1/2 "80 character" lines), file a bug report.  If your news tool is
barfing over the long header, edit the header and delete _one_ of the
reference message IDs - perhaps the second, third, or fourth message
ID.  Once you look at the format of that header, it should be obvious.

        Old guy
Comment 1 Olivier Trichet 2010-01-23 20:53:26 UTC

*** This bug has been marked as a duplicate of bug 187345 ***