![]() Upgraded from very old *.pst formats until the 2007 version. I have another solution that works for a large e-mail database I have gathered from 1985 until now. In that sense, having an export feature or using a standardized email storage format would potentially increase the number of em Client users as making the switch would require less risk on the users part. What if I find that I don’t like em client, that em client development is stopped, the company shuts down, I switch operating systems, etc? I’m not willing to take that chance, so I’m not going to switch to em Client, even if em Client is a far superior product in every other way. If I import my mail archive into em Client, I’m stuck with em Client or I sacrifice my email archive. It also doesn’t use an existing well defined email storage format so I can’t use other standards compatible applications with its mail archive. em Client isn’t open source, so I can’t just grab the source and create an email converter, if I were so inclined. ![]() I’ve not heard of any 3rd party support for em client similar to that which exists for Outlook/PST. ![]() Both of these provide options for ‘getting my mail back’ even if they don’t have an export menu item. Thunderbird is open source and uses an RFC defined format to store the mail archive. Outlook uses the PST format, which is very widely supported - import features of other email clients, third party utilities, etc. I know this seems like you’d be building a feature to allow people to more easily leave your software, but it’s actually the opposite.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |