Bug 82671 - posts to moderated newsgroup don't go through
Summary: posts to moderated newsgroup don't go through
Status: RESOLVED UNMAINTAINED
Alias: None
Product: knode
Classification: Miscellaneous
Component: general (show other bugs)
Version: unspecified
Platform: Debian testing Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-06-01 23:46 UTC by Ross Boylan
Modified: 2018-09-04 18:39 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Ross Boylan 2004-06-01 23:46:38 UTC
Version:            (using KDE KDE 3.2.2)
Installed from:    Debian testing/unstable Packages
OS:                Linux

I have twice attempted to post to comp.lang.c++.moderated using knode.  Although the posting shows up in the sent folder, and there is no indication of an error, the post does not go through.  I receive no acknowledgement, and the post never appears.  When I sent the message via email to the email address for the list, it appeared shortly thereafter, so it's not that the moderators are asleep or didn't want to post.  (I just did my 2nd try by email and already have confirmation of its receipt.).

I speculate the problem has something to do with this being a moderated newsgroup.  I also have fairly tight firewalls, so possibly they are interefering.  On the latter point, I don't know where to look, but I can provide more info (all outbound operations should go through, and any packet recognized as resulting from an outbound session should be able to get back).
Comment 1 Ross Boylan 2004-06-02 02:36:37 UTC
I can post to an unmoderated group, either local or remote.

I have verified with the moderators of c.l.c++.moderated that they didn't get the previous posts.  I am checking with the local news server people.

In looking at the code for knnntpclient.cpp, function KNNntpClient::doPostArticle() ends like this

  if (!checkNextResponse(240))            // 240 article posted ok
    return;
}

Although checkNextResponse apparently does set an error code, this seems an odd ending.  Since there is an implicit return at the end of the function, it is equivalent to
  if ()
    return;
  else
    return;
Comment 2 Andrew Crouthamel 2018-09-04 18:39:50 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.