Paul,
> You're confusing two issues. OPIM is Entourage's _creator_ code, not the
> file type. The creator code is not the problem. The file type Entourage uses
> is MBOX, whereas the file type Eudora wants is TEXT. Yes, it is a text file,
> but of a very special type. If you try importing 1 million other TEXT files
> into Eudora, which don't happen to be constructed as mbox format but are
> just plain old text files, or BBEdit files, or BinHex files, all of which
> are TEXT files, it won't work. That's what's ambiguous. Since the only type
> of text file that works is one in MBOX format, it should be honest and say
> that it wants MBOX files. Entourage does the right thing by not being vague,
> but precise.
Thank you very much your excellent explanation. I realize now why I couldn't
complete the import: I was changing the creator code to TEXT rather than the
file type. I'm embarrassed, as I do understand the difference, at least now that
I see that I had everything backasswards.
> Entourage has now done all the work to make exporting into a
> common standard format. If the Eudora developers want to make it easy for
> users to switch to Eudora (as you'd think they would), they should specify,
> or at least allow, the proper MBOX filer type to be recognized. Go complain
> on the Eudora mailing list. This is the wrong place.
Point taken. I just know that if I ask Steve Dorner at Eudora or Rich Siegel at
Bare Bones (which makes Mailsmith), I'll get another perspective that makes
sense. But I will in fact bring it up with them and see what they say.
But I'm glad to have your explanation and it does make it possible for me to
solve my immediate problem. Thank you for taking the time.
Will
____________________________________
P O L Y T R O P E * Houston, Texas
--
To unsubscribe: <mailto:[EMAIL PROTECTED]>
To search the archives:
<http://www.mail-archive.com/entourage-talk%40lists.boingo.com/>
