Just a sample of the Echomail archive
Cooperative anarchy at its finest, still active today. Darkrealms is the Zone 1 Hub.
|    MYSTIC    |    Mystic support echo    |    16,010 messages    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
|    Message 14,401 of 16,010    |
|    Bj”rn Wiberg to Mike Dippel    |
|    Re: Routing Settings for Fido    |
|    27 Feb 22 18:23:53    |
      TID: Mystic BBS 1.12 A48       MSGID: 2:201/137 357a1cbe       REPLY: 1:135/393 4c3f6c94       TZUTC: 0100       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)       SEEN-BY: 1/123 15/0 80/1 90/1 92/1 103/705 105/81 106/201 120/340       SEEN-BY: 123/131 124/5016 129/305 330 331 153/757 7715 154/10 201/0       SEEN-BY: 201/137 203/0 124 218/700 221/0 1 6 226/30 227/114 229/110       SEEN-BY: 229/206 307 317 400 424 426 428 452 550 664 700 230/0 240/1120       SEEN-BY: 240/5832 266/512 280/464 5003 282/1038 292/854 8125 301/1       SEEN-BY: 301/113 317/3 320/219 322/757 335/364 341/66 234 342/200       SEEN-BY: 396/45 460/58 633/280 712/848 2452/250 3634/24 5020/1042       SEEN-BY: 5058/104       PATH: 201/137 0 203/0 280/464 301/1 229/426           |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
(c) 1994, bbs@darkrealms.ca