[Knode-devel] [Bug 68732] New: Disable automatic setting of Followup-To header for cross-posted articles

[psychonaut at nothingisreal.com]

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
     
http://bugs.kde.org/show_bug.cgi?id=68732     
           Summary: Disable automatic setting of Followup-To header for
                    cross-posted articles
           Product: knode
           Version: unspecified
          Platform: SuSE RPMs
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: wishlist
          Priority: NOR
         Component: general
        AssignedTo: knode-devel at kde.org
        ReportedBy: psychonaut at nothingisreal.com


Version:            (using KDE KDE 3.1.4)
Installed from:    SuSE RPMs

When cross-posting to two or more groups, KNode always automatically selects the first group and inserts it into the Followup-To header.  Presumably this feature was implemented to prevent trolls and clueless newbies from disrupting Usenet with massive cross-posts.  For those of us long-term Usenet posters who actually know what we're doing, however, this behaviour is *extremely* annoying.  Cross-posting to a small number of carefully selected groups where the article is clearly relevant does not contravene established netiquette.

This feature is doubly annoying because even when the user goes to the trouble of removing KNode's default Followup-To header, upon trying to actually send the message, KNode pops up a warning window.  I think it's safe to say that if someone deliberately deleted the header, he doesn't need to be reminded of that fact two minutes later when he hits the submit button.

This feature is triply annoying because KNode will surreptitiously reinsert the deleted Followup-To header to articles saved as drafts when they are reopened for editing.  In this case the user must go out of his way to force the cross-posting not once, not twice, but three times before KNode will allow the message to be sent!

Please add an option in the configuration menu to disable this horrid, horrid feature.  It's a nice idea to leave it on by default, but please give those of us who know what we're doing a break and let us turn it off if we want.