(*** This bug was imported into bugs.kde.org ***) Package: knode Version: 0.6 (using KDE 2.2.0 ) Severity: wishlist Installed from: Unspecified Linux Compiler: Not Specified OS: Linux OS/Compiler notes: Not Specified When selecting "Forward by E-Mail" to forward an article KNode only shows three header fields in the message: Subject From and Date. These are too few. Would be nice if one could select the fields or just include *all* fields in the message. "My" problem was: Whenever I forwarded a message the recipient could not determine the group the article was in. Thanks in advance! Great work! Christian. (Submitted via bugs.kde.org)
kdenetwork/knode knarticlefactory.cpp1.641.65 kngroupbrowser.cpp1.351.36 Author: maragato Modified Files: knarticlefactory.cpp kngroupbrowser.cpp Log Message: CCMAIL: 32535-done@bugs.kde.org Properly identify article when forwarding by email.
Please reopen this bug report. I don't see this fix in KDE 3.5.1; the only headers present in e-mail forwards are Subject, From, Date, and Newsgroup. I can't find any way of configuring KNode so that it can include specific additional headers, or even all headers. There are many cases in which it is important to send certain other headers, or all headers. Some examples: 1) The newsgroup alt.humor.best-of-usenet accepts submissions by e-mail, and requires that all forwarded articles contain the Message-ID header. 2) If you are experiencing technical problems posting to a newsgroup, the person you contact for technical support may wish to see an example of an article you tried to send, naturally including all headers. 3) If you forward someone a newsgroup article by e-mail, they naturally might wish to open the article in their newsreader so that they can read the rest of the thread. If the Message-ID header were included, the user could simply click on it and have it open in their newsreader, but without it they are forced to manually search for the article with their news client or with Google Groups.
This bug/feature request is still outstanding as of KDE 3.5.5. Please reopen.
This bug/feature request is still outstanding as of KDE 4.4.1. Please reopen.