On 2019 Apr 04 20:03:14, you wrote to Alan Ianson:

 MK> @MSGID: 1:153/7001 5ca66303
 MK> @REPLY: 1:153/757.0 6dcfa5e3
 MK> Hey Alan!

 AI>> 153/7715 was the first node this area was connected to here when
 AI>> I setup this area so you will likely see that node in the path
 AI>> also.

 MK> I see it in the SEEN-BY but not in the PATH.  As far as the PATH is
 MK> concerned there is only you in the message I am replying to and it looks
 MK> unscathed.  It's  only messages from further afield where the message
 MK> body gets altered.

i see it here but GoldEd's reflowing corrects it... i would not have known that
 i was seeing it here if you had not mentioned that there's a space added to
the beginning of the line that's being force-wrapped by the intermediate
system... i've added the space back to the above... here it showed up before
"only"...

 AI>> Just as a point of focus for me, what changes are you seeing?

 MK> Shoddy word wrapping.  If I have to guess I'd say it was via one of those
 MK> NNTP gateways.  They are the usual source of longtime screwed up messages,
 MK> including  messing with datetime stamps as well as replacing valid
 MK> node numbers with their own.  Beats me what they see in that crap but
 MK> they shouldn't be allowed on a PATH given their track record.

in the above, it showed up before "messing"...

 MK> Life is good,
 MK> Maurice

 MK> ... Don't cry for me I have vi.
 MK> --- GNU bash, version 5.0.3(1)-release (x86_64-pc-linux-gnu)
 MK>  * Origin: Little Mikey's Brain - Ladysmith BC, Canada (1:153/7001)
 MK>  MK> 229/426
 MK>  MK>  MK>  MK> 123/50
 MK>  MK> @PATH: 153/7001 757 250 770/1 280/464 154/10 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...
... Grinin' Like A Mule Eatin' Briars.
---
 * Origin:  (1:3634/12.73)