REPLY: 1:275/362.0 5c990e9c   
   MSGID: 1:3634/12.73 5c992ddc   
   PID: GED+LNX 1.1.5-b20180707   
   CHRS: CP437 2   
   TZUTC: -0400   
   TID: hpt/lnx 1.9.0-cur 07-09-15   
    On 2019 Mar 25 12:23:48, you wrote to All:   
      
    ON> Are the tearlines only added by the tosser? Or (as I see GoldEd do) is it   
    ON> okay for the Message System (BBS or in my case NNTP Service) to append the   
    ON> Tear line?   
      
   the message creation system can add tear lines... that would be the editor or   
   maybe the BBS software after the message is created and imported into the   
   message base when the user leaves the editor after saving the message...   
      
   tossers, being the last in line, can add tear lines if they do not already   
   exist... some tossers add a tear line all the time... some properly invalidate   
   existing ones and add their own... generally invalidating a tear line is   
   simply changing the center dash to an exclimation point... some tossers also   
   have the ability to retear which means replacing an existing tear line... i   
   used to use fastecho's retear to remove tear lines completely...   
      
   retearing was brought to us by the tear line wars... folks didn't want to be   
   called out for running unregistered software which was noted in the tear line   
   so someone came up with a tool to specifically retear and put what they wanted   
   on the tear line... this is where the PID and TID control lines came from...   
   instead of putting the information, registered or not, in the tear line, it   
   can now be hidden in the control lines...   
      
    ON> And, of course the next step down - * Origin... I noticed JAMNNTPd   
    ON> would double space in from of the original when reading or replying to   
    ON> the message. Any reason I should or should not follow their lead?   
      
   there sure is a reason... it should not be putting two spaces... that's an   
   invalid origin line... you need to check the code and see why it is doing   
   that... it wasn't when i was using it... check in the JAMNNTPD echo...   
      
    ON> And on a new post - okay if I add the Origin line too? Or is that a   
    ON> Tosser piece?   
      
   any software, from the editor back to the tosser can add tear and origin   
   lines... the key is if one already exists, it should not be messed with... but   
   operators have control over their systems and if they want to change these   
   lines, they can up to the point of the messages being packed into pkts for   
   delivery to other systems...   
      
   [trim]   
      
    ON> And per those two topics, if an editor appends the tear line and possible   
    ON> the Origin, should the BBS/NNTP re-tear?   
      
   it is not a "should"... it is up to the system operator but only to a point as   
   mentioned above... once packed and transmitted, other systems handling the   
   message must not alter them... there is a difference in how they are handled   
   during export and how they are handled on import or passing to other systems...   
      
   )\/(ark   
      
   Always Mount a Scratch Monkey   
   Do you manage your own servers? If you are not running an IDS/IPS yer doin' it   
   wrong...   
   ... Dancing: A perpendicular expression of a horizontal desire.   
   ---   
    * Origin:  (1:3634/12.73)   
   SEEN-BY: 1/19 120 15/0 2 16/0 18/0 200 19/36 34/999 90/1 104/57 116/18   
   SEEN-BY: 116/116 120/544 123/0 25 50 130 131 140 150 755 1970 135/300   
   SEEN-BY: 153/7715 154/10 203/0 2 124 211/37 218/700 220/60 221/0 1   
   SEEN-BY: 222/2 226/17 229/107 354 426 452 1014 230/0 150 152 240/1120   
   SEEN-BY: 240/5832 249/206 317 400 250/1 261/38 100 1466 266/512 267/155   
   SEEN-BY: 275/100 280/464 5003 5006 282/1031 1056 291/1 111 310/31   
   SEEN-BY: 317/3 320/119 219 322/757 340/400 342/13 200 393/68 396/45   
   SEEN-BY: 423/81 120 633/280 712/848 770/1 801/161 189 2320/105 3634/0   
   SEEN-BY: 3634/12 15 24 27 50 5020/715 1042   
   PATH: 3634/12 261/38 320/219 203/0 280/464 229/426