Howdy,

Over the last two weeks of so, I've done quite a few more updates to clrghouz - mostly on the back of errors that I saw as some folks started to use it (thanks) as well takling some of the "to do"s I had put down to do later.

I've added outbound polling - so now mail received can be sent out CRASH, Scheduled (twice daily) or held for collection. You'll be able to select your mode of operation in the web ui for now, and when I write an areafix there too.

Most of the improvements have been done on the back end (for the hub admin), but I've now got clrghouz sending some netmails when it sees problems. For example, if you use an incorrect packet password, you should get a netmail back letting you know (and that your last packet wasnt processed), as well when you are put on "auto hold" because polling your system is failing (after 5 attempts over 2ish days).

I've implemented more tracking of packets sent/received (which is now shown in the web ui) - which was a pre-requisite to enable you to resend packets if you need (this piece I need to implement). I also need to implement RESCAN, but I can do it manually if somebody wants some old messages resent.

I also have 1 more feature that I need to implement (echoarea security, with corresponding netmails back to you when you attempt to post to an area that you are not subscribed, or dont have permission). One network that I host for has a "hub only area" - so I need to implement that before I start to move all my hosting over to it.

If anybody else wants to play with clrghouz, your welcome to have a go and let me know if you find something not quite right, or not as expected.


...ëîåï
--- SBBSecho 3.20-Linux
* Origin: I'm playing with ANSI+videotex - wanna play too? (21:2/116)

On 27 Jul 2023 at 08:58p, deon pondered and said...

Over the last two weeks of so, I've done quite a few more updates to clrghouz - mostly on the back of errors that I saw as some folks started to use it (thanks) as well takling some of the "to do"s I had put down
to do later.

Thanks! :)

Most of the improvements have been done on the back end (for the hub admin), but I've now got clrghouz sending some netmails when it sees

:)

I also have 1 more feature that I need to implement (echoarea security, with corresponding netmails back to you when you attempt to post to an area that you are not subscribed, or dont have permission). One network that I host for has a "hub only area" - so I need to implement that
before I start to move all my hosting over to it.

I did get a number of these sent to 1/101 saying I was not allowed to post to the fsxNet echos :)

Happy to be a tester for this.

Kerr Avon [Blake's 7] 'I'm not expendable, I'm not stupid and I'm not going' avon[at]bbs.nz | bbs.nz | fsxnet.nz

--- Mystic BBS v1.12 A48 (Linux/64)
* Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)

Re: Re: Clrghouz update
By: Avon to deon on Sun Jul 30 2023 01:28 pm

I did get a number of these sent to 1/101 saying I was not allowed to post to the fsxNet echos :)

Happy to be a tester for this.

Oops :)

Yeah, I noticed that the address I was testing against was the originator of the echomail, not the packet that sent it too me ;)

I fixed that last night.

You can try a few things if you want, and make sure you get a response back:

* Send a packet with an incorrect packet password,
* Send a packet to an echo area that doesnt exist,
* Send one to an existing one that you dont have permission, eg: FSX_DIY
* Send a message to an echo that you havent subscribed to

(In each case you should get a netmail back).

I'm going to enable my "pi" build, so that the clrghouz container can be run on a PI. How much memory does your PI have? My biggest doubts at the moment is memory consumption especially when the number of echomails stored start to increase (and the number of nodes increases) - since I'm recording each seenby seperatly (so I can do some stats).

I want to optimise memory/consumption, its something I've put off, but I have everything else in place now that it is the next thing to do to tune...


...ëîåï
--- SBBSecho 3.20-Linux
* Origin: I'm playing with ANSI+videotex - wanna play too? (21:2/116)

On 30 Jul 2023 at 12:27p, deon pondered and said...

Yeah, I noticed that the address I was testing against was the
originator of the echomail, not the packet that sent it too me ;)

I fixed that last night.

Coolio, not a problem and good stuff for catching it.

You can try a few things if you want, and make sure you get a response back:

do you want this as 1/101 or me testing as 1/179 which has the current link with the HUB?

I'm going to enable my "pi" build, so that the clrghouz container can be run on a PI. How much memory does your PI have? My biggest doubts at the moment is memory consumption especially when the number of echomails

I think it's 4 gig but it's been a while I'm going to need to fire it up and check... will let you know.

