20 Feb 97 07:22, Ronald Hoekstra wrote to andrew clarke:

 >> What you're experiencing is normally attributed to storing your 
 >> messages in JAM format, but since Msged doesn't currently support JAM 
 >> message bases that pretty much rules that theory out.  I can only 
 >> assume Paul's message was damaged in-transit.  A rescan of a JAM base 
 >> could have caused this, or perhaps a broken packet sorter or mail 
 >> processor.

 > Hmm... The only jam-like thing in my config is that FastEcho does 
 > support JAM... But I'm not using it.

One of your uplinks (or their uplinks, etc.) might be though.  If they did
a rescan of this echo from a JAM base you may have had the control lines of
some messages re-ordered on you (without knowing they were reordered),
resulting in damaged mail.  At least, that's one theory.

Regards
Andrew

-- randy{at}zws.com

--- Msged/2 4.20 beta 2