Update November 17 2012:
I started this post back on July 20 – four months ago – and have only finished the migration now. That’s because I found a lot of unexpected problems along the way.
The rest of this post is my new, improved, and corrected step-by-step guide on how to migrate email from Eudora (up to version 7) or Thunderbird to GMail, based on hard-won experience.
I’ve been using Eudora since 1995 (17 years). Before that I used Unix mail (Sun; early 1990s), CompuServe (back to 1981), and something called “The Source” (1979; I was ‘TCA818’). Disk space was expensive back then so I didn’t save a lot of email.
But since 1995 I’ve kept everything – disk drives got bigger faster than my mail archive. So I had about 14 GBytes of email in Eudora.
Eudora has been abandoned by Qualcomm since 2006 and is getting old; there’s a new open source version based on Thunderbird (“Eudora OSE”), which sucks.
As our company grows the job of administering Eudora users (plus myself) was getting too big for me, so I decided to outsource it to Google Apps for Business. Which means GMail, and migrating the old email.
In the following, I’ll use these abbreviations:
- E7 – Eudora 7 (or any earlier version of Eudora)
- OSE – Eudora Open Source Edition (used only for migration)
- Tbird – Mozilla Thunderbird
- Outlook – Microsoft Outlook 2003 or later
- OE – Outlook Express
THINGS THAT WON’T WORK
To save you time, here are some things that won’t work:
- Syncing E7 to GMail using IMAP
- Converting E7 to E-OSE, then sync E-OSE with GMail using IMAP
- Converting E7 to E-OSE, then sync Tbird with GMail using IMAP
- Converting E7 to Outlook Express, that to Outlook, then Outlook to GMail
- Importing E7 data with Outlook, then sycning to GMail
- Importing Tbird data with Outlook, then sycning to GMail
- Importing E7 data with Thunderbird
- Syncing Outlook with GMail via IMAP (use this instead; it works)
Trust me, don’t bother.
If you really care or don’t believe me, in the Appendix at the very end of this posting I’ve put some of my notes on why some of those don’t work.
(I haven’t the patience to describe all the problems…comments in the Python files give some more details.)
STUFF YOU WILL NEED
To do the migration, you’ll need the following:
- Your Eudora mailbox and “attach” files
- Eudora Open Source Edition
- Mozilla Thunderbird
- Microsoft Outlook (2003 or newer)
- Python (installed on your system)
- These four Python scripts (click to download; put them all in one folder)
- Free disk space (at least 3x as much as used up by Eudora data now)
These are only for the migration. Once it’s done you can throw away all of them.
All of those are free except for Outlook, but you probably know someone who has a copy you can borrow for the migration. Alternatively, you could look on eBay for an older version cheap. (I used Outlook 2003, so you don’t need a recent one to do this.)
(You need real Outlook, not “Outlook Express”.)
If installing Python and running my Python scripts is too complex for you, this method won’t work for you, and I don’t have any suggestions – I haven’t found a simpler way that works. (Not for lack of trying.)
STEP 1 – GET GMAIL WORKING
Before you do anything else, you need to have your GMail account working, and new mail needs to arrive at GMail (not Eudora or Thunderbird). Test it by sending yourself an email.
If you’re using free GMail (@gmail.com), you you can skip the rest of this step.
To get mail to arrive at GMail using your own domain name:
- CNAME records need to be alerted at your domain server (usually the web hosting site – wherever the A record points), not at the domain registrar. If you’re using cPanel, this is most easily done using the “Advanced DNS Zone Editor”.
- The same goes for MX records – these need to be changed at the host the A record points to, not at the domain registrar.
Our domain registrar is 1and1.com, but the DNS A records point at our server at hostgator.com, where the web page is hosted. This was confusing because our domain registrar also offers web hosting, so they have an interface to change your CNAME (and I think also MX) records. But that only has an effect if the domain registrar is also the web host.
http://www.mxtoolbox.com is a really useful tool to check your DNS records.
Another problem I had was that email was getting to GMail just fine from everywhere except internal company addresses; those emails kept arriving at the old mail server (at Fastmail.fm – highly recommended if you only need email).
It turns out that during the transition to GMail some users were still sending internal email via Fastmail’s SMTP server (not yet Google’s), and Fastmail still thought it was supposed to handle incoming mail for our domain. So when it got an email directed internally, it wasn’t even looking at the MX records (and therefore not picking up the change on where to deliver the mail). So,
- Remove your domain from the list of domains handled by your old mail provider
Once I did that (under “Virtual Domains” at Fastmail), internal-origin mail started getting delivered to GMail.
STEP 2 – SETTING UP GMAIL
In each user’s individual GMail account, I’ve setup:
|Settings>Labels||Check “Show in IMAP” for both “All mail” and “Drafts” (per Google)|
|Settings>General||Set up signature
Conversation View: Off (more like Eudora)
Button Labels: Text
|Settings>Themes||High contrast (helps distinguish panel areas)|
|Settings>Web Clips||Turn off|
Except for IMAP (which we’ll need), these things are a matter of taste.
I wanted to use another domain as an alias for the company domain, for testing purposes. Google supports that, but wants you to put a cookie in the root of your web page to verify that you own the domain. Unfortunately, the test domain I wanted to use was redirected to our main web page (that domain is a mis-spelling of our correct domain), and Google didn’t like that.
They offer another method to verify ownership, by adding a TXT record with the cookie to the domain’s DNS entry. At first I tried adding a TXT record to “mailtest.myTestDomain.com”, and that didn’t work.
It turns out that you can have multiple TXT records for a single domain (who knew?) – Google was looking for the cookie in the TXT records for “myTestDomain.com” (not any sub-domain). Once I did that, Google was happy and I could use the test alias.
Like the CNAME and MX records, the TXT records need to be modified at your domain server (in my case, at Hostgator), not the registrar.
STEP 3 – PREPARATION FOR THE MIGRATION
If you’re converting from Thunderbird instead of Eudora, skip forward to Step 6 below (you already have a Thunderbird data folder).
Before you start the migration, make sure you’ve done the following:
- Verify new email arrives at GMail (see above)
- Reduce the total number of folders in Eudora (or Thunderbird) to (much) less than 500.
- Eudora 7: Special>Empty Trash
- Eudora 7: Special>Compact Mailboxes
- Exit Eudora 7. Do not run it again (this will mess things up).
- Make sure you have at least 3x as much free disk space as occupied by the Eudora 7 user folders.
- Backup your Eudora data folder (in case something goes wrong and you need to start over, or if you ever want to use Eudora to look at your old email again).
Re #2, the 500 folders includes all sub-sub-sub-folders. After a lot of discussions with GMail support people at Google, I found that GMail simply can’t handle large numbers of labels (each folder gets converted to a GMail label). Their stated limit is 500 labels.
If you go past 500 labels, things will seem to work, but then break in hard to predict ways. If you get “oops…error #400” from GMail, this is the problem – too many labels. There’s no workaround; just avoid too many labels in GMail.
Re #5 and #7, the migration process will mangle your Eudora 7 users folders; running Eudora 7 again will un-mangle them and break things. So backup your user folder (#7). After the migration is complete, you can restore it and then use Eudora to access your old email. (It’s fine to run Eudora again after you’ve restored the user folders.)
If you have more than one Eudora user folder on your computer, make sure the one you want to migrate is the last one you open with Eudora. When you start Eudora OSE, it will try to migrate the last Eudora 7 mail account you opened (I’m guessing this is stored somewhere in the registry, but I haven’t found where).
STEP 4 – RUN FixEudora7Mail.py SCRIPT
Make sure you’ve done steps 1 to 7 (above) to prepare.
- Start up Python
- Change the Python working directory to the Eudora user data folder.
You can do this with:
os.chdir('path to Eudora user data folder')
os.getcwd() # just to verify that it worked
- Run the Python script “FixEudora7Mail.py“.
Just FYI, this will read descmap.pce (mapping of file names to mailbox names), then for each mailbox:
- Make a binary copy of mailbox
- Read each message in the order it appears in the .TOC index file
- Rewrite the “From ???@???” line with a time derived from the UTC time in the .TOC file
- Delete the original mailbox, and replace it with the revised one using a “safe” name acceptable to both Tbird and Windows
STEP 5 – MIGRATE EUDORA 7 DATA TO EUDORA OSE
Do not run E7 any more on this folder. If you do, E7 will break some of the corrections applied in the previous step. (If you need to run E7 later, restore your backup first.)
In this step we’re going to convert E7 data to Thunderbird format using Eudora OSE. (E-OSE and Tbird use the same data files.) Thunderbird stores its data here:
Vista or Win7:
<user path>\Application Data\Thunderbird
Linux and OS X probably store it somewhere else – find out where.
- Navigate to the Thunderbird folder (just mentioned).
- Delete it (…\Thunderbird) if it already exists from previous use of Thunderbird. (Or rename it if you want to keep it.)
- Turn off your antivirus software – this is really important, otherwise you’ll get “Unable to save your message as draft. Error writing temporary file.” errors.
- Start Eudora OSE. When it starts and doesn’t find a Thunderbird profile, it will offer to migrate the Eudora 7 mail. Let it. (“Import from Eudora”, then Next.)
- Wait. OSE will import everything from the last-used Eudora 7 user data folder into the Thunderbird folder. The import is amazingly slow. If you have a lot of messages, allow several hours.
- When it’s done importing, hit ‘Cancel’ (to the “System Integration” box), and exit OSE.
- Turn your antivirus software back on.
If you don’t run out of disk space and didn’t have an antivirus program running, the import should complete without any error messages.
We’re not going to transfer email directly from OSE to Google because OSE isn’t very good at that; instead we’ll use Tbird, which is better and faster at it. But first we have to fix some things in the next steps.
STEP 6 – FIX CONVERTED EMAIL
Now we’re going to fix a lot of mistakes OSE made in the conversion. (If you’re starting from Tbird instead of Eudora, this step is harmless and may fix some problems.)
- Be sure your antivirus software is back on.
- Start up Python again
- Change the Python working directory to the Thunderbird “Local Folders” folder.
This is a sub-folder buried deep within the main Thunderbird data folder mentioned earlier. It’s here:
Vista or Win7:
<user path>\AppData\Roaming\Thunderbird\Profiles\<unique key>\Mail\Local Folders
<user path>\Application Data\Thunderbird\Profiles\<unique key>\Mail\Local Folders
As before, you can change the Python working directory like this:
os.chdir('<user path>\AppData\Roaming\Thunderbird\Profiles\<unique key>\Mail\Local Folders')
os.getcwd() # just to verify that it worked
- Run the Python script “FixTbirdMail.py“.
Just FYI, for each mailbox, this will:
- Remove the .msf file (Tbird index file; we will let Tbird rebuild this)
- Open a new output mailbox (“.new”)
- Fix HTML entities split across lines (example: “µ”)
- Replace all ‘&’ with ‘&’
- Identify mailboxes with attachments too large for GMail
- Delete the original mailbox, replace it with the fixed one.
STEP 7 – SET UP AUTOMATIC MAILBOX RECONFIGURATION
If you had a lot of mailboxes in Eudora (too many for GMail) and you want to mechanically reduce the number (instead of doing it all by hand), you can use this step to do it.
If that isn’t a problem for you, you can skip this step.
The next (and final) Python script will parse the entire ‘Local Folders’ tree looking for files with any of the three following names:
If it finds ‘CONCATENATE.ME’, it will concatenate all the mailboxes in that folder (the folder where the file was found) into a single mailbox, with the name of the folder where the file was found. This is a quick way to merge a bunch of mailboxes.
If it finds ‘MOVEUP.ME’, it will move up the entire folder (where the file was found) by one level in the folder tree.
If it finds ‘EXECUTE.ME’, it will execute the Python commands in the file, in the context of the folder where the file was found. This is a way to customize changes of your own to the folder structure (you’ll have to know a little Python). Here’s an example of an EXECUTE.ME file I used:
src = ‘3GPP’
dest = ‘Old stuff.sbd\Organizations.sbd\3GPP’
shutil.move(os.path.join(path, src), dest)
src = ‘ETSI TIPHON’
dest = ‘Old stuff.sbd\Organizations.sbd\ETSI TIPHON’
shutil.move(os.path.join(path, src), dest)
src = ‘GII’
dest = ‘Old stuff.sbd\Organizations.sbd\GII’
shutil.move(os.path.join(path, src), dest)
src = ‘Misc’
dest = ‘Old stuff.sbd\Organizations.sbd\Misc’
shutil.move(os.path.join(path, src), dest)
The contents of the CONCATENATE.ME and MOVEUP.ME files don’t matter – they can be empty files; all the script cares about is whether the file names exist.
So place the files where you want them (if you care).
STEP 8 – MERGE AND SPLIT MAILBOXES
This step has two purposes:
- It will process the CONCATENATE.ME, MOVEUP.ME and EXECUTE.ME files as just mentioned. If they don’t exist, that’s OK.
- It will split any mailboxes that are > 2 GBytes in size into a number of smaller mailboxes. This prevents Thunderbird from choking on excessively-large mailboxes (you can re-combine them in GMail later if you want).
Any mailboxes that get split will have the old name plus a suffix to distinguish it. For example, if the mailbox called “Customers” was split into 3 parts, you’ll have:
- Start up Python again
- Make sure the Python working directory is again at the Thunderbird “Local Folders” folder.
- Run the Python script “MoveMergeSplitTBirdMailboxes.py“.
- Save (cut and paste) the output from the script – it will identify which mailboxes contained messages that are too large for GMail (> 25 MBytes). You’ll need this info in the next step.
Again, just FYI, for each mailbox, this will:
- For each path, excecute any Python commands in “EXECUTE.ME” file, then delete the “EXECUTE.ME” file.
- For each path, if file “MOVEUP.ME” exists, delete “MOVEUP.ME” then move entire folder up one level.
- Reparse the new directory structure.
- For each mailbox, if “CONCATENATE.ME” exists in the folder, concatenates all mailboxes there into a single mailbox.
- For each mailbox, split the file into smaller chunks if it’s > 2 GB in size (avoid Tbird 4 GB size limit).
- For each folder, remove any “CONCATENATE.ME” files.
- Remove empty files and folders.
STEP 9 – START THUNDERBIRD AND REMOVE MESSAGES TOO BIG FOR GOOGLE
Now we’re ready to run Thunderbird and look at the mail.
- Start TBird.
- Click “Cancel’ to the inital “System Integration” box.
- It will ask you for the password to your old email – don’t give it. Hit Cancel.
- Your mailboxes should be visible under “Local Folders”.
- Expand all the mailbox folders in Thunderbird. You have to open each one to get Thunderbird to index the folder and count the messages in it. Click on the top most folder (to show the mailboxes), then hit the down arrow on the keyboard to go to the next one. Repeat for all folders. Wait a while for Thunderbird to index everything.
- Refer to the output from the FixTbirdMail.py script – this should tell you which mailboxes have messages with attachments that are too big for GMail. (Look for mailboxes with more than zero messages that are “tooBig”.) With luck you won’t have any at all.
- If you have some, open up each mailbox with over-large messages. Right-click on the “Subject” heading for the messages and turn on the “Size” column. Then sort by size to find the messages that are over 25 MBytes in size. For each one, either delete the whole message or remove enough attachments to get it under 25 MBytes. (If you didn’t save the output from FixTbirdMail.py, you’ll have to check every mailbox.)
Note that the output from FixTbirdMail.py tells you which input file (before splitting) had “tooBig” messages; it doesn’t identify which of the new (split-up) mailboxes have the large messages.
For example, if you see:
Read: Dave Write: Dave.new 2,952 output messages.
Write: Dave_2.new 1,798 output messages.
Write: Dave_3.new 1,720 output messages.
Write: Dave_4.new 205 output messages. 6,675 messages 7 tooBig.
This indicates that the input mailbox “Dave” had 7 messages that were “tooBig” for GMail; you need to check all four output files to find them.
It’s normal that some of your mailbox names may have been slightly altered – some characters that either Windows or Thunderbird can’t handle in mailbox names were automatically changed to ‘_’; the most common one is a slash. For now, leave these alone – you can change them back if you like once the mail is at GMail.
Now your Thunderbird email should be in good shape, and ready to transfer to Google.
STEP 10 – SETUP THUNDERBIRD TO TALK TO GMAIL VIA IMAP
We’re going to transfer the mail from Thunderbird to GMail using the IMAP protocol.
To configure Thunderbird to do that, in Thunderbird do:
- Tools>Account Settings>Account Actions (button): Delete any imported email accounts
- Tools>Account Settings>Local Folders>Junk Settings: Disable
- Tools>Account Settings>Account Actions>Add mail account… Then fill in:
- Your name
- Your complete email address (to be used with GMail)
- Password (for GMail)
- Click CONTINUE
- Immediately click MANUAL CONFIG (don’t let it auto-configure)
- Set Incoming: IMAP imap.gmail.com 993 SSL/TLS Autodetect
- Set Outgoing: SMTP smtp.gmail.com 587 STARTTLS Autodetect
- Set Username: Your complete email address (including domain)
- Click Done.
- Tools>Account Settings>GMail account>Server Settings: JUST MARK IT AS DELETED
- Tools>Account Settings>Copies & Folders:
- Clear “PLACE A COPY IN”
- Keep message drafts in “OTHER”
- Tools>Account Settings>GMail account>Junk Settings: DISABLE
- Click OK
At this point Thunderbird will log into Google and synchronize with your GMail account.
There will be two trees of mailboxes – “Local Folders” (stored on your computer) at the top, and below that, your GMail account (with your email address). This has your synchronized GMail. If you click on “Inbox”, you should see all your mailboxes at GMail.
STEP 11 – TRANSFER MAIL TO GMAIL
Finally, transfer the mail from Thunderbird to GMail. This is done by dragging the mailboxes from “Local Folders” in Thunderbird into the GMail account.
If you drag a whole folder, Tbird will copy the folder to GMail.
If you drag messages within a folder, Tbird will move the messages to GMail (deleting them from Tbird).
Do it any way you want. Each transfer requires a lot of time – GMail will only accept uploaded mail at a fairly slow rate. In the lower left corner, Tbird will show the status of the transfer (how many emails have been copied so far).
Also, GMail has bandwidth limits on how much email it will accept via IMAP – see here. At this writing, the limit is supposedly 500 MBytes/day (but it practice it seems to accept more). If you try to upload too much, at some point Google will just stop the transfer. You’ll get a (brief; easy to miss) message from Tbird that it “can’t append message”, and the transfer will stop. Try again later.
There’s no harm in re-uploading the same messages multiple times – GMail will detect that they’re duplicates; you’ll only have one copy of each message.
My suggestion is to copy the folders one at a time, and after each one is copied, check the number of messages in Thunderbird (or Eudora) against the number in GMail. Once it checks OK, rename the moved folder in Thunderbird to indicate it has been moved OK.
You can quickly see how many GMail messages have a given label – go into Settings>Labels on GMail and there’s a count next to each label. (Be sure to turn off “conversation view” to count messages instead of conversations.)
Don’t be too concerned if there are a few less messages in GMail than in Eudora 7 – GMail is very good about noticing and collapsing duplicate messages that crept into the Eudora 7 mailboxes over time. (Of course if there are more than a few missing, investigate.)
If there are missing messages after the transfer, it’s probably because the transfer of messages from Tbird to GMail stopped before the whole mailbox was sent. This can be because:
- GMail saw a message that was too large (> 25 MBytes).
- You’ve exceeded Google’s bandwidth limit for the day.
- GMail saw a malformed message that it “doesn’t like”.
Start by checking for over-large messages in the mailbox.
If that’s not the problem, consider if you’ve exceeded the bandwidth limit. If so, wait a day and try again.
If you still can’t transfer a mailbox completely, probably the mailbox has a malformed message that GMail doesn’t like. Messages with missing From: or To: fields are likely culprits. If you suspect a message is causing a problem, try moving just that message by itself. If you get an error from Tbird, that’s the problem – you’ll have to remove it from the mailbox.
If you can’t figure out which message(s) are causing the problem, you’ll have to find it by divide-and-conquer:
- Create a new mailbox called “name – part 2”.
- Move half the messages from the problem mailbox into the new mailbox
- Try transferring each of the 2 mailboxes separately.
Probably one of them will transfer OK, and the other won’t. The one that doesn’t has the problem email. If neither transfers, both mailboxes may have problem emails.
In either case, take the problem mailbox and do 1, 2, 3, above again (split it 2, try to transfer each half). Repeat until you’ve narrowed it down to the problem messages.
I had to do this on several mailboxes, but unless you have huge, old, mail archives, you probably won’t run into it.
BACKING UP YOUR GMAIL DATA
If you don’t 100% trust Google to keep all the correspondence you’ve accumulated over a lifetime safe, and want to back it up, here are some ways:
- Sync Outlook with GMail using Google Apps Sync for Microsoft Outlook®, then exit Outlook and backup the resulting .PST file(s). (You have to exit Outlook or the .PST file is locked by Windows and can’t be read for backup.)
- Getmail (via IMAP; see this article at Wired)
I’ve only tried the first so far (Outlook syncs very nicely with GMail using Google’s tool), but I plan to find a more automated method.
I do not recommend using Thunderbird/IMAP for backup – the IMAP sync is too flaky. Outlook, using Google Apps Sync for Microsoft Outlook®, syncs much more reliably.
The rest of this post provides some random useful information I discovered along the way.
ABOUT FILE FORMATS – GENERAL
Since Eudora OSE is a variant of Thunderbird, it stores email in the same format Thunderbird does, which is Unix mbox format (plus or minus some minor variations).
The end of the message header and start of the message body is marked by a blank line.
Eudora 7 uses almost the same format, except that it extracts all email attachments and saves them in binary in its “attach” folder. Since the Unix mbox format only stores text, with attachments in-line, the import to OSE results in folders that are larger (by about 1/3) than the Eudora 7 data was, because all the attachments get MIME-encoded as text.
ABOUT FILE FORMATS – EUDORA 7
Eudora doesn’t store the time/date messages were sent in the usual way (in the “Date:” field). Instead, it’s usually in the .TOC file (Table Of Contents) that’s unique to Eudora 7. Unfortunately, none of the migration tools (other than mine) read the .TOC file, so instead the wrong date gets picked up. Often the date is close enough to being correct that it isn’t obviously wrong, other times (depending on the history of the file and any past synchronization problems with the .TOC file,) it can be off by years.
The Python scripts read the .TOC file and fix this.
Some other things I learned along the way regarding Eudora 7 mail files:
- Messages in Eudora 7 format mailbox files start with the string “From ???@??? ” in the first characters of the line. This is followed by a date which is not trustworthy. My best guess is that this date is when the message was downloaded by Eudora from the server (not when it was sent). Usually; sometimes it’s just crazy.
- As mentioned above, attachments are not stored in the mail file. Instead, they’re stored as binary files in the “attach” folder.
- The best (only) reference for the format of the Eudora 7 .TOC file I know of is here: http://users.starpower.net/ksimler/eudora/toc.html (email me if that link dies; I have a copy of it).
- Message dates can be stored in three places in Eudora 7:
- In the “From ???@???” field (“From”)
- In the “Date:” field (“Date”)
- In the .TOC file, in 2 places (binary and text)
Sometimes a date is present in all 3 places, sometimes less. If any of the 3 differ, the “From” is the least reliable (it seems to be the date/time when the email was downloaded by Eudora, not when it was sent.)
Re the .TOC dates, the binary one is in seconds from 1970-01-01 00:00:00 UTC (standard Unix format), the text one is in local time with truncated seconds. The two always match.
Read/unread status is stored in the .TOC file.
ABOUT FILE FORMATS – EUDORA OSE AND THUNDERBIRD
If you look in the Thunderbird mail folder (given above), you’ll see a single file with no file extension for each mailbox – for example “pending” is the pending mailbox. There is also “pending.msf”.
The file without the extension (“pending”) is the Unix mbox format mail spool with everything in it, including attachments. The “.msf” file is the index, and entirely redundant – OSE and/or Thunderbird will rebuild it if/when it needs to (takes a long time).
Mailbox names that use invalid filename characters are stored in “panacea.dat”.
Read/unread status is stored in the message header (in the mbox file) in fields X-Mozilla-Status and X-Mozilla-Status2. (Details are here.)
WHY IMPORTING EUDORA 7 EMAIL DIRECTLY TO OUTLOOK DOESN’T WORK
It seems that Outlook 2003 really can’t import data from Eudora, even tho it claims it can.
All my attempts end in:
The mail folder could not be opened. If another application is using this file, please close and try again.
Supposedly this is caused by the mail not being in the folder where Outlook expects it; I tried copying it to “C:\Program Files (x86)\Qualcomm\Eudora” (the old XP-era default location) and also “…\Users\dave\AppData\Roaming\Eudora” (the new default location); that didn’t help.
To be fair to Outlook, it only claims to be able to import from Eudora 4 or earlier, although I’m pretty sure the file formats didn’t change since then. I even tried to install an old copy of Eudora 4, but Win7 doesn’t support 16 bit executables anymore, so that didn’t work. I suppose I could have tried it on XP, but I’m not very confident it would have helped.
Besides, this site claims that even when it works, it doesn’t work very well (supposedly attachments get messed up).
WHY IMAPSIZE DOESN’T WORK
Google’s official advice is that the only really robust method of migration to GMail is from Outlook “.PST” files.
I found a few commercial programs that claim to migrate Eudora mail to Outlook. I’m not against paying for something, but given all the complications I found with migrating to GMail, I’m very skeptical that these actually work as promised, and I didn’t feel like paying for something that won’t work.
IMAPSize is a free program that converts Unix mbox files to Outlook Express (“OE”). Outlook (not OE) claims to be able to import from OE.
But OE can’t handle files larger than 2 GBytes. If all your mail files are smaller than that (including attachments), it might work for you. Otherwise, not.
Also, IMAPSize doesn’t process the X-Mozilla-Status and X-Mozilla-Status2 headers used by Thunderbird to keep track of read/unread status, so that gets lost.