https://bugs.kde.org/show_bug.cgi?id=312391

            Bug ID: 312391
           Summary: Reference line is too long in deeply nested threads
    Classification: Unclassified
           Product: knode
           Version: 4.9
          Hardware: Fedora RPMs
                OS: Linux
            Status: UNCONFIRMED
          Severity: major
          Priority: NOR
         Component: general
          Assignee: kdepim-bugs@kde.org
          Reporter: bugs.kde....@philippgampe.info

If you reply to a message inside deeply nested thead, then the Reference header
lines gets too long and the server refuses the message.

Reproducible: Always

Steps to Reproduce:
1. Replay to deeply nested thread

Actual Results:  
Message refuses the server and Knode displays an error message. The message is
refused with "441 437 Too long line in header 1030 bytes", because the
References line is not truncated.

Expected Results:  
Message is send to server. The references line is truncated.

Knode does not forwards the actual error message from the server, but talks
about an error and a possible readonly group.

Sample message (wireshark dump):
-------------------8<---------
POST
340 Ok, recommended ID <kbptvj$5jm$2...@srv102.typo3.org>
Content-Type: text/plain; charset="UTF-8"
From: Philipp Gampe <philipp.ga...@typo3.org>
Organization: TYPO3
Date: Sun, 30 Dec 2012 18:33:35 +0100
Content-Transfer-Encoding: 8Bit
Subject: Re: [TYPO3-english] Last TYPO3 version without fluid/extbase
Newsgroups: typo3.english
References: <mailman.8386.1352882684.598.typo3-engl...@lists.typo3.org>
<mailman.1.1353018225.10201.typo3-engl...@lists.typo3.org>
<mailman.8626.1353030564.598.typo3-engl...@lists.typo3.org>
<mailman.8627.1353033858.598.typo3-engl...@lists.typo3.org>
<mailman.8652.1353059722.598.typo3-engl...@lists.typo3.org>
<mailman.8654.1353060452.598.typo3-engl...@lists.typo3.org>
<mailman.8684.1353070904.598.typo3-engl...@lists.typo3.org>
<mailman.8690.1353074686.598.typo3-engl...@lists.typo3.org>
<mailman.8700.1353079053.598.typo3-engl...@lists.typo3.org>
<mailman.1.1353081383.5142.typo3-engl...@lists.typo3.org>
<mailman.8705.1353082070.598.typo3-engl...@lists.typo3.org>
<mailman.1.1353090499.29365.typo3-engl...@lists.typo3.org>
<mailman.12350.1356109700.598.typo3-engl...@lists.typo3.org>
<mailman.1.1356110532.31435.typo3-engl...@lists.typo3.org>
<mailman.12396.1356208499.598.typo3-engl...@lists.typo3.org>
<mailman.1.1356281650.29430.typo3-engl...@lists.typo3.org>
<mailman.12444.1356298271.598.typo3-engl...@lists.typo3.org>
Lines: 16
MIME-Version: 1.0

Hi Tonix (Antonio Nati),

Tonix (Antonio Nati) wrote:

> Look in google for the patch called chkuser (and chkusr). It is saving
> thousands of qmail installations.
> It has been installed in dozens (if not hundreds) of thousands servers
> running qmail.

Test mail ... ignored it ... it is to reproduce a Knode bug.

Happy new year
-- 
Philipp Gampe ... PGP-Key 0AD96065 ... TYPO3 UG Bonn/K..ln
Documentation ... linkvalidator
TYPO3 .... inspiring people to share!

.
441 437 Too long line in header 1030 bytes
---------------------------8<--------------------------

I manually edited the message in the outbox mbox file and deleted the first two
references. Then I could send the mail. However I do not think is is an
acceptable workaround and deeply nested threads should not be that uncommon.

The news server is lists.typo3.org (aka srv102.typo3.org).

-- 
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Kdepim-bugs mailing list
Kdepim-bugs@kde.org
https://mail.kde.org/mailman/listinfo/kdepim-bugs

Reply via email to