"Avon -> Adept" <
0@101.1.21> wrote:
For Avon to do troubleshooting -- quoting of the entire message
plus kludge.
@PATH: 1/126 100 4/100 2/100
Thanks for this, yep it's come via NET 4. And Al also mentioned his
looked amiss. I'll check on NET 4 tonight when I can and see how the message displays in 4/100. Will keep everyone posted.
I know Dan has had some issues with the HUB and I wonder if some of
the JAM bases are in some way corrupted?
I although considered a corrupted JAM base as the cause of the problem, but I couldn't figure out how this could lead to this scrambled messages. I'm assuming that NET 4 uses Mystic only and no other tools are involved in processing the messages.
The first question that comes to mind: does the Mystic tosser route echomail in
one pass? Or does it import the messages to the JAM message base and than exports it from JAM and forwards it to other nodes?
If it's one pass tossing how is the JAM base involved?
Or do some (corrupted) mails appear as not scanned in a (corrupted) JAM base and gets exported?
How is it possible that a message is exported with the correct header and kludges but part of the end of the same message appears at the top?
In JAM the text body of a message is stored in the .jdt file. Header, kludges, SEEN-BY lines and a pointer to the position of the text in the .jdt file is stored in the .jdx file. So if a pointer is pointing to a wrong position I would expect more random errors and parts of two messages or more messages put into one.
Maybe it's a JAM base corruption, but I don't find a plausible explanation for this kind of scrambled messages.
---
* Origin: (21:1/151)