----------------------------------------------------------------------------------
@TID: FMail-lnx64 2.3.4.1-B20260520
@RFC-X-No-Archive: Yes
@TZUTC: 0200
@CHRS: UTF-8 4
@PID: GED+LNX 2.0.0-b20260928
@MSGID: 2:280/464 6ad09252
@REPLY: 2:292/854 121c3d11
Hi Ward,
On 2026-10-15 09:20:17, you wrote to All:
WD> I do fly the PING-flag and try to have it followed-up correctly. But
WD> today something interesting occured.
WD> I do "not" fly the `TRACE`-flag, but someone sends me a trace on my
WD> 2:292/854
WD> anyway ... Now what? ... I`d say the system should remain idle.
I got one too... ;-)
WD> I don`t have the flag, hence I shouldn`t care about it.
WD> Second, what if a node "is" flying `TRACE` and gets a TRACE-request? Since
WD> the
WD> message stops there, is not passing through in other words, it shouldn`t be
WD> traced either and the receiving system can remain idle as well ...
There is no such thing as a TRACE request! `TRACE` is not a defined destination
adres that should generate an auto-response.
The trace flag means the system where a PING request passes through,
auto-respondes to the sender with a "Trace" response.
http://ftsc.org/docs/fts-4010.001 Paragraph 3; TRACE.
Bye, Wilfred.
--- FMail-lnx64 2.3.4.1-B20260520
* Origin: FMail development HQ (2:280/464)
SEEN-BY: 2/29 1000 103/705 124/5016 153/757 154/10 30 203/0 221/0 1 229/426
SEEN-BY: 240/1120 5832 263/1 280/464 1043 5003 5006 5555 292/789 854 8125
SEEN-BY: 301/1 310/31 335/364 341/66 234 396/45 400/2992 410/9 421/79 790
SEEN-BY: 423/120 460/58 463/68 469/122 633/280 712/848 770/1 5001/100 5015/46
SEEN-BY: 5020/290 545 715 1042 1146 5452 8912 9696 5022/2 5023/24 5030/1081
SEEN-BY: 5030/1997 5034/13 5051/44 5060/900 6035/3 6090/1
@PATH: 280/464 292/854 5020/715