(*** This bug was imported into bugs.kde.org ***) Package: knode Version: 0.4 (using KDE 2.2.2 ) Severity: normal Installed from: Debian testing/unstable Packages Compiler: 2.95.4 OS: Linux OS/Compiler notes: Debian Package knode 4:2.1.1-7 If you post an article with subject with umlauts or other 8Bit chars Knode simply uses _one big_ encoded word starting with the first word with an Umlaut. eg: Subject: =?ISO-8859-1?Q?=D6sterreich_aalt_sich_und_trinkt_massenweise_Sonnen=F6l_b=FCs_es_=FChnen_schlecht_wird=2E? If the Subject is long enough this violates rfc2047 ---------------------------- 2. Syntax of encoded-words [...] An 'encoded-word' may not be more than 75 characters long including 'charset' 'encoding' 'encoded-text' and delimiters. If it is desirable to encode more text than will fit in an 'encoded-word' of 75 characters multiple 'encoded-word's (separated by CRLF SPACE) may be used. ---------------------------- This Bug seems to be still present in Knode 0.6 cu andreas References: Newsgroups: at.test Message-ID: <3c67cb33$0$32508$3b214f66@news.univie.ac.at> Newsgroups: ger.pc.linux Message-ID: <3c6538f0$1@news03.heise.de> (Submitted via bugs.kde.org)
The last update to this bug report was many months ago. Can you please give us an updated on whether this is still a problem for you with a more recent version of knode? If it is not a problem - the status of this bug report will be changed to closed. If it is still a problem can you please tell me how to add an Umlaut with a english kerboard ? :-)
Subject: Re: violates rfc2047: uses too long encoded words. On Wed, Sep 25, 2002 at 01:48:32AM -0000, Cp Hennessy wrote: > The last update to this bug report was many months ago. Can you > please give us an updated on whether this is still a problem for you > with a more recent version of knode? I can crosstest with KDE 3.0.0 (shipped with RedHat 3.0), but fixing this properly would have required _some_ work - I do not think it would have gone unnoticed. BTW I now think this is a cosmetical problem, feel free to downgrade it to wishlist. > If it is not a problem - the status of this bug report will be > changed to closed. > If it is still a problem can you please tell me how to add an Umlaut > with a english kerboard ? :-) I have not got an English keyboard, but there are some possibilties: * Copy&paste from the manpage iso_8859_1(7) * --------"------ a webpage containing 'ü' displayed in konqueror * Using the Compose-key with " and o. ------------------------------------------- If you really have time to spare or know some MIME+KDE-guru please take a shot at #42576 - This is a real showstopper, knode 0.7.1 sometimes sends out postings with 8-Bit characters and wrongly declares them as Content-Type: text/plain; charset=ascii Content-Transfer-Encoding: 7bit I know the bugreport is not written very well, the problem is that the bug seems to be hard to reproduce, while reading de.comp.os.unix.linux.* I regularily find such postings (iirc about two or three a day) - but there seems to be no pattern, the next article from the same author is ok. Of 953 articles from knode 0.7.1 in my local newsspool of de.comp.os.unix.linux.* 48 articles are broken. ------------------------------------------- cu andreas
Confirmed with knode 0.7.1 from RedHat 7.3 <3d9181d3$0$9620$3b214f66@news.univie.ac.at>.
Sorry Andreas, but when you say it is "confirmed", do you mean that it is still a problem with 0.7.1 ? CPH
Subject: Re: violates rfc2047: uses too long encoded words. On Mon, Sep 30, 2002 at 01:00:15AM -0000, Cp Hennessy wrote: > Sorry Andreas, but when you say it is "confirmed", do you mean that it is > still a problem with 0.7.1 ? Yes I do, I've tested with 0.7.1 and the bug is still there. Sorry if my message was unclear. thanks, cu andreas
This seems to be fixed, at least in KNode 0.9.1.
Please reopen. Problem still exist with 0.9.1 Newsgroups: de.comm.software.newsreader Subject: Re: Sonderzeichen im Subject (was: Desktpohintergrung zeigt =?UTF-8?B?IllPVbRSRSBJTiBEQU5HRVIiIGFuLi4uLnZpcnVzPyBiZWhlYnVuZ3Nt9mdsaWNoa2VpdD8p?= Date: Thu, 07 Jul 2005 17:39:56 +0200 Organization: =?UTF-8?B?Xy3Cry1f?= Lines: 24 Message-ID: <6305902.NMoXrKNfn2@m-id.message-center.info> =?UTF-8?B?IllPVbRSRSBJTiBEQU5HRVIiIGFuLi4uLnZpcnVzPyBiZWhlYnVuZ3Nt9mdsaWNoa2VpdD8p?= is longer than the allowed 76 chars (it is 85 chars). Further, there's no folding done at all, making the line too long.
This header line violates another part of 2047: | 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. The line is longer than 76 chars.
This bug is STILL present in KNode/0.9.1. Please fix it! Pine does *not* decode Subjects that are longer than 75 bytes.