@MSGID: 2:280/464 6929d307
@REPLY: 1:154/10 6929cb1a
@TID: FMail-lnx64 2.3.2.4-B20240523
@RFC-X-No-Archive: Yes
@TZUTC: 0100
@CHRS: CP850 2
@PID: GED+LNX 1.1.5-b20240604
Hi Nick,

On 2025-11-28 10:15:04, you wrote to me:

 >> The simplest fix is to not create empty PATH lines at all (with or
 >> without space)! ;-)

 NB> Is /not/ creating a PATH kludge covered anywhere in the holy grail of
 NB> documented standards and/or proposals?

 NB> So far, all that has been pointed out is a document that shows the proper
 NB> format of the PATH kludge.

fts-0004.001 says it`s not required.

fsc-0074.001 says:

    -  Shall contain a list of net/node numbers.

    -  Shall identify at least one net/node number.  "Blank"
       path lines shall not be transmitted.

So that is pretty clear to me! ;-)


Bye, Wilfred.

--- FMail-lnx64 2.3.2.4-B20240523
 * Origin: FMail development HQ (2:280/464)
SEEN-BY: 19/10 50/109 103/705 104/117 124/5016
134/101 153/757 154/10 30
SEEN-BY: 201/0 203/0 218/840 221/0 1 6 360
240/1120 5832 263/1 280/464 5003
SEEN-BY: 280/5006 5555 292/854 8125 301/1 310/31
320/119 219 335/364 341/66
SEEN-BY: 341/234 396/45 423/81 120 460/58 463/68
633/280 712/848 770/1
SEEN-BY: 5000/111 5015/46 5020/400 715 846 848
1042 4441 12000 5030/49 1081
SEEN-BY: 5058/104 5060/900 5061/133 5075/128
5083/444
@PATH: 280/464 221/1 6 5020/1042 4441