Subj : Re: Routing Settings for Fido
To   : Mike Dippel
From : Bj”rn Wiberg
Date : Sun Feb 27 2022 06:23 pm

Hello Mike!

On 27 Feb 2022, Mike Dippel said the following...
 MD> I tried to send a netmail to someone other than my hub.  The netmail did
 MD> not go direct to the address, but went to the hub.

I think that should be so -- only crashmail is sent directly to the recipient's system (for points, via their boss node). However, I don't think there is any option to flag a netmail as "crash" from within the message editor parts of Mystic?

However, if you have defined an echomail node for that specific recipient in your Mystic setup -- which is a rather tedious "work-around" as netmails often are "one-off" messages -- and flagged (Export Type) that echomail node as Crash (send directly and as soon as possible) or Direct (do not send via anyone else; requires you or the recipient system to initiate a poll, though, to actually deliver it), any outgoing mail for that node will be flagged accordingly in the outbound folders and handled as desired.

I believe you will also need to make an explicit exception to the routing of the zone that the recipient's node is in, in the Routing Info of your "normal" uplink (hub) for that zone, or it will follow the routing rules and ignore the fact that you have defined a specific echomail node for the recipient...

There is a short example of this here:

http://wiki.mysticbbs.com/doku.php?id=config_echomail_nodes#export_type

....however that one shows how an entire net (1:123/*) and not just a specific node (e.g. 1:123/456) is being forced to go to a certain uplink. In your case you would want to modify the Routing Info to use the specific node number of the recipient instead of an entire net.

Hope this helps!

Best regards
Bj”rn

--- Mystic BBS v1.12 A48 2022/02/15 (Linux/64)
 * Origin: Star Collision BBS, Uppsala, Sweden (2:201/137)

.