Bug 108746 - Long header lines are not folded
Summary: Long header lines are not folded
Status: RESOLVED UNMAINTAINED
Alias: None
Product: knode
Classification: Miscellaneous
Component: general (show other bugs)
Version: 0.9.1
Platform: Gentoo Packages Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-07-08 11:51 UTC by Alexander Skwar
Modified: 2018-09-04 18:38 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments
Article with a too long header line (974 bytes, text/plain)
2005-07-08 11:58 UTC, Alexander Skwar
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Alexander Skwar 2005-07-08 11:51:31 UTC
Version:           0.9.1 (using KDE KDE 3.4.1)
Installed from:    Gentoo Packages
OS:                Linux

rfc2047 states:

|   While there is no limit to the length of a multiple-line header
|   field, each line of a header field that contains one or more
|   'encoded-word's is limited to 76 characters.

Articles posted with Knode 0.9.1 do not follow that rule. I'll attach an article showing this misbehaviour. <news:2108432.r8JuzgESjG@work.message-center.info>
Comment 1 Alexander Skwar 2005-07-08 11:57:05 UTC
Oh, the KDE bugzilla doesn't have an attachment feature :)

http://stuff.alexander.skwar.name/knode.too-long-header.eml

Subject: no reply - ignore - long header line with a lot more than 80 characters. because of this, the subject header line must be folded. but sadly, knode 0.9.1 does not seem to do that...

The subject is just one very long line.
Comment 2 Alexander Skwar 2005-07-08 11:58:31 UTC
Created attachment 11717 [details]
Article with a too long header line

Gosh, I'm so blind... There is an attachment feature....

In this attachment, you'll find a post done with 0.9.1 showing a way too long
header line (subject).
Comment 3 Andrew Crouthamel 2018-09-04 18:38:49 UTC
Hello! Sorry to be the bearer of bad news, but this project has been unmaintained for many years so I am closing this bug.