On 2019 Apr 04 12:53:58, you wrote to Maurice Kinal:

 >> Also on tne EuroPoint message "MSGID: 1:153/757.0 4e505c01" with "PATH:
 >> 153/757 250 770/1 280/464" is buggered up as well.  Bottomline is that
 >> it isn't your node that is buggering it up.

 AI> That is a quick path that I see here a lot. I chat at times with the
 AI> first two nodes in that path and haven't noticed any problems but
 AI> maybe I just wasn't looking. I'll investigate.

it'll be hard to see on a standard 80x25 terminal screen... if the terminal is
wider than 80 columns, it should be easier to see since it is forced
wordwrapping to fit within 80... i'd guess that 120x25 would work to try to see
 it as long as the BBS software doesn't try to format it for you on
transmission...

of course, having the raw PKTs would tell the real story, too... especially the
 one coming in and one going out where the message could be compared at a
digital level...

my old system used to archive both inbound and outbound PKTs specifically for
research like this... it is harder to do with my current setup on my main
system but it is something i've been thinking about doing and how to go about
doing it... i may have to (re)learn some C to do it, though... especially if i
do it the easiest and most direct way by adding the capability to sbbsecho to
copy the PKTs before processing the inbound ones after they are possibly
unarchived and then to also copy the freshly generated outbound PKTs before
they are placed into the BSO... hummm...

)\/(ark

Always Mount a Scratch Monkey
Do you manage your own servers? If you are not running an IDS/IPS yer doin' it
wrong...
... Yellowknife, a really cool place!
---
 * Origin:  (1:3634/12.73)