I want to optimise memory/consumption, its something I've put off, but I have everything else in place now that it is the next thing to do to tune...

No prob and no rush in any of this.

Kerr Avon [Blake's 7] 'I'm not expendable, I'm not stupid and I'm not going' avon[at]bbs.nz | bbs.nz | fsxnet.nz

--- Mystic BBS v1.12 A48 (Linux/64)
* Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)

Re: Re: Clrghouz update
By: Avon to deon on Sun Jul 30 2023 02:33 pm

do you want this as 1/101 or me testing as 1/179 which has the current link with the HUB?

Actually, you could do it with both. :)

In most of my testing I've done, the other side has been "known" - I've not done much testing with unknown systems (1/101 will be unknown since if there are no auth details setup) - so be good to know what happens (I dont think I'm handling that case).

Technically mail from 1/101 shouldnt be processed (unless its netmail), but what I really want to do is reject the files/echomail in the first place. I might need to work that through a bit more.

I think it's 4 gig but it's been a while I'm going to need to fire it up and check... will let you know.

Ahh, OK, good. Be interesting how well it performs...


...ëîåï
--- SBBSecho 3.20-Linux
* Origin: I'm playing with ANSI+videotex - wanna play too? (21:2/116)

On 30 Jul 2023, deon said the following...

You can try a few things if you want, and make sure you get a response back:

* Send a packet with an incorrect packet password,
* Send a packet to an echo area that doesnt exist,
* Send one to an existing one that you dont have permission, eg: FSX_DIY
* Send a message to an echo that you havent subscribed to

(In each case you should get a netmail back).

Just tried all of these and they worked as expected. I forgot to remove sending to 3/100 for the incorrect PKT password, so it did go through there but Clearing Houz did reject it.


Jay

... We dressed up as almonds for Halloween. Everyone thought we were nuts

--- Mystic BBS v1.12 A49 2023/04/30 (Linux/64)
* Origin: Northern Realms (21:3/110)

Re: Re: Clrghouz update
By: Warpslide to deon on Sun Jul 30 2023 08:05 am

Hey Jay,

Just tried all of these and they worked as expected. I forgot to remove sending to 3/100 for the incorrect PKT password, so it did go through there but Clearing Houz did reject it.

Awesome...

I'm going to keep an eye on clrghouz over the next few days - I think I have got everything sorted now. If I dont hear of, or see, any issues I'm going to start to move stuff off of binkd/hpt to clearing houz.

Thanks for the testing, its been really helpful.


...ëîåï
--- SBBSecho 3.20-Linux
* Origin: I'm playing with ANSI+videotex - wanna play too? (21:2/116)

Howdy,

I've just pushed out an update to clrghouz that enables you to see netmail or echomail to help with debugging.

It only works with those items with a msgid. In the search box (top of the page - after being logged in), if you key in the msgid, you'll get a list of messages that have that ID as the msgid, or replyid.

If you select an item from the search list, and:

* for netmail, it is either from or to your system,
* for echomail, your system is in the seenby,

Then you'll be able to see it.

(Naturally this only works for netmail or echomail that passes through Hub 3).

Let me know if you see something unsual...


...ëîåï
--- SBBSecho 3.20-Linux
* Origin: I'm playing with ANSI+videotex - wanna play too? (21:2/116)

Re: Clrghouz update
By: deon to All on Tue Dec 19 2023 12:05 pm

Howdy,

I've just pushed out an update to clrghouz that enables you to see netmail or echomail to help with debugging.

So since some messages come in as ANSI (and the clrghouz welcome message is ANSI) when viewing messages in clrghouz, it would appear jibberish (with the ANSI sequences)...

So I had a look at ansilove.js - and it works really well. It does a nice job of presenting a ANSI text as a PNG file. Kudos to that team who wrote it: https://github.com/ansilove/ansilove.js

I might have to look at filtering out KLUDGE lines to really make these ANSIs pop...

https://clrghouz.bbs.dege.au/echomail/view/421217 https://clrghouz.bbs.dege.au/echomail/view/421094

[Sorry, you'll only be able to see these if you have an account, you've claimed your BBS and it is in the seenby of the respective messages - and hub 3 doesnt get all the SEENBY info :(...]


...ëîåï
--- SBBSecho 3.20-Linux
* Origin: I'm playing with ANSI+videotex - wanna play too? (21:2/116)