Hello mark,

On Tuesday February 16 2021 05:50, you wrote to Nigel Reed:

 ml> there was also something written that originally described the PING
 ml> function but i don't recall where it was written... i've not found
 ml> anything about it in my FTSC documents library, either...

FTS-5001.005  par 5.10

5.10. Robot flags
-----------------

  PING
  ----

    Specified as exactly "PING" with no arguments.  Nodes flying this
    flag will adhere to the following functionality:

    1) PING-function:

    If a message destined to "PING" arrives at its final destination
    and this final destination flies the "PING"-flag, then the
    receiving node will bounce the message back to the original sender
    clearly quoting all the original via-lines.

    If a message destined to "PING" arrives at its final destination
    but this final destination does _not_ fly the "PING"-flag then the
    message may be deleted from the inbound-queue without further
    follow-up.

    2) TRACE-function:

    If a message destined to "PING" arrives at a node which flies the
    PING-flag but is merely passing-through to another destination
    then the in-transit node will notify the sender of this occurrence
    and will forward the original mail unaltered towards its final
    destination.

    WARNING: the sender's name (in either direction) must *NEVER* be
    "PING".


What more needs to be said?


 ml> i remember implementing it in my netmgr configs quite a while back...

Your implementation does not support the TRACE part.


Cheers, Michiel

--- GoldED+/W32-MSVC 1.1.5-b20170303