1. Forum
  2. FidoNet
  3. MYSTIC

  • Re: Crash Netmail

    From g00r00@1:129/215 to Flavio Bessa on Mon May 13 00:35:31 2024
    Mystic has it's own logic as to how it will route netmail. Refer to whatsnew.txt to see what this is. g00r00 has documented it there. Loo for 'netmail routing' in that document and read this to understand th steps Mystic takes.

    Yeah, I did go through the docs and the process is pretty smart 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)
  • From Paul Hayton@3:770/100 to g00r00 on Tue May 14 14:21:16 2024
    On 13 May 2024 at 12:35a, g00r00 pondered and said...

    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.

    If there's non delivery after X attempts I'd suggest an auto netmail to the sender is generated and something to sysop as well / noted in MUTIL logs.

    Not sure if the logic is in there but if a netmail is routed to another Mystic system and the routing at destination sends the netmail back to the originating system... and you start getting a back and forth loop happening... there needs to be something there to detect this, cease the loop and send a netmail to the sender and sysop of the source system alerting them to the failed delivery...

    Nice to see you active, hope things are going well.

    Kerr Avon [Blake's 7] 'I'm not expendable, I'm not stupid and I'm not going' avon[at]bbs.nz | bbs.nz | fsxnet.nz

    --- Mystic BBS v1.12 A48 (Linux/64)
    * Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (3:770/100)