Hello Wilfred,

 WV>  PATH: 266/512 261/38 153/757 221/6 1 280/464

 WV> So maybe it broke passing through 261/38. Janis had some problems this
 WV> week...

I went looking and I discovered a couple things..

That message is intact at 261/38, it was also forwarded to 222/2 and it is intact there. What the cause is of my copy being short and missing path and seen by lines and tear and origin line I am not sure.

There are two copies of that message at 261/38. A second short copy of that message arrived at 261/38 with a new origin line, "* Origin: -Somewhere- (1:266/512)". I think the message was changed at 301/1 and that's why it was tossed again.

There were also two copies of my post to you. One of the copies that passed through 301/1 had quoted seen by lines removed. Those quoted lines looked like this..

ML>>> > SEEN-BY: 123/456

More questions than answers. It seems now that that short post happened here. I don't have the input .pkt to examine, so I am not sure how it compares to the original message.

I am copying inbound files to a backup directory now but it is rather crude and doesn't take filename collisions into account. If need be I hope I can find the inbound packets in there to examine.

 Ttyl :-),
         Al

--- GoldED+/LNX 1.1.5-b20180707