Post reply

Warning: this topic has not been posted in for at least 120 days.
Unless you're sure you want to reply, please consider starting a new topic.
Name:
Email:
Subject:
Message icon:

Verification:
Type the letters shown in the picture
Listen to the letters / Request another image

Type the letters shown in the picture:
[Anti-Spam] Type in w65nbi:

shortcuts: hit alt+s to submit/post or alt+p to preview


Topic Summary

Posted by: yDecode
« on: May 18, 2009, 09:23:00 PM »

We updated download links with final version which fixes this and a number of other bugs. Please retry the download with the new version which should now work on your server as well.
Posted by: yDecode
« on: April 28, 2009, 02:19:35 PM »

I think we found the bug, thanks to your helpful log - we also found a few of our own - so I guess we'll have a beta version prepared in a couple of days which will work entirely. The problem was minor - in handling the output of server responses so it's also easy to fix.

However, it was not really "our" bug. Easy Post was handing stuff properly.

The server in question - usenetserver.com is sending INCORRECT codes. 201 code which it sends on login means "no posting allowed". Obviously if no posting is allowed Easy Post being a posting software has nothing to do there and quits.

You may say - yes, but it should be allowed only after login - well - on properly written server, 200 code (posting allowed) should be sent on connection regardless if user is logged in or not or if it does require login or not - and only when the posting is attempted but user is not logged in before doing that - the server would return "error" code. At least that's how it should be done with a proper server.

I just tried a few more servers that also require authentication and they all without exception return proper "200" code on connection - so usenetserver.com is the one to blaim here. Perhaps maybe a few others as well.

So we'll put a little bit of "tolerance" to such faulty messages that may come from server to avoid such cases in the future. Anyway, it should work with next release thanks to new built-in tolerance.
Posted by: wanderer0621
« on: April 26, 2009, 03:38:14 PM »

Hi.

So I just installed the alpha application on my windows 2000 laptop. with my primary server (usenetserver.com) it would not connect. I checked all my settings, login/pw, and everything is correct.  the errorlog file reported:

4/26/2009 7:22:04 AM Error loading list. Socket error #10060
4/26/2009 7:24:44 AM Unexpected server response.
4/26/2009 7:24:46 AM Unexpected server response.
4/26/2009 7:24:47 AM Unexpected server response.
4/26/2009 7:24:48 AM Unexpected server response.
4/26/2009 7:24:49 AM Unexpected server response.

just for kicks, I applied connection settings for my local internet provider, and it actually read the newsgroup list.. ! woohoo.!  I'm sure its going through cox now..

so maybe there's a problem with login info passing?