Bug 33036

Summary:	Lost artikles with delaybody
Product:	[Unmaintained] knode	Reporter:	Unknown <null>
Component:	general	Assignee:	kdepim bugs <kdepim-bugs>
Status:	RESOLVED UNMAINTAINED
Severity:	normal
Priority:	NOR
Version:	0.6.1
Target Milestone:	---
Platform:	Unlisted Binaries
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description fnoack 2001-09-27 20:16:42 UTC

(*** This bug was imported into bugs.kde.org ***)

Package:           knode
Version:           0.6.1 (using KDE 2.2.1 )
Severity:          normal
Installed from:    Unspecified Linux
Compiler:          Not Specified
OS:                Linux
OS/Compiler notes: Not Specified

knode dont display artikels correct if leafnode is configured with delaybody=1. leafnode saves the later loadet body under an other number then the header but knode serches for the number of the header. 

(Submitted via bugs.kde.org)

Comment 1 Kim Neunert 2001-12-13 13:11:27 UTC

Hello !

It seems that I have the same bug ! 
Systeminformations:
Suse 7.3
Linux Kernel: 2.4.10
KDE 2.2.1 
Knode 0.6.1
leafnode 1.9.19

Nothing is compiled by myself everything are RPMs of my Distribution !

regards

Kim Neunert

Comment 2 L Epperlein 2002-01-11 21:06:47 UTC

knode looks for the Xref: header set by leafnode. After fetching the news
via fetchnews all old articles have got a new Xref: header with a new
number so that knode can't get it from the news server leafnode.

Why doesn't use knode the message ID? This should stay consistent.

-- 


GMX - Die Kommunikationsplattform im Internet.
http://www.gmx.net

Comment 3 Cp Hennessy 2002-09-25 02:43:03 UTC

  
Can you please give us an updated on whether this is still a problem for either of you   
with a more recent version of knode?

Comment 4 peter_s_d 2002-11-20 05:02:39 UTC

Knode 0.7.1 and Leafnode 1.9.25.rel misbehave when delaybody=1. 
 
SuSE 7.0 
KDE 3.0.4 
kernel 2.2.19

Comment 5 peter_s_d 2003-10-16 05:11:21 UTC

Knode now works with the leafnode option of delaybody=1 if the new 
leafnode option of delaybody_in_situ=1 is set int /etc/leafnode/config

I am using;
leafnode-1.9.41-1mdk
Knode 0.7.2
KDE 3.1.4
Mandrake cooker

Comment 6 Rainer Endres 2004-04-05 12:26:53 UTC

Is it reasonable to close this bug as FIXED? or as WONTFIX?


	Rainer

Comment 7 Roberto Selbach 2004-04-05 15:11:59 UTC

Neither. I will fix it. There is a workaround for now, though.

Besides setting delaybody=1 in Leafnode's configuration, also set the option below:

    delaybody_in_situ = 1

Then go to Settings -> Configure KNode -> Reading News -> Memory Consumption and set the "Cache size for articles" to 0KB. That should do it.

Comment 8 Stephan Kulow 2004-05-19 12:03:59 UTC

Replaced fnoack@t-online.de with null@kde.org due to bounces by reporter

Comment 9 Andrew Crouthamel 2018-09-04 18:34:36 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.