Closed Winter closed 5 years ago
Winter
commented
5 years ago Apologies for creating a new issue, but I figured it may catch a little more attention if I were to create a new Open issue.
I may look into this option when I get home from work. XstReader seems quite promising.
Dijji
commented
5 years ago Hi
Actually, it makes little difference whether you open a new issue or comment on an existing one, I get notified of both.
However, in this case it is probably convenient to have a new issue, as I may be able to add a feature to meet your needs. It seems reasonable to me to be able to extract the properties that I show for a message or a contact as a CSV file, and by extension, a folder of messages or contacts as a multi-row CSV file. This would simply contain all the properties shown in the property window and their names and values, as shown there.
If this would suit, let me know, and I will add it to my work queue.
Dijji
catprisbrey
commented
5 years ago Dijji, thanks for the redirect to this issue. And yes, what you've described sounds perfect.
For my needs, a multi-row CSV with the contact properties would be perfect. Rebuilding lost contact lists from corrupt OST files has caused me issues on more than one occasion where users prefer a local address book. Using XstReader to open and old OST and pipe contact properties out to a CSV would solve my problem entirely I think. Microsoft has a CSV Contact template for easy contact importing, so if i could pull a CSV with XstReader, and pass that info into their template, I'd have the perfect recipe to solve the issue entirely.
Dijji
commented
5 years ago I have now released Version 1.4 supporting export of CSV files. Give it a go and let me know what you think.
Dijji
catprisbrey
commented
5 years ago Just tried out v1.4. That export option is awesome! I bet it'll work perfectly. My tests of the feature make it seem perfect.
I'm reaching out to some folks who lost their contact lists recently and I'm going to try using the exporter on their old OST to rebuild their contacts list and put it into an Outlook importable .csv file. I'm very excited about this.
Very fine work Dijji!
sutekh849
commented
5 years ago Would it be possible to add an option to export messages to CSV too? The present function works fine for contacts, but if you've got mail that failed to sync to the remote imap server in an ost file you need to recover (Don't ask) and try to export that, the output isn't readable by outlook's import CSV wizard.
Dijji
commented
5 years ago Actually, the current CSV output is not readable by Outlook for Contacts, either. You have to edit the columns and titles down to the specific ones that Outlook expects.
The same holds true for messages, except that the message body is not included in the CSV. However, if only a few messages are involved, you can use the CSV to retrieve blank messages into Outlook, then copy and paste the body from the mail body window in the viewer.
I have deliberately stopped short of providing a mass email export option, partly because there is no universal standard format to export to, and partly out of respect for the developers earning a living by writing and selling software that does the job (although I agree, their marketing practices are often highly dubious: there appears to have been an unfortunate competitive race to the bottom in this regard).
Dijji
Rather than attempting to create an entire PST file, which as mentioned in #1 is a lot of work; Just output to a CSV. Most* email clients are able to take advantage of CSV importing / exporting. The problem is we just can't open a lot of our OST/PST files which XstReader is able to pull data from.