Page 1 of 1

6.71B1 sends bad commands to server: nothing can be fetched

PostPosted: Mon May 23, 2016 8:59 pm
by stephane
Since the upgrade to B1, Newsbin is unable to fetch anything from the server (xsnews.nl). Log below.
Reinstalling 6.70 and transfers restarted ok. Sorry I forgot to write down the build number, but SHA1 is 5763CFF64843BDEDA0588DDD498BD3CD

[01:33:06] ERROR Server:HollandSendCommand - failed Status Response From server: 500 unsupported.
[01:33:06] ERROR Server:HollandSendCommand - failed Status Response From server: 500 unsupported.
[01:33:06] ERROR Server:HollandSendCommand - failed Status Response From server: 500 unsupported.
[01:33:06] ERROR Server:HollandSendCommand - failed Status Response From server: 500 unsupported.
[01:33:06] ERROR Server:HollandSendCommand - failed Status Response From server: 500 unsupported.
[01:33:06] ERROR Server:HollandSendCommand - failed Status Response From server: 500 unsupported.
[01:33:06] ERROR Server:HollandSendCommand - failed Status Response From server: 500 unsupported.
[01:33:06] ERROR Server:HollandSendCommand - failed Status Response From server: 500 unsupported.
[01:33:06] ERROR Server:HollandSendCommand - failed Status Response From server: 500 unsupported.
[01:33:06] ERROR Server:HollandSendCommand - failed Status Response From server: 500 unsupported.
[01:33:06] ERROR Server:HollandSendCommand - failed Status Response From server: 500 unsupported.
[01:33:06] ERROR Server:HollandSendCommand - failed Status Response From server: 500 unsupported.
[01:33:57] ERROR Server:HollandSendCommand - failed Status Response From server: 500 unsupported.
[01:33:57] ERROR Server:HollandSendCommand - failed Status Response From server: 500 unsupported.
[01:33:57] ERROR Server:HollandSendCommand - failed Status Response From server: 500 unsupported.
[01:33:57] ERROR Server:HollandSendCommand - failed Status Response From server: 500 unsupported.
[01:33:57] ERROR Server:HollandSendCommand - failed Status Response From server: 500 unsupported.
[01:33:57] ERROR Server:HollandSendCommand - failed Status Response From server: 500 unsupported.
[01:33:57] ERROR Server:HollandSendCommand - failed Status Response From server: 500 unsupported.
[01:33:57] ERROR Server:HollandSendCommand - failed Status Response From server: 500 unsupported.
[01:33:57] ERROR Server:HollandSendCommand - failed Status Response From server: 500 unsupported.
[01:33:57] ERROR Server:HollandSendCommand - failed Status Response From server: 500 unsupported.
[01:33:57] ERROR Server:HollandSendCommand - failed Status Response From server: 500 unsupported.
[01:33:57] ERROR Server:HollandSendCommand - failed Status Response From server: 500 unsupported.
...
Stéphane

Re: 6.71B1 sends bad commands to server: nothing can be fetc

PostPosted: Mon May 23, 2016 10:26 pm
by Quade
In the server options do you have "Use Body Command" checked? If not you might try that. Some servers don't support the whole usenet spec. I think XS is one of them.

It's possible the "BODY" itself isn't working

Edit: I confirmed that "Body" is working. Maybe I need to make using it automatic...

Re: 6.71B1 sends bad commands to server: nothing can be fetc

PostPosted: Thu Jun 09, 2016 1:37 am
by stephane
I downgraded. BODY command is not used (so I guess it wasn't when I upgraded). I'll wait for the next BETA I guess.
[EDIT]
I can see there is a new Beta. I'll try it... later.

Re: 6.71B1 sends bad commands to server: nothing can be fetc

PostPosted: Thu Jun 09, 2016 4:15 am
by Quade
Turns out it wasn't "body" it was "XFeatures" in the advanced server options. Even if you don't upgrade, just disabling XFeatures would make it work too.

Re: 6.71B1 sends bad commands to server: nothing can be fetc

PostPosted: Sun Jun 12, 2016 11:27 pm
by stephane
True.