MSGID: 2:221/1.58@fidonet d7802161   
   REPLY: 1:3634/12.73 5cb68c36   
   PID: OpenXP/5.0.38 (Win32)   
   CHRS: ASCII 1   
   Hello mark!   
      
   ** 16.04.19 - 22:15, mark lewis wrote to August Abolins:   
      
   AA>> @MSGID: 2:221/1.58@fidonet d7782048   
   AA>> @PID: OpenXP/5.0.38 (Win32)   
   AA>> @CHRS: ASCII 1   
      
   AA>> This message should have a customized origin text specific just for this   
   AA>> echo.   
      
   AA>> ---   
   AA>>  * Origin: [++++++++1+++++++++2+++++++++3+++++++++4++++++++5++++]   
   AA>> (2:221/1.58)   
      
      
   Thank you for that.  As you could see, I was just exploring oxp's custom     
   origin settings.  Apparently, I can create a different one for each     
   particular area or echo.   
      
   In the original message I was testing the max char limit according to the     
   program.  Apparently oxp is very smart and precalculates the limit based     
   on the total chars with the nodenumber at the end so as to not exceed the     
   total 79 char limit for that line as per the ftsc-0074 and therefore "fit"     
   perfectly.   
      
     ../|ug   
      
   ---   
    * Origin: [++++++++1+++++++++2+++++++++3+++++++++4++++++++5++++] (2:221/1.58)   
   SEEN-BY: 15/2 123/1970 203/0 221/1 6 360 226/17 229/107 354 426 1014   
   SEEN-BY: 240/5832 249/206 317 400 280/464 5003 292/789 854 8125 317/3   
   SEEN-BY: 322/757 335/364 342/200 393/68   
   PATH: 221/1 292/854 229/426