Newshound and Eternal September

Could I suggest that the -32 on the end of the version number is removed, as it is probably no longer relevant, and is likely to be confusing to many?

I agree. It’s not in RC2. Which, by the way, fixes a completely different issue reported to me by Andrew Rawnsley.

Hey all

Dave Higton pointed me at this thread, so I thought I might as well chime in :)

Thanks Steve for doing the conversion to git – I hadn’t even realised these were still stored in CVS, and had been a little puzzled when sourceforge sent me an email a few days ago saying I’d made a whole load of new commits to these projects.

There’s no licensing issues, apart from perhaps that I may not have made the fact that it’s BSD licensed clear enough.

If folks want to move the source etc over to GitHub I’m supportive of that. I’ve given Dave write access to the repo, and as Steve says he has admin access as well and I’m happy for him to add people he trusts.

(Apologies for the code; much of it dates back to 1996 and as best I can remember I didn’t know C when I started writing NewsHound.)

Thanks

Joseph

Hmm. I’ve just managed to get some communication with the eternal-september server in secure mode, after issuing a STARTTLS :-)

It’s not by any means working properly (it just crashed horribly), but I do feel encouraged.

The Mozilla server doesn’t like STARTTLS; it responds with a 500 error.

Just been trying to access the eternal-september website, partly to check something a person said on the Armini mailing list about when they pinged news.eternal-september.org it responded from reader2.eternal-september.org, which I know uses a different port.
The website seems to be down or overloaded, tried three browser all failed to access the site.

One of my machines seems to have stopped accessing news from aioe on port 119 via Newshound at around the same time as this thread started. “Connection to server failed. Connection refused” using the version bundled in the current Netfetch release.

Hi Grahame,

What AIOE server are you pointing towards.

There is the main server starting with nntp or backup starting with news.

I have just tried it with both 1.52 and 1.53 and it works Ok.

Perhaps a common fault now resolved?

I’m using nntp address version. I was starting to wonder if the problem started after installing the latest ARMX6 update, but that may just be a coincidence. I’ll pop downstairs and give it another try, and also try the news address.

<fx: goes down, comes back up>

Just checked with no change in result using either nntp. or news. I did a full reboot after changing the news server to ensure the system variable had been updated, checking it was correctly set afterwards.

Grahame,

I have the latest ARMX6 updates installed.

It could be a localised network issue , are you in the same sort of location as Chris?

You could also check your IP or ISP IP address range isn’t on a list of banned IP via the AIOE website.

It even works in Netsurf!

Statistics>Banned IPs

It will give a reason as well.

Server status shows as OK via the Tools option

My IP is not listed as banned. I do have a Wandboard homebrew that I can connect to aioe with on the same LAN. The only real difference is that one hasn’t had the OS18 update from RComp as it doesn’t have any trace of an SD card once it has booted from that SD card to the desktop, so the upgrade can’t find it to update. It might just be that I upgraded the ARMX6, where the Newshound problem occurs, to OS18 at around the time this started but I can’t be sure.

Because the Newshound error box self-closes after a while, it’s hard to tell exactly when this issue started with Newshound or if it coincides with the ROM update of that machine. But if there was an issue related to the RComp upgrade I would have seen reports by now from other users in the mail list, so this is probably one of those coloured fish (red herring).

I very much double your issue Grahame has anything to do with the OS18 update to your ARMX6. I am running that on my ARMX6, and !newshound is still working now I changed the port number to 119 for Eternal-September.

It appears Newshound on the ARMX6 at least places a logfile within !SysLog.Logs (which in my case is within !Boot.resources.

By the way quick question for Dave Higton, is there a version of Newshound available allowing me to post to Eternal-september yet. Even if beta?

I did suspect there wasn’t a problem with OS18 otherwise I would have been aware of it by now, but I thought it was worth a mention as the timing might have fitted.

My syslog for newshound just consists of lines: -

20 Jan 14:33:54 000 Error : Connection to server failed – Connection refused
20 Jan 14:54:02 000 Error : Connection to server failed – Connection refused
20 Jan 15:03:54 000 Error : Connection to server failed – Connection refused

going back every 30 minutes to 16th Jan – oldest entry. I’m sure them problem started before then, but the details have probably expired from the log.

going back every 30 minutes to 16th Jan – oldest entry.

You will find the previous log in SysLog.Logs.Old.

The first occurrence was on 14th Jan and then continuously since then.

is there a version of Newshound available allowing me to post to Eternal-september yet. Even if beta?

Yes. My apologies, I thought I had posted earlier in this thread to say so, but evidently I only did so in the csa.apps newsgroup.

Email me at dave at davehigton dot me dot uk and I’ll send you RC2.

I’ve just been trying the two aoie addresses. I can’t get a connection to port 119. Port 80 on nntp.aoie.org returns a page that suggests the domain name may be up for sale.

It looks like there’s a problem that is beyond me to solve!

Try aioe.org.
http://news.aioe.org/ has the news server info.

Dave

As per testing information sent to you previously 1.52 and 1.53 work ok with nntp.aioe.org.

Looks like a typo error has set in as Frank suggests :-)

Looks like a typo error has set in as Frank suggests :-)

Oh, bigger it :-)

Chris Hughes: all my emails to you have been rejected as spam. I don’t know if you have any control over your spam filter – if so, please have a look at what you can do.

I hate it, I really hate it, when stupid systems like that throw the baby out with the bathwater.

I hate it, I really hate it, when stupid systems like that throw the baby out with the bathwater.

Indeed. It wouldn’t kill them to have a spam folder where stuff is deleted automatically after X days. That way, the user can look to see if something was mistaken for being spam.

If it was rejected back to you, can you examine the headers? A system that rejects a message ought to insert some indication of why (IP address, subject, not in recipient’s address book, blah blah).

I’ve examined the headers, but I can’t see any reason for the rejection.

I sent one message with a Runimage attached. I haven’t seen a rejection for that. Immediately after the one with the attachment, I sent another one without attachment, as a sort of insurance policy in case the first one was rejected. That second one got a rejection.

I then sent another one to tell Chris of the rejection, thinking that it referred to the first one – I hadn’t examined it in detail. The third one was also rejected as spam.

I’m guessing that the first one was rejected, but silently. Even worse.

Sounds like… Some utter PoS freaked out at an attachment that it couldn’t make sense of, and decided that your address was not to be trusted any more.

That sort of “security” is on par with “nuke it from space”; especially when it is doing such a great job of rejecting stuff that nothing gets through.
Makes you wonder how many other legitimate things were discarded/bounced where the sender thought “oh bigger it” ☺ and simply gave up.

I’m happy that a recent message from Doug arrived at my domain email account with the prefix “[Spam]”.
Why am I happy? It’s because OVH doesn’t provide a spam folder, and I had no messages that appeared to be spam, so I was wondering if they were silently rejecting things (every so often I find legitimate messages in Yahoo’s spam folder, and legitimate spam in the inbox, the system isn’t infallible). Since Doug’s message came through with a spam warning (no idea why), I know at least it will tag the message as possibly being a spam, and deliver it anyway, so I can use the biological processor to make the final decision.
That’s how it ought to be.