Tag Archives: Outlook

Emailchemy 13.1 Released

software-updateEmailchemy 13.1 introduces a new output format: Outlook for Mac OLM files. By converting directly to Outlook OLM files, users of Outlook for Mac 2016 will finally have a way to import mail without having to use Emailchemy’s built-in IMAP server. Emailchemy’s Outlook OLM files can be created on Mac, Windows or Linux and Outlook does not need to be installed.

We have successfully tested Emailchemy’s Outlook OLM files with Outlook 2011 and Outlook 2016. However, please note that the import of Outlook OLM files can take quite some time. For example, importing a 5.5GB OLM file into Outlook 2016 on a brand-new MacBook Pro took about 10 minutes.

Emailchemy 13.1 is a free update for Emailchemy 13.0 license owners.

Emailchemy 13.0 Released

software-updateEmailchemy 13.0 is now available for download. It includes several new converters and a powerful new message filtering capability. Emailchemy 13 is a free upgrade for current license holders. If your license is more than 1 year old, you will be able to use Emailchemy 13 by purchasing a license renewal (contact support for details).

The new formats are:

  • AOL for Mac (v3 and newer)
  • AOL Desktop for Mac
  • Apple Mail v9 (El Capitan)
  • CompuServe v3 and v4 for Windows
  • Outlook 2015/2016 for Mac

As always, Emailchemy converts the emails from these applications – not the tasks, notes, contacts, calendar, rules or whatever else. The email organization (the folders) is preserved in the conversion, and in all converters but AOL for Mac, attachments are preserved as well.

The new filtering capability is pretty cool. The filter is now a step in the Conversion Wizard tool. If you don’t want to use it, select “Convert All Messages” and Emailchemy will work as it always has. Otherwise, it works a bit like how you might setup filtering rules in your email application.


First, select which attribute you want to filter on in the first dropdown on the left:

  • Date Sent
  • Folder Name
  • Sender
  • Recipient
  • Subject

Then, select how you want to match the attribute in the first column. The matching operators you can select here may be different depending on the attribute.

For Date Sent, you can choose:

  • is the date
  • is on or after
  • is before

For all other attributes, you can choose:

  • contains
  • begins with
  • ends with
  • does not contain
  • is equal to

Finally, enter the date or text you want to match on and your rule is complete. If you want to add another rule, click the “+” button at the end of the rule. To delete a rule, click the “-” button at the end of the rule.

Look for a blog post soon for examples.

We need your help to nail down an Outlook 2011 bug

computer-bugAs we’re building new features into Emailchemy, we’re also trying to fix all open bugs. There is one bug that is proving to be quite elusive, though. Some users have reported that after using Emailchemy’s Outlook 2011 Native converter, some messages with non-English characters do not render correctly. That is, they see question marks or incorrect characters in place of a German umlaut-o or the Swedish A with a circle above it.

The bug seems to be isolated to messages that were imported into Outlook 2011, as opposed to having been downloaded directly from a mail server. The workaround now is to export your Outlook mail to an OLM file and then have Emailchemy convert that, but we really want this to work natively. So far, our attempts to re-create this bug have failed, and so far nobody has been able to share a file with us for analysis. So, we’re asking for your help.

If you have tried to convert your Outlook 2011 Native files and have seen this bug, and if you can provide us some files so that we can reproduce the problem, we’ll give you a free Emailchemy Personal Edition – Household license. If you already have a license, we’ll extend it for another year free of charge.

Send an email to our helpdesk or support address and let us know if you can help.


On converting Exchange-style addresses to SMTP format

When email is sent between 2 people with accounts on an Exchange email server, the email addresses that are used are not the typical and familiar SMTP-style email addresses. An Exchange user’s SMTP email address may be joe.bob@somecompany.com, but Exchange uses an address that is based on X.400 (or X.500) and this user’s address would look like this: /O=SOME_COMPANY/OU=EXCHANGE_GOUP_1/CN=RECIPIENTS/CN=JOEBOB

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

Emailchemy 11.0 Released

Emailchemy 11 introduces support for Outlook Mac 2011 OLM files. It also adds features to the Google Apps Uploader command line tool for more control over scripted migrations.

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!

FAQ: Why are my messages blank after converting Outlook to Entourage?

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

Video walkthrough for importing email into Outlook

NOTE: an updated version of this video for Outlook 2013 is posted here: http://www.weirdkid.com/blog/2015/08/14/video-walkthrough-of-importing-email-into-outlook-2013/

The screencast starts with the act of converting Entourage email, but you could substitute the converting of any supported format. For example, you could use these instructions to move a standard mbox file into Outlook, too, as a general way to convert mbox to PST files.
Continue reading

Emailchemy 9.8.2 released

Version 9.8.2 is a maintenance update that includes an improved Entourage converter and a few bug fixes. It’s a free update to all who have access to any 9.x release of Emailchemy. If you are converting Entourage or Outlook PST files, then you should install this update.

The new Entourage converter has increased throughput (i.e. “it’s faster”) because it now keeps the entire database index in memory. This reduces the amount of jumping around the file, and it doesn’t increase the memory requirements significantly because all Entourage database files have known maximum number of items they can hold.

Also, and perhaps more importantly, the new Entourage converter extracts more data. It preserves all message flags (e.g. read/unread, priority, replied-to, forwarded, flagged) and sent attachments now too. Previous versions only preserved received attachments.

The Outlook PST converter was also modified to be a bit more resilient to corrupted PST files. Still, it’s always a good idea to make sure your PST file still works in Outlook before trying to run it through Emailchemy. See our previous post on working with corrupt PST files for more details.

Using Emailchemy on corrupt PST files

Inbox Repair Tool on Windows Vista

Inbox Repair Tool on Windows Vista

Outlook PST files have a very complicated internal database structure, which is read from and written to probably thousands of times every day, and they tend to be quite large. The combination of these characteristics, combined with the fact that Outlook and Windows do crash every now an then, makes the Outlook PST file somewhat susceptible to data corruption.

It can be random, and you may not even notice it right away, but even if a single bit gets flipped from a “0” to a “1” in a PST file, you could lose messages or the ability to even open the PST file in Outlook.

How do you know if a PST file is corrupt? There are major tells, like if Outlook tells you, for example, when you try to open it, or, if Outlook crashes when you try to open a particular message or open a particular folder in the PST data. But sometimes it is more subtle, like you may discover messages or attachments have disappeared, search no longer returns any results, or you can’t move messages in or out of the PST file. These are the cases that you may not notice in normal day-to-day use, but when you want to export your email from Outlook PST files with a utility like Emailchemy, you just might.
Continue reading