Bug 193550

Summary: Error when fetching articles from nntp.perl.org, other newsgroups are fine though
Product: knode Reporter: Adam Jimerson <vendion>
Component: generalAssignee: kdepim bugs <kdepim-bugs>
Status: RESOLVED FIXED    
Severity: normal    
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: unspecified   
OS: Linux   
Latest Commit: Version Fixed In:
Attachments: Screenshot of the error

Description Adam Jimerson 2009-05-21 20:44:32 UTC
Version:           0.99.01 (using 4.2.3 (KDE 4.2.3) "release 1", KDE:42 / openSUSE_11.1)
Compiler:          gcc
OS:                Linux (x86_64) release 2.6.27.21-0.1-default

With Knode 4.2.3 while trying to read any article from
nntp.perl.org I get an error but Knode is able to fetch the headers, but other
newsgroups such as forums.novell.com and news.mozilla.org work fine.  The
problem is still there after removing ~/.kde4/share/config/rcknode and removing
the entire directory of ~/.kde4/share/apps/knode.  Also this problem only
happens with Knode using Seamonkey it can retrieve the message without any
problems.

Reproducible: Always

Steps to Reproduce:
1. Add the nntp.perl.org server
2. Subscribe to a list
3. Try to fetch an article
Actual Results:  
Knode error screen

Expected Results:  
The selected article

Screenshot of the error will be provided
Comment 1 Adam Jimerson 2009-05-21 20:46:10 UTC
Created attachment 33904 [details]
Screenshot of the error
Comment 2 Olivier Trichet 2009-07-01 14:17:36 UTC
SVN commit 990006 by otrichet:

By default, fetch articles using their server-side Id instead of their msg-id.

It was the behaviour back in KDE3.
Work around broken nntp.perl.org server.
BUG: 193550

 M  +10 -1     nntpjobs.cpp  


WebSVN link: http://websvn.kde.org/?view=rev&revision=990006
Comment 3 Stephan Binner 2009-09-22 18:42:39 UTC
Any reason that this fix hasn't been backported to 4.3 branch?
Comment 4 Olivier Trichet 2009-09-27 19:47:42 UTC
> --- Comment #3 from Stephan Binner <binner kde org>  2009-09-22 18:42:39
>  --- Any reason that this fix hasn't been backported to 4.3 branch?

None, but lack of time.
If you have the time to recompile the whole 4.3 stack to test the backport, 
feel free to do it.