Re: I need classic outlook
My advice is to get your email out of that proprietary format as soon as possible, and into something easier to work with, like plain text.
It's a beautiful dream, but Outlook's export mechanisms are rubbish (let's see — I have a choice of CSV or ... another PST?). And while plain text is fine for, well, plain text (assuming you can get it exported in Unicode, because Not Everything Is ASCII), it's not a ton of help when half a zillion of your interlocutors insist on using RTF. (Let's assume we can lump HTML, or The Thing That Microsoft Office Calls HTML Even Though It Really Isn't, in with "plain text".)
And then there's the problem of attachments.
And after that, there's the problem that Outlook actually stores a bunch of not-actually-email things, such as calendar items, task items, journal entries, contact-list information, and so on. Maybe the user needs to keep some of that stuff too. I have a ton of historical information in Outlook PST files which I occasionally have reason to refer to. It's important perhaps a few times a month — which is often enough to be quite important indeed. And, yes, you can represent those in plain text, but you'll want to know how they're going to be represented so you can find them later and do useful processing on them.
Outlook's capabilities for organizing and retrieving information are moderately to severely terrible, but it does have them. Any export process is going to need to be able to duplicate those. Sure, if I have everything exported to, say, mbox format,1 I can happily grep and awk and whatnot all the day long. But that does rely on my knowing how those messages have been exported. And it probably involves doing some scripting to split mbox files up and that sort of thing.2
So exporting all that historical Outlook data — mine goes back to 1996 (including, I am amused to note, "to do" items from at least as far back as 2002; must get on those soonish) — looks like a fairly major job.
1And mbox is horrible too. It really only exists because BSD Mail was invented before BSD had a fragging filesystem, and disk space was a really scarce resource then, so small files were excessively expensive, and emails tended to be small because accurséd MIME hadn't been invented yet. Really each message should be its own file, and the collection should be organized using a hierarchy of directories; that's the whole damn point of a hierarchical filesystem. Putting multiple messages in a single file these days is just stupid.
2Oh, I'm sure there are any number of open-source Perl and Python packages to split mbox files. Unfortunately, those would require either Perl or Python. I'd rather write my own stuff from scratch than use someone else's Perl or Python code.3
3This.