• 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.

And, when the Exchange client stores the email message, for example, when Outlook writes the message in the PST file, the client often stores the Exchange-style address only. The SMTP version of the email address is simply not written in the message record.

When you go to migrate this email to another email app, this can be a problem if you are not moving your mail to another Exchange server environment. Maybe you are converting an old PST file to something you can read in Thunderbird or Gmail, for example. The problem is that the original SMTP address is not in the source data and there is no direct mapping of the Exchange-style address to a SMTP address. So, Emailchemy handles this 3 different ways:

1) Include the Exchange-style addresses as-is. This preserves the original data, but the address won’t be routable by SMTP in downstream processing, of course. And, it might actually cause some email clients to not render the message correctly.

2) Try to convert it to SMTP-style. Emailchemy will create a valid-formatted SMTP address out of content found in the Exchange-style address. It will look like user@company, where company will be the org name from the Exchange address, but it won’t have a .com or .net at the end and the address won’t be routable. In our example above, it would generate joebob@somecompany. This will keep downstream email clients from breaking, and you’ll have an idea who this is, but you won’t be able to send email to this address.

These first 2 options are selectable in the Emailchemy GUI and CLI. This last one is in the API only.

3) Emailchemy’s API has a callback function that you can implement to do a lookup of the SMTP address in an Active Directory server

• Excludes RSS feeds from Apple Mail conversions
• Fixed registration issue on Solaris 11
• Improved IMAP server performance
• Improved compatibility of IMAP server with Outlook 2010 for Windows

RSS feeds in Apple Mail are now stored as mail archives, which is confusing, because RSS feeds are not email messages. So, just as Emailchemy ignores Usenet newsgroups (some older email clients included them – kids, ask your parents), Emailchemy now ignores the RSS feeds.

The registration issue on Solaris 11 was interesting, since fixing it required figuring out how and where to install Solaris 11 for testing. It turns out it’s pretty easy to get it running on Oracle’s VirtualBox.

Emailchemy’s embedded IMAP server had an issue with Outlook 2010 for Windows only, when nested folder paths exceeded a length of 115 characters (which is a lot longer than it sounds). So if you were trying to use the IMAP server with Outlook 2010 but it was stalling at deeply nested folders, please try it now.

A few users have recently complained that the IMAP server is slow. It’s not meant to be a high-performance mail server; it only implements enough of the IMAP spec to allow you to download email from it. However, we did improve processing speed a bit by making some changes to how the server breaks a tight loop (to give other processes time to execute).

• Better handling of AOL HTML content
• Entourage converter now includes and identifies both original and user-edited subjects
• Fixed blank attachment names from PST files
• Improved handling of corrupt Claris Emailer 2 databases
• New option for manually deleting the Google Apps Uploader history file

This is a free update for all current v11 users. For users of older Emailchemy versions, the upgrade is free if you purchased after June 17, 2010 (within 1 year of the release of v11). If you purchased before June 17, 2010, send us an email to get a 50% off renewal coupon.

The bugs that were fixed were only a problem in very rare cases, for example, if you were converting Japanese emails with extremely long subject lines, or if you were converting Outlook Express 4 for Mac files where the mail folder names had a slash (“/”) in the name.

Work continues on the Outlook 2011 native converter, and in this release there is a converter for the new .olk14MsgSource files. The rest of the format will be done in a coming soon release. For now, you can use the Outlook 2011 for Mac OLM file converter to get your mail out of Outlook 2011.

This version of Emailchemy MemoryBoost adds compatibility with 64-bit Java running on 64-bit Windows, and the executables are now signed so Windows will let you run them more easily. Emailchemy MemoryBoost remains completely free.

We also recently released 11.0.1 which added support for using Emailchemy’s built-in IMAP server with Apple Mail 5. We don’t normally like doing 2 releases in a single week, but the 11.0.1 went out quickly with a fix to help a customer who was dealing with some corrupt Apple Mail folders.

Use the coupon code V11PROMO before June 19 to save $18.95 off the regular price. That means you can get the Personal Edition – Individual license for just $11!

• Improved IMAP server performance – faster imports
• New Google Apps Uploader feature to fixes Gmail’s Sent folder for uploaded mail
• New option for better handling of international characters in folder names

The new Google Apps Uploader feature requires a bit of an explanation. In Gmail, there is no notion of a “Sent” folder. Yes, there is a link you can click that says “Sent Mail” which will show you mail that you sent, but it’s not a folder in the sense that there are specific messages put into a container (i.e. a folder) of messages. The subtle though important difference in how Gmail’s Sent Items link works is that it does a real-time search of all your email messages and shows you a list of all of the messages that have your gmail.com email address (or Google Apps address) in the “From: ” header. Effectively, this is the same as having a real “Sent” folder, but it breaks if you try to import messages into Gmail.

Why? Because if you are importing email into Gmail (or Google Apps), the email you have sent from your previous mail accounts will have your old email address in the “From:” header field of each sent message and they won’t show up in the search results you see when you click the “Sent Mail” link in Gmail. As far as Gmail is concerned, they just aren’t “sent” messages.

So, when you do see your old sent messages in Gmail, Gmail will think they are received messages and display them as such in the list, showing your old email address in the “name field of the message list (because you were the sender, remember).

Gmail only shows three fields in the message list: the sender, the subject and the date — and you can’t change this as you might be able to in Outlook or Thunderbird. Sure, Emailchemy can upload your sent messages into Gmail and then tag them with the name of the folder they came from, so these messages appear to be in a folder called “Sent Items” or “Sent”, but Gmail will still display these messages with the same 3 fields: sender (you), subject and date. Not helpful at all when you are trying to find an old email you sent to your boss.

In Emailchemy 10.1, we introduced a new option on the Google Apps Uploader tool: “Re-write sender of messages in ‘Sent’ folder to force them into Gmail ‘Sent Mail’”. When you check this box, Emailchemy will change the “From:” field of all your sent messages to contain your new Google Apps email address. Then, “Sent Mail” will work as it should, showing all your old sent messages too. This option has been added to the command line version of the Google Apps Uploader too.

Emailchemy 10.1 is a free update for all licensed users of Emailchemy 10.0.

• CompuServe for Windows (WinCIM)
• Outlook .MSG files
• Outlook for Mac versions 8 & 2001 (not 2011)
• Outspring Mail
• Windows Live Mail
• Windows Mail

It’s important to point out that the Outlook for Mac support we’ve added is only for the very old versions of Outlook for Mac and not for the new version just released in Office 2011 for Mac. These were versions of Outlook for Mac that existed before Entourage, and they used a variation of the PST file for storage. We are working on the Outlook 2011 for Mac formats and hope to release support for them soon.

We’ve also simplified the download and install process by no longer requiring you to log-in to a web site to download updates. Now, just download the update directly from the main Emailchemy web page.

Emailchemy version 10 is a free update for anyone who bought Emailchemy in the past 12 months.