Re: Enigma-Netmail test
  By: Alan Ianson to mark lewis on Wed Apr 22 2020 12:36:52


 ml>> [...] when it should have gone routed from here... that bug has
 ml>> hopefully be fixed now and i'm running the latest available code
 ml>> for the tosser... we're watching closely for more routed netmails
 ml>> arriving here with the crash bit in place to see if the tosser
 ml>> now properly strips/ignores that bit and follows my routing table
 ml>> properly ;)

 AI> I saw your comment about that. It looked like Mystic routed a
 AI> crash netmail to  your node? :)

yeah... but i haven't looked deeper to see if it was a mystic system or not...
i've been thinking that RM was running sbbs but could easily be wrong about
that...

 AI> I happen to have a Mystic I have been doing some testing with. I
 AI> am going to  use that setup with your node as the route-to and see
 AI> if it routes a crash netmail to your node and if it does you can
 AI> see what happens with it.

ok... it is possible to route crash netmail, though... it depends on one's
definition of crash...

crash means "send as soon as possible"... it doesn't necessarially mean "send
it direct now"...

this distinction is why the frontdoor guys introduced DIRect and IMMediate...

DIRect means "send directly, ignoring any routing statements"...

IMMediate means "send it right now regardless of any schedule
qualifications"...

a message with DIRect and CRAsh bits would mean "send as soon as possible and
send directly to the destination"...

a message with DIRect and IMMediate would mean "send right now and send
directly to the destination"...

a message with only IMMediate would mean "send right now following the routing
table"...

a message with only CRAsh would mean "send as soon as possible following the
routing table"...

 AI> If that does happen we should pass that info on to James. It's a
 AI> small but important detail.

even more important would be to ensure that HOLD, CRAsh, LOCAL, and IMMediate
are stripped in the packed message so they are not mistakenly used/followed by
an intermediate system... DIRect won't be seen by any intermediate systems...
not without manual intervention so it should probably also be stripped from the
packed message, too...

i'm sure all of this was already properly in mystic v1.11 before things moved
to another FTN... i don't understand why it has changed since then... i was
very active with mystic at that time and provided a lot of input and assistance
on this stuff... i dunno...


)\/(ark
--- SBBSecho 3.10-Linux