newsbin.com

Anyone else seeing this?

After their move to UsenetExpress I cannot download headers for several groups.

Even after "Delete stored posts" which removes the spool directory and of course, range.db file I'm getting these:
[12/02 07:05:04] ERROR Server:Newsdemon XOVER Data Corrupt: 2032852425
and lots of them.

It seems I just needed patience. After a long while the headers did download.

After more investigation, I had to disable XFeatures for the NewsDemon server. Too bad, I'll miss the header compression.

mjpierce wrote:After more investigation, I had to disable XFeatures for the NewsDemon server. Too bad, I'll miss the header compression.

Thanks! I wondered what was going on when everything started going to shit 2 days ago. I also had no idea they were moving the backbone to a different supplier. Hope they maintain their level of service as they've been rock solid for me for ages.

Cheers.

XFeatures is disabled by default these days because of stuff like this. Used to be it was defaulted to enabled but not it's disabled, and has to be enabled for new servers.

That doesn't help you if you're using an existing NBI though.

Quade wrote:XFeatures is disabled by default these days because of stuff like this. Used to be it was defaulted to enabled but not it's disabled, and has to be enabled for new servers.

That doesn't help you if you're using an existing NBI though.

Yeah, my .nbi is a frankenstein's-monster-affair that has been stitched together and relatively untouched over many years so compatibility issues were bound to occur at some point.

Sorted now though. Thanks all. Appreciated.

As a reminder for folks, on 12/7/20 the NewsDemon Blog noted that article numbering of headers changed (due to their backend move), which was causing general problems. See their blog at: https://www.newsdemon.com/blog/ for more info. Related to the change I've noticed an awful lot of missing data/articles, even for recent material ("Failed: 430 no such article"). I now have to regularly use my backup block accounts for fills. Until they change to their new backend (late January '21?) I would say their service is no longer generally usable. It's a shame to have such basic problems today, given their stellar history.