Can I check routing logic with you?

If an echomail node is defined in Mystic and netmail comes in for it from another node, Mystic will route that netmail to the known node. Tick.


Now if that recipient netmail node sits lower down the echomail node list
(so it has a greater echomail node ID number) than another defined echomail node that just happens to have a routing rule that would otherwise apply to the incoming netmail... .. Mystic will still ignore that routing rule and route the netmail direct to the known defined echomail node? It seems the answer is also yes.

As an example in 21:1/100 HUB..

I have echomail node 21:3/100 with a routing rule 21:3/* and this is sitting
in the list of echomail nodes with and ID of 111

Then later on I have echomail node 21:3/102 define with no routing rule.

I send a netmail from 21:1/101 to 21:1/100 the HUB then does this

+ Jan 28 21:27:05 Importing 112647db.pkt (21:1/101 to 21:1/100)
+ Jan 28 21:27:05 Route (21:1/101 to 21:3/102) via 21:3/102

So ignores the routing rules of 21:3/100 and just routes to 3/102 because
it's known, albeit further down the list.

Righto.. now in this example (for various reasons) I wanted 3/102 to be able
to poll 21:1/100 and collect filebox traffic, but I wanted to route my netmail to 3/102 it via 3/100 HUB

It seems there's no way to do this...

I know most routing tables work on the last rule that matches applies, and clearly there's a defined direct route with 3/102 defined in 1/100 HUB .. but would there be a way to override that behavior to create a forced rule to direct 3/102 netmail to 3/100 instead?

Any suggestions/thoughts appreciated.

--- Mystic BBS v1.12 A46 2020/08/26 (Windows/32)
* Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (3:770/100)

Can I check routing logic with you?

Yes the logic is to check if there is a direct address configured and route to them if so. If there isn't a direct entry for that address, then it will look through and try to find the first routed match.

I know most routing tables work on the last rule that matches applies,
and clearly there's a defined direct route with 3/102 defined in 1/100
HUB .. but would there be a way to override that behavior to create a forced rule to direct 3/102 netmail to 3/100 instead?

I just finished adding a "Bypass Direct" flag for echomail nodes which will disable direct routing for that node, causing it to fall back to the netmail routing policy. Sounds like that should do exactly what you want! Its in the latest prealpha for A47 as of today (my today (Jan 30), not the today of time travelers such as yourself).

Other "forks" of logic after that if you wanted them could be done by using the "NOT" function of the routing

--- Mystic BBS v1.12 A47 2021/01/29 (Windows/64)
* Origin: Sector 7 | Mystic WHQ (1:129/215)

On 30 Jan 2021 at 09:50p, g00r00 pondered and said...

Yes the logic is to check if there is a direct address configured and route to them if so. If there isn't a direct entry for that address,
then it will look through and try to find the first routed match.

Thanks, that's what I thought was going on.

I just finished adding a "Bypass Direct" flag for echomail nodes which will disable direct routing for that node, causing it to fall back to
the netmail routing policy. Sounds like that should do exactly what you

Thanks for adding this :) Yep I think it will do the trick. I'll try to get updated in the coming week or so and test it out.

30), not the today of time travelers such as yourself).

There's gotta be some advantages of living in the future :)

Now those lottery number you wanted were 6, 23, ....

--- Mystic BBS v1.12 A46 2020/08/26 (Windows/32)
* Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (3:770/100)

I have a question regarding Netmail routing...

At my system, my uplink has the following Route Info setting:

1:* 2:* 3:* 4:*

But, when sending a Netmail to a node that is not directly connected to my system, I am getting the following error message:

"No netmail route"

What should be the proper netmail routing config then?

--- Mystic BBS v1.12 A42 2019/02/01 (Windows/64)
* Origin: Saturn's Orbit BBS - Rio de Janeiro, Brasil (4:801/188)

On 06 Feb 2021 at 07:10p, Flavio Bessa pondered and said...

I have a question regarding Netmail routing...
At my system, my uplink has the following Route Info setting:
1:* 2:* 3:* 4:*
But, when sending a Netmail to a node that is not directly connected to
my system, I am getting the following error message:
"No netmail route"

Are you trying to send netmail to a Zone 1 - 4 netmail address or is it an othernet Zone?

--- Mystic BBS v1.12 A46 2020/08/26 (Windows/32)
* Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (3:770/100)

Are you trying to send netmail to a Zone 1 - 4 netmail address or is it
an othernet Zone?

It was to a Zone 1 netmail address, but at the end of the day there was
an error at my routing config part. Got it fixed already.

--- Mystic BBS v1.12 A42 2019/02/01 (Windows/64)
* Origin: Saturn's Orbit BBS - Rio de Janeiro, Brasil (4:801/188)