To test this for yarn I inserted a ^Z in the middle of my inbox file -
brave soul that I am. Yarn not only did not recognize most of my mail
messages, it went nuts in a typical way: Prior to inserting the EOL,
my inbox file was perhaps 3K in size. After the EOL, yarn inserted a
million null characters in the file, increasing its apparent size to -
over 11Megs!
I also fixed this in a typical way for me: I deleted all null characters
from the file, and made sure all end of line characters were Unix style
newline characters only. Then I did a search/replace, inserting the file,
From
before all (message separating) lines that began with one or more control
characters and continued with the word, "Received:". I also deleted the
initial control characters. Now I had a file, roughly in Unix mail
box format. I then imported this file into yarn with:
import -r filename <RETURN>
This gave me all my messages back. I did not find the yarn utilities,
unfolder or editfold helpful in editing or repairing the damaged inbox
file, although I tried them.
In Unix mailbox format, statuses like read, new, saved, etc. are indicated
with a line in the message header that starts with Status: I dont know
if yarn uses this same line to track the status of its mail messages.