Sanford Whiteman wrote:
Extra  x-  headers  within  the  body in the plain-text BOX, which are
dynamically  relocated  to  the headers when read by NetMail? And thus
create  a  mangled result when reindexed and read as IMail MBXen? That
sounds pretty unlikely, no?

yes, it did; hence why I said "at first glance"
Make  sure  that  any  lines  beginning  with  'From ' in the body are
escaped   to  '>From  '--perhaps  what  you're  seeing  are  truncated
messages.  Unless  NetMail  between 2.6 and 3.1 stopped using anything
that could remotely be called an mbox format.


I have confirmed this to be the problem; while building the .UID file, any line in the MBX file that begins with 'From '  is considered to be the beginning of a new message; thus creating message fragments.  I seem to recall that one of the 'rules' about the mbox format  was that there be a blank line between the end of one message and the beginning (the 'From' line) of the next message.  If this is so, then iMail is ignoring this rule; in most of the fragments I encountered, the line before the one that begins with 'From' is NOT blank.

Basic logic of the program is use a re-directed DIR to create a list
of  NetMail .BOX files, then have the program fetch a file name, and
regurgitate  it  as  an  iMail  .MBX  file  with  the  problem areas
repaired.
    

Still don't think this requires any programming, but it's up to you.

For the true 'From' lines, the format is exactly the same, so no editing is needed there.  A simple search ('From ') & replace (' >From ') would cure the fragmentation problem, as long as there's no encoded file attachments containing the string 'From '.  My luck is that there would be one; one of my users has > 300MB of archived mail.. Mr. Murphy would never pass up a chance like that.

-- 
----------------------------------------------------------------
Bud Durland, CNE     [EMAIL PROTECTED] fax: 518-561-0017
----------------------------------------------------------------
For sale: Parachute.  Like new, used once.  Small stain.
----------------------------------------------------------------


Reply via email to