Subj : Re: ping netmail - Does M
To : G00R00
From : WKITTY42
Date : Thu Jan 31 2019 07:20 pm
On 09/01/14, g00r00 said the following...
g0> Ps> Does Mystic currently handle netmail addressed to "ping" to reply bac
g0> Ps> to the sender a route path the netmail has taken thus far, and contin
g0> Ps> sending on the original as expected?
g0>
g0> Let me make sure I understand exactly what you're asking for.
http://ftsc.org/docs/fts-5001.005
====== snip ======
Publication: FTS-5001
Revision: 5
Title: Nodelist flags and userflags
Author: FTSC Members, Administrator and Honoured Guests
Date: 2014-07-01
[...]
Section 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".
====== snip ======
as for software that supports it, numerous netmail trackers recognize and
respond to ping messages... OT-Track does, netmgr can be configured to, GIGO
(FTN<->internet gateway package) can be configured to... there are others, as
well...
HTH
--- Mystic BBS v1.10 A51 (Windows)
* Origin: (46:1/132)