10 Apr 20 14:18, you wrote to Paul Hayton:

 WV> Hi Paul,

 WV> On 2020-04-10 14:13:52, I wrote to you:

 PH>>> @MSGID: 3:770/100 651d79ff

 PH>>> @PATH: 770/100 1 317/3 229/426 292/854 261/38 801/189 188
 PH>>> 292/854

 WvV>> Or is this a hickup on that system that shows up twice in the
 WvV>> path?

 WV> It was. I noticed there already was a message in this area with the
 WV> above MSGID... Sorry for the noice. ;)

Interesting. At least two nodes in fsxnet received bad packages with scrambled
messages. The origin line of 292/854 were in the To, From or Subject field.
There were also some empty messages in this area with 2:292/854 in the origin
line, but otherwise completely empty. But how do we know that 292/384 is
causing the problems? It could be 261/38 too (less likely though).

Btw, 4:801/189, which is in the path between 2:292/854 and 2:292/854, is
running an older version of Mystic that
- writes incorrect SEEN-BY lines
- ignores SEEN-BYs
- modifies mails in-transit (line breaking)
- doesn't recognized modified and unmodified mails with the same MSGID as
dupes.

Using something like this with fidoweb-style echo routing has to create some
problems at some point. Like loops and dupes.