Hello AgoraNet,

A test post from disflux (46:1/115), a new node here. The board runs
flux/bbs, our own BBS with its own binkp mailer and tosser, so this
checks that echomail goes out right.

Thanks to Accession for the quick setup.

phrac

--- flux/bbs 0.1.0
* Origin: disflux (46:1/115)

phrac wrote:

A test post from disflux (46:1/115), a new node here. The board runs flux/bbs, our own BBS with its own binkp mailer and tosser, so this checks that echomail goes out right.

Gotcha!

-esc
--- ViSiON/3 v0.9.4/Linux
* Origin: gEMENON (46:1/211)

Hey Phrac

On 26/10/2026 20:27 phrac said...

Hello AgoraNet,

A test post from disflux (46:1/115), a new node here. The board runs flux/bbs, our own BBS with its own binkp mailer and tosser, so this
checks that echomail goes out right.

Thanks to Accession for the quick setup.

phrac

--- flux/bbs 0.1.0
* Origin: disflux (46:1/115)

Greetings, from another tester with my own thing going! :)

Echomail is continuing to be a headache for me (BinkD and Husky).

Randers

--- Krystal BBS Software
* Origin: Dumpster Dive - Victoria, Australia (46:30/106)

Hey Randers!

On Tue, Oct 27 2026 14:11:48 +1100, you wrote:

Echomail is continuing to be a headache for me (BinkD and Husky).

What exactly is a headache? I may be able to assist as I use both of what you listed above. ;)

Regards,
Accession

... Politicians and diapers should be changed regularly for the same reasons. --- AmberEdit/linux 0.9.4
* Origin: thePharcyde_ telnet://bbs.pharcyde.org (Wisconsin) (46:1/100)

Hey Accession,

On 27/10/2026 16:48 Accession said...

What exactly is a headache? I may be able to assist as I use both of
what you listed above. ;)

Thanks! Nothing is really inherently faulty with either, and trouble shooting is a matter of time and learning as always. Panadols are needed for the headache, but they are growing pains only. It has just been time consuming.

At the moment, one annoyance is that I am needing to share the same password across two different FTN networks when it resolves to the same hub address (in this case Clearing Houz). I get an 'inconsistent pwd settings' error if I try and make them separate. But, it saves call-outs I guess. I haven't tried hard to fix it just yet. It is low in the list of bugs to work out.

The rest is all my garbage, one way or another, and has been solved - as far as I know.

A repeating problem (also with Synchronet, which is odd - could be a different origin) was the @fidonet domain being added to FTN addresses, due to config only being read once. There were lots of glitches with leftover files causing problems, too.

Husky silently not tossing messages has been a battle - due to things like area lines being in the wrong order, and also no tossed messages for 10 days due to not realising Agoranet packet passwords are blank (I should have remembered that one from Synchronet!). Other small issues here and there. Those are all my stuff to solve, though.

A forced trouble shooting measure was implementing real time error messages when things go wrong, that get sent to my phone. Which has been lovely, because it has lead to enabling alerts for other things like incoming messages, new users, etc. So there's a silver cloud to it all.

There will be more glitches. It sure is fun, though.

I think. :)


Randers

--- Krystal BBS Software
* Origin: Dumpster Dive - Victoria, Australia (46:30/106)

Hey Randers!

On Wed, Oct 28 2026 20:41:24 +1100, you wrote:

At the moment, one annoyance is that I am needing to share the same password across two different FTN networks when it resolves to the same
hub address (in this case Clearing Houz). I get an 'inconsistent pwd settings' error if I try and make them separate. But, it saves call-outs I guess. I haven't tried hard to fix it just yet. It is low in the list of bugs to work out.

Don't worry about trying to work that "bug" out. IIRC, this is a pretty known thing in most binkp implementations. When a connection is made, all matching AKAs are checked, and the first one to match begins the transfers.

I actually recommend people that connect here for multiple networks to do this. It just makes it easier on the whole process, and for both sides.

A repeating problem (also with Synchronet, which is odd - could be a different origin) was the @fidonet domain being added to FTN addresses,
due to config only being read once. There were lots of glitches with leftover files causing problems, too.

Husky silently not tossing messages has been a battle - due to things like area lines being in the wrong order, and also no tossed messages for 10 days due to not realising Agoranet packet passwords are blank (I should have remembered that one from Synchronet!). Other small issues here and there. Those are all my stuff to solve, though.

Ah, I see. I also use Synchronet, so I can attest that the configurations of both differ just enough to forget something in one or the other. ;)

There will be more glitches. It sure is fun, though.

That's all that matters (that you're enjoying it)!

Regards,
Accession

... Sarcasm, because beating people up is illegal.
--- AmberEdit/linux 0.9.4
* Origin: thePharcyde_ telnet://bbs.pharcyde.org (Wisconsin) (46:1/100)

Hey Accession,

On 28/10/2026 18:05 Accession said...

Don't worry about trying to work that "bug" out. IIRC, this is a
pretty known thing in most binkp implementations. When a connection
is made, all matching AKAs are checked, and the first one to match
begins the transfers.

I actually recommend people that connect here for multiple networks
to do this. It just makes it easier on the whole process, and for
both sides.

Right, thanks. Good to know. It is not a big deal at all, and an easy fix compared to other stuff.

Ah, I see. I also use Synchronet, so I can attest that the
configurations of both differ just enough to forget something in one
or the other. ;)

Yeah.. just enough to make it confusing! But, solving these small glitches makes them satisfying to solve, too. It would actually be really interesting to revisit Synchronet once I am done with this, knowing what I know now. Which is still not that much :D

That's all that matters (that you're enjoying it)!

It's great! And I'm posting more, and actually interacting more with other boards now, too, having slopped this software together myself. I am more inspired to use it, with more perceived ownership of the project.

But - putting together (getting Claude to put together) my own BBS software is possibly the biggest piece of string I have ever encountered. Where do I stop with it? Each little feature I add isn't enough... I want more, MORE! :D

I should have named it Franken-BBS... Partially because I made it, and partially because in reality I didn't make it at all. Still fun, though.

Thanks again for your help :)


Randers

--- Krystal BBS Software
* Origin: Dumpster Dive - Victoria, Australia (46:30/106)

Randers wrote:

But - putting together (getting Claude to put together) my own BBS software is possibly the biggest piece of string I have ever encountered. Where do I stop with it? Each little feature I add isn't enough... I want more, MORE! :D

I should have named it Franken-BBS... Partially because I made it, and partially because in reality I didn't make it at all. Still fun, though.

Thats exactly what I'm doing over here on my board! I started with a port of iniquity and I just keep adding stuff to it!

-- phrac - disfluxbbs.com

--- flux/bbs 0.1.0
* Origin: disflux (46:1/115)