Get new headers not following server settings?

[dengle]

When retrieving new headers from biggulp.readfreenews.net (a free server I'm sure most of you all know), it often gives an error 400 due to too many connections for the access class. I have the retries set to 9, however, after one failure on new headers, it dies.

Is this a setting I'm missing or does the proggy not apply the retries setting when getting new headers?

[alex]

the 400 error is recoverable; you can also make any socket/string returned by server error recoverable in properties->general, recoverable errors.

if it is a socket error just put there the error number.

[dengle]

So in othere words...

REMS:

REad the Manual Stupid