ml> FWIW: i found out when working with a WWIV system way back... it had to
ml> do a double toss to get FTN mail into the system... the first toss was to
ml> MSG format and the second toss was from MSG to WWIV's internal format...
ml> the WWIV tool refused to import the MSG files created by (IIRC) FMail
ml> being used by that system... after weeks and weeks of trying, that
ml> operator finally asked me if i could come out and help figure this out...
ml> after some time learning the process, a quick look with a hex editor
ml> showed the MSG files just terminating with no 0x00 or EOF... i wrote a
ml> quick utility that added a trailing 0x00 to each MSG file and the WWIV
ml> tool was happy as a lark on a summer's day with those MSG files which it
ml> ate and pumped into the WWIV message format... reading the specification
ml> of a stored message in FTS-001, it was easy to see why the WWIV tool
ml> wanted that ending NUL character ;)

That is still how I do it today.. :)  D'Bridge creates the *.MSG files,
WWIVTOSS converts them to native WWIV format and writes them to the message
bases.

Same thing happens in reverse when posting (like this message).

- Mark

--- WWIVToss v.1.51