So you’ve converted all you mail and imported into your new email app and everything looks fine. But when you open up one of your old sent folders and you see a list of messages that show the From column instead of a To column.
Your new email app doesn’t know that your old sent mail folders are sent folders, that’s all, and it’s easy to fix. Just change the view options or column settings for those folders to show the Recipient (or To) column instead of the Sender (or From) column.
You should be getting at least a message per second, but sometimes the upload seems to be unbearably slow. There are a number of factors that could be limiting the speed of the upload:
- The speed of your home internet connection uplink is much slower than your downlink. Most home users have between 256kbps (kilobits per second) and 1mbps up, regardless of how fast their download speed is. A speed of 256kbps would give a max upload speed about 32K (kilobytes) per second. If you aren’t sure what your uplink speed is, try a network speed test here: http://www.speakeasy.net/speedtest/
- Google imposes quotas and throttles on the upload of messages, but it never says exactly how much. Basically, Google doesn’t want you to upload too many messages per minute nor too many messages per day. So, if the uploader is going too fast, or if Google’s upload servers are too busy, Google will start rejecting messages with a “service unavailable” message. When this happens, Emailchemy waits a second and then retries the message upload. If you exceed the max allowed for a given 24 hour period, no amount of retrying will work until the quota resets.
- The Google message upload protocol is also a bit wasteful in that as a confirmation to each message uploaded it sends the entire message back to the upload program. This isn’t a huge problem for small messages, but, especially if you have attachments, it can add up.
- Anything else your internet connection being used for while doing the upload will impact the performance too. So, a good thing to do is to avoid file downloads or any kind of streaming from the internet to computers on your home LAN at the time you are doing the upload.
I’ve seen this happen when the RGE files were created on the Windows PC and then moved to the Mac. There are certain methods of moving files between Mac and PC that can screw up the encoding of the linefeed character.
Try this method instead:
1) copy your PST files to your Mac
2) run Emailchemy and convert Outlook PST to Entourage Archive (.rge files)
3) run Entourage and use its import wizard and import the .rge file you created in step 2
The “garbage” is likely the base64-encoded attachments — which is the standard behind-the-scenes way of including attachments in a message. Most modern mail programs interpret this raw information correctly and display the attachments either inline or as icons within the message. Simple text file viewers will likely not display these attachments correctly.
Some email programs will show the date you imported the converted mail as the date for each message in the message list. This is usually incorrect behavior of the new email application because it is trying to find a “received” date and not finding one.
To fix this, change the displayed columns in your email program to show “sent” date instead of the “received” date. The sent date is the real date of an email message per the RFC-2822 specification. There is no specification for received dates and every application interprets the idea differently.
The simple answer is “yes, but indirectly.” For example… Does Emailchemy create Outlook PST files? No, but it creates files that can be imported into Outlook.
Emailchemy converts email to open, standard formats (and a few variations) which are directly importable by most modern email programs. These formats are all based on the RFC-2822 Internet Message Format for maximum portability and compatibility. The core 3 formats are:
.eml : a file with a single RFC-2822 message in it
mbox : a common mailbox format that contains one or more RFC-2822 messages
maildir : a common mailbox format that is made of directories (folders) of RFC-2822 message files
All modern email software can either import one of these standard formats or at least be tricked into importing it with Emailchemy’s ImportServer tool.
A complete list of supported formats can be found on the Emailchemy web page and in the Emailchemy User Manual. The User Manual also has instructions for importing the converted mail into many modern mail programs.
The IMAP ImportServer, a part of the Emailchemy Toolbox, is designed for helping you to import your converted mail into all email programs. This tool hosts converted mail on an embedded mail server for your new mail program to download it from. See the Emailchemy User Manual for more information.
A complete list of supported email formats can be found on the Emailchemy web page and in the Emailchemy User Manual. Support for new formats is typically released in new major versions of Emailchemy.
The demo version of Emailchemy masks the subject and sender of each message with a “nag” message like “Please purchase Emailchemy”. This enables you to see that Emailchemy can convert all your email before you purchase.
If you are still seeing these “nags” after you purchase, it usually means one of two things:
1) You have not entered your license key and are still using the demo version.
2) You are using files created by the demo version.
There are a few things you need to do after purchasing a license for Emailchemy:
- (optional, though recommended) Delete the messages and files created by the demo version of Emailchemy. Do NOT delete your original email files.
- Launch Emailchemy and register it by entering your license key on the Register window (look for it in the Help menu if it doesn’t pop up on launch).
- Run your conversion again, starting with the ORIGINAL email files, so that the full version of Emailchemy can now fill-in the email header fields that were blocked in the demo version.
Yes, but you or your clients will require the proper licensing. Emailchemy’s End User License Agreement for the Personal Edition of Emailchemy states one email user per license.
We do offer Technician, Site and Migration Editions for organizational use and bulk migrations. If you have questions or need a quote, please contact firstname.lastname@example.org.
No. Emailchemy requires a modern version of Java to operate, and Apple stopped developing Java for OS 9 in the year 2000. However, Emailchemy can convert email files from Mac OS 9 email applications on any current system (Mac, Windows, or Linux), so simply transfer your email file to another computer and run Emailchemy there.