Subj : it is but it's a bit buggy here 'n there
To   : August Abolins
From : mark lewis
Date : Mon Mar 25 2019 23:19:18

 On 2019 Mar 25 19:32:38, you wrote to Martin Foster:

 MF>> - 5D addresses MUST be used, otherwise, WinPoint transmits invalid
 MF>> AKAs to the remote system and the result of that is that the remote
 MF>> system will boot you off.

 AA> Well... it *is* a point program, so.. to me that implies that it
 AA> *expects* to operate as a 5D machine, and communicate with a Boss(es)
 AA> only.   Every message it creates internally will be 5D.

ummm... 5D includes the FTN domain, guys...

  1D : node
  2D : net/node and node.point
  3D : zone:net/node and net/node.point
  4D : zone:net/node.point
  5D : zone:net/node.point@domain or domain#zone:net/node.point

the old 1D and 2D formats that leave off the zone and/or net are no longer used 
since the network has evolved to zones...

echomail seenby and path lines are (still) 2D (net/node)...

echomail origin lines are 3D/4D with the zone or one of the 5D formats...

MSGID/REPLY are 3D/4D with the zone...

in netmail points are denoted in the TOPT/FMPT lines if they are not 0 (zero) 
but a TOPT/FMPT of 0 (zero) should still work properly...

i just wanted to clarify the terminology...

)\/(ark

Always Mount a Scratch Monkey
Do you manage your own servers? If you are not running an IDS/IPS yer doin' it 
wrong...
.... And God said, "Ah, the hell with it, I'll just get an ant farm."
---
 * Origin:  (1:3634/12.73)

.