Version: 0.7.6 (using KDE 3.1.9) Compiler: gcc version 3.3.1 20030626 (Debian prerelease) OS: Linux (i686) release 2.2.20 I posted a mail with long syslog excepts, and an attachment, to gmane.linux.kernel (GMane is a NNTP gateway for thousands of mailing lists, see www.gmane.org). When I wanted to post, KNode complained that the post contained wrong characters for the specified charset, and I was supposed to specify another one. (why? I set this to "auto" because I DIDN'T want to keep saying what charset I want!) The post then appeared in my "sent_3.mbox" file (in knode's config directory underneath $KDEHOME) and in the mailing list with quoted-printable encoding, but NOT the appropriate headers (so that other mail software could not view this properly). Also, when sending it got truncated (which I suppose was done by the receiving mailserver, maybe because of the wrong encoding, I don't know). From aaa@aaa Mon Jan 01 00:00:00 1997 X-KNode-Overview: Re: Linux 2.4.22-rc2 gmane.linux.kernel 3031 Message-Id: <bh8vv8$3qc$1@sea.gmane.org> From: Jens Benecke <usenet@jensbenecke.de> Subject: Re: Linux 2.4.22-rc2 Newsgroups: gmane.linux.kernel Date: Mon, 11 Aug 2003 22:57:21 +0200 References: <Pine.LNX.4.44.0308081751390.10734-100000@logos.cnet> Lines: 3031 User-Agent: KNode/0.7.6 MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="nextPart1474120.dtPh4Wnd94" Content-Transfer-Encoding: 7Bit X-No-Archive: Yes --nextPart1474120.dtPh4Wnd94 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7Bit Marcelo Tosatti wrote: > Here goes release candidate 2. > It contains yet another bunch of important fixes, detailed below. > Nice weekend for all of you! I'm having problems. had them with -pre10 as well, posted here, but th= ey somehow didn't appear in the list. Here's the short story: No network (3c509) because the card gets IRQ 22= (or something) and doesn't like it, no USB, no firewire, no X11 (yeah, shou= ld have recompiled the NVIDIA drivers, duh), and a total crash on shutdown= truncated here. I guess because the next line was a single dot on a line and thus got misinterpreted by the mail server (which should be prevented by proper encoding - at least I would expect this). my knoderc settings for posting news: [POSTNEWS] 8BitEncoding=false Att_Headers=115,91,55,110,60 Att_Splitter=595,91 Charset=iso-8859-1 ComposerCharsets=us-ascii,utf-8,iso-8859-1,iso-8859-2,iso-8859-3,iso-8859-4,iso-8859-5,iso-8859-6,iso-8859-7,iso-8859-8,iso-88 Intro=%NAME wrote: MIdhost= UseOwnCharset=false appSig=true cursorOnTop=false dontIncludeUA=false externalEditor=kwrite %f generateMId=false incSig=false maxLength=76 rewrap=true useExternalEditor=false useExternalMailer=false wordWrap=true Please have a look into this. Thank you!
The BTS has a B. :-) It cuts mails when "From ..." in one line is encountered. Here's the rest of the post, with a mangled "From" line: From aaa@aaa Mon Jan 01 00:00:00 1997 X-KNode-Overview: Re: Linux 2.4.22-rc2 gmane.linux.kernel 3031 Message-Id: <bh8vv8$3qc$1@sea.gmane.org> From: Jens Benecke <usenet@jensbenecke.de> Subject: Re: Linux 2.4.22-rc2 Newsgroups: gmane.linux.kernel Date: Mon, 11 Aug 2003 22:57:21 +0200 References: <Pine.LNX.4.44.0308081751390.10734-100000@logos.cnet> Lines: 3031 User-Agent: KNode/0.7.6 MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="nextPart1474120.dtPh4Wnd94" Content-Transfer-Encoding: 7Bit X-No-Archive: Yes --nextPart1474120.dtPh4Wnd94 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7Bit Marcelo Tosatti wrote: > Here goes release candidate 2. > It contains yet another bunch of important fixes, detailed below. > Nice weekend for all of you! I'm having problems. had them with -pre10 as well, posted here, but th= ey somehow didn't appear in the list. Here's the short story: No network (3c509) because the card gets IRQ 22= (or something) and doesn't like it, no USB, no firewire, no X11 (yeah, shou= ld have recompiled the NVIDIA drivers, duh), and a total crash on shutdown= truncated here. I guess because the next line was a single dot on a line and thus got misinterpreted by the mail server (which should be prevented by proper encoding - at least I would expect this). my knoderc settings for posting news: [POSTNEWS] 8BitEncoding=false Att_Headers=115,91,55,110,60 Att_Splitter=595,91 Charset=iso-8859-1 ComposerCharsets=us-ascii,utf-8,iso-8859-1,iso-8859-2,iso-8859-3,iso-8859-4,iso-8859-5,iso-8859-6,iso-8859-7,iso-8859-8,iso-88 Intro=%NAME wrote: MIdhost= UseOwnCharset=false appSig=true cursorOnTop=false dontIncludeUA=false externalEditor=kwrite %f generateMId=false incSig=false maxLength=76 rewrap=true useExternalEditor=false useExternalMailer=false wordWrap=true Please have a look into this. Thank you!
Additional info: If you post via quoted printable with KNode, and you have a dot "." as the last character in one line which _just_ exceeds the colum limit, then KNode will wrap this dot, leading to a single dot on one line, which usually means "END of communication" for mail servers. I.E. YOUR MAIL WILL BE TRUNCATED! This can't be a feature :-) One example: You write: Here's the short story: No network (3c509) because the card gets IRQ 22 (or something) and doesn't like it, no USB, no firewire, no X11 (yeah, should have recompiled the NVIDIA drivers, duh), and a total crash on shutdown. KNode generates: Here's the short story: No network (3c509) because the card gets IRQ 22= (or something) and doesn't like it, no USB, no firewire, no X11 (yeah, shou= ld have recompiled the NVIDIA drivers, duh), and a total crash on shutdown= . The last dot means that any NNTP->Mail gateway will TRUNCATE your mail. Please fix this =;) Thank you!
Did anybody EVER look at this?
Hi, can this bug be closed as RESOLVED, or WONTFIX? (I'd prefer the first ;) Thank you!
Hello! Sorry to be the bearer of bad news, but this project has been unmaintained for many years so I am closing this bug.