KNode
/ KNode Home / FAQ
Learn
 What is KNode?
 FAQ
 Documentation
 Screenshots
 People

Download
 Stable Version
 Development Version

Develop
 Changelog
 Roadmap
 Bug Reports

Contact
 Contacts
 Mailing Lists

SourceForge Logo
Valid XHTML 1.0!

Frequently asked questions

  1. General questions
    1. Can I use KNode as an offline newsreader?
    2. Can I run KNode without running KDE ?
    3. Do I need to update to KDE2 to run KNode?
    4. Suddenly KNode crashes on accessing some newsgroup(s).
  2. Questions about KNode 0.6
    1. KNode doesn't remember the colorize-rules after a restart.
    2. Rule editor: How can I say that the rule is for all groups? Wildcard (*) doesn't work.
    3. Articles are not sorted correctly by date.
  3. Questions about KNode 0.3.2
    1. KNode crashes frequently on Caldera Open Linux 2.4
    2. KNode doesn't remember the window size and position
    3. In some newsgroups the article list shows a lot of questionmarks instead of the real characters.
    4. Sending mails doesn't work at all.
    5. What does "501 FROM my-email-address invalid source route address syntax" mean?
    6. Why are my articles duplicated?

General questions

1.1 Can I use KNode as an offline newsreader?
Not yet. Offline support will be eventually added in a later release. Until then we recommend to use a local newsserver like Leafnode. This solution has some advantages, especially in multi-user environments.

1.2 Can I run KNode without running KDE ?
Sure. Just install Qt, kdesupport and kdelibs, and launch KNode from your favourite window manager.

1.3 Do I need to update to KDE2 to run KNode?
All current versions of KNode require KDE2, but you can find the last version for KDE1 (0.1.13) in the download section.

1.4 Suddenly KNode crashes on accessing some newsgroup(s). If I start KNode in a xterm it says "KNGroup::updateThreadInfo() : Found broken threading infos! Restoring ..." right before the crash. What can I do about this?
This error is caused by some corrupted data-files. Normally these are restored automatically but some times this doesn't work very well ;-) If you run in such a problem, the only solution ist to unsubcribe from the broken groups and then re-subscribe to them. We are working on a better solution though.

Questions about KNode 0.6

2.1 KNode doesn't remember the colorize-rules after a restart.
This is a known issue.
A work around is to run "recalculate scores" in the scoring menu after a restart.

2.2 Rule editor: How can I say that the rule is for all groups? Wildcard (*) doesn't work.
You have to use regexps. Try '.*' instead.

2.3 Articles are not sorted correctly by date.
The sec. 1E+09 bug has reached us. Since 9.9.2001, new threads are not sorted correctly by date. This bug has already been fixed. The patch will hopefully be in KDE 2.2.1.

Questions about KNode 0.3.2

3.1 KNode crashes frequently on Caldera Open Linux 2.4
A conflict between the mimelib versions distributed with KDE 1.x and 2.0
Updated RPMS will be made available soon. Temporary workaround:
cd /opt/kde/lib
rm libmimelib.so
ln -s /usr/lib/libmimelib.so.1.0.1 libmimelib.so
rm libmimelib.so.1
ln -s /usr/lib/libmimelib.so.1.0.1 libmimelib.so.1

3.2 KNode doesn't remember the window size and position
You have to save these settings via "Settings->Save Options". This will work automatically in KNode >=0.4

3.3 In some newsgroups the article list shows a lot of questionmarks instead of the real characters.
This is a known bug caused by KNode's very limited support for non-ISO-8859-X charsets. We are working on this issue and you can expect it to be fixed in the next major release (probably 0.4).

3.4 Sending mails doesn't work at all.
The default configuration for the port number of the SMTP server is wrong. Change the port number from 115 to 25.

3.5 What does "501 FROM my-email-address invalid source route address syntax" mean?
This is a bug in KNode 0.3.2. Please update to a newer snapshot.

3.6 Why are my articles duplicated?
This problem happens only when you use the Leafnode feature "delaybody". It's a missunderstanding in handling articles between KNode and Leafnode.
At the moment I see two solutions:
1.) You have to ignore the duplicated articles.
2.) Don't use the "delaybody" feature in Leafnode.
This problem will be fixed in the next release of KNode.