Hello!


This message should have a customized origin text specific just for this echo.


../|ug

---
* Origin: [++++++++1+++++++++2+++++++++3+++++++++4++++++++5++++] (2:221/1.58)

On 2019 Apr 16 19:58:00, you wrote to All:

@MSGID: 2:221/1.58@fidonet d7782048
@PID: OpenXP/5.0.38 (Win32)
@CHRS: ASCII 1
Hello!

This message should have a customized origin text specific just for this echo.

../|ug

---
* Origin: [++++++++1+++++++++2+++++++++3+++++++++4++++++++5++++] (2:221/1.58)
SEEN-BY: 57/0 153/105 135 250 757 6809 267/67 800 280/464 290/10 317/2 393/68
SEEN-BY: 770/0 1 10 100 330 340 772/0 1 500 3634/12 116/116 123/25 50 120 150
SEEN-BY: 123/755 135/300 153/7715 261/38 3634/15 24 27 50 0 18/0 123/0 1/120
@PATH: 221/1 280/464 770/1 153/250 757 3634/12

)\/(ark

Always Mount a Scratch Monkey
Do you manage your own servers? If you are not running an IDS/IPS yer doin' it wrong...
... How do they get the deer to cross at the signs?
---
* Origin: (1:3634/12.73)

Hello mark!

** 16.04.19 - 22:15, mark lewis wrote to August Abolins:

@MSGID: 2:221/1.58@fidonet d7782048
@PID: OpenXP/5.0.38 (Win32)
@CHRS: ASCII 1

This message should have a customized origin text specific just for this AA>> echo.

---
* Origin: [++++++++1+++++++++2+++++++++3+++++++++4++++++++5++++]
(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)