Hi g00r00,

Had a situation recently where someone sent a netmail to a point address on my system that used to exist but no longer does. Since it didn't match any of the configured points it was routed to 21:* and ended up getting passed back & forth between my system and the hub until the hub noticed & nuked it.

My fsxNet address is 21:3/110


$ ./mis poll route 21:3/110.10
Netmail addressed to 21:3/110.10 would route to 21:3/110.10 (Ogg's fsxNet Point)

$ ./mis poll route 21:3/110.1
Netmail addressed to 21:3/110.1 would route to 21:3/100 (fsxNet)

$ ./mis poll route 21:3/110
Netmail addressed to 21:3/110 would route to 21:3/100 (fsxNet)


Would it be possible to have Mystic either drop or bounce a message back if it receives a netmail addressed to its boss node address but the point doesn't exist?


Jay

... I don't know if I'm allergic to dogs, I've never been stung by one

--- Mystic BBS v1.12 A49 2023/04/30 (Linux/64)
* Origin: Northern Realms (1:229/664)

Would it be possible to have Mystic either drop or bounce a message back if it receives a netmail addressed to its boss node address but the
point doesn't exist?

Sure thing. I'll need to not forget about this this coming weekend and see if I can set up a test. If you don't hear anything about it being fixed from me in the next week or so please feel free to nudge me lol

... A Mystic asking for a hot-dog: "Make me one with everything"

--- Mystic BBS v1.12 A49 2023/04/30 (Windows/64)
* Origin: Sector 7 * Mystic WHQ (1:129/215)

On 21 May 2023, g00r00 said the following...

Sure thing. I'll need to not forget about this this coming weekend and see if I can set up a test. If you don't hear anything about it being fixed from me in the next week or so please feel free to nudge me lol

I know you're busy, but I figured I'd nudge you anyway... ;)


Jay

... I hate funerals that are at 9am. I'm not really a mourning person

--- Mystic BBS v1.12 A49 2023/04/30 (Linux/64)
* Origin: Northern Realms (1:229/664)