FB> PH> Mystic has it's own logic as to how it will route netmail. Refer to
FB> PH> whatsnew.txt to see what this is. g00r00 has documented it there. Loo
FB> PH> for 'netmail routing' in that document and read this to understand th
FB> PH> steps Mystic takes.
FB> Yeah, I did go through the docs and the process is pretty smart
FB> actually.
The auto routing can really simplify things!
You are correct there is a problem with direct flag where it is not routed
directly to the node - the flag does not override anything..
It has been a while so my memory is foggy but I think the reason this happened
is because there was no way to specify the direct flag on a per message level
within Mystic when sending Netmail. It is either every single netmail in the
base gets direct or none of them do - which is a problem that needs to be
resolved first. Users should be able to per-message direct a Netmail if they
meet a specific ACS level configured.
Once that part is done then the tosser needs to override any auto routing and
send it direct.
One challenge I could use suggestions on for the community is what happens when
a netmail is flagged direct and there is no nodelist entry or the entry is there
but the system doesn't answer or doesn't have an IP address/hostname etc.
... There is an exception to every rule, except this one.
--- Mystic BBS v1.12 A49 2024/05/13 (Windows/64)
* Origin: Sector 7 * Mystic WHQ (1:129/215)
|
