TZUTC: -0700   
   MSGID: 740.net_dev@1:103/705 21f12ed0   
   REPLY: 2:335/364.1 5d8b71b4   
   PID: Synchronet 3.17c-Win32  Sep 21 2019 MSC 1922   
   TID: SBBSecho 3.10-Linux r3.141 Sep 24 2019 GCC 6.3.0   
   COLS: 80   
   CHRS: CP437 2   
   NOTE: FSEditor.js v1.103   
     Re: Node originating a message   
     By: Fabio Bizzi to Wilfred van Velzen on Wed Sep 25 2019 03:53 pm   
      
    > Hello Wilfred!   
    >   
    > 25 Sep 19 15:39, you wrote to me:   
    >   
    >  NA>>> The PATH.   
    >   
    >  FB>> Many Thank, but now I have to ask how to get the Zone? :)   
    >   
    >  FB>> In the path you have the first node that is the originating node   
    >  FB>> plus all the traversed nodes, but it's without the preceding   
    >  FB>> zone.   
    >   
    >  WV> That's another reason why you shouldn't use the PATH... ;)   
    >   
    > Ok, but:   
    >   
    > - The PATH can be cleared   
    > - The MSGID is not mandatory and can be omitted   
    > - The Origin can be forged   
    > - The Headers can be forged   
    >   
    > So, how can I determine the originating node of a message? :D   
      
   If you're referring to EchoMail, then FTS-4 is the spec (http://   
   tsc.org/docs/fts-0004.001) and it instructs you to use the Origin line to   
   determine where a message originated.   
      
                                               digital man   
      
   Synchronet/BBS Terminology Definition #19:   
   DOCSIS = Data Over Cable Service Interface Specification   
   Norco, CA WX: 83.3øF, 53.0% humidity, 14 mph ENE wind, 0.00 inches rain/24hrs   
   --- SBBSecho 3.10-Linux   
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)   
   SEEN-BY: 1/123 15/2 18/200 103/705 154/10 203/0 218/700 221/0 227/114   
   SEEN-BY: 229/354 426 1014 240/5832 249/206 317 280/464 5003 292/854   
   SEEN-BY: 310/31 317/3 322/757 342/200 396/45 423/120 633/280 712/848   
   SEEN-BY: 770/1   
   PATH: 103/705 280/464 229/426