Ipswitch IMail to SmarterMail Converter

This conversion utility will convert Ipswitch IMail to SmarterMail. It has been tested with IMail version 12.x. Previous versions have not been tested but should still function.
Version 1.2 (2018-04-17)
  • Fixed issues with parsing Ipswitch IMail files from the registry and associated UID files.
Version 1.1 (2016-09-02)
  • Fixed an issue reading UID file on conversion
  • Fixed an issue that would cause mail to get stored in incorrect folder
Version 1.0 (2013-03-27)
The following are converted:
  • Domains
  • Domain Aliases
  • Users
    • Email
    • Passwords
    • Signatures
    • Auto-responders
    • Address book
    • Forwarding addresses
  • User Aliases
  • Lists
IMPORTANT NOTE: Build 1.2 and earlier are not compatible with a conversion to SmarterMail Build 6911 (Dec 3, 2018) and later. If converting to a current Build of SmarterMail, you will want to do the following:

Option 1
SmarterMail licenses are backwards-compatible. So, if you have a license for a current build, you can download and install SmarterMail 16.x, then run the iMail converter. You'd then need to upgrade that installation to a current Build after the conversion.

Option 2
If you want to use the converter for a recent Build, you still can. However, there are some extra steps that are required. Current Builds of SmarterMail transitioned to JSON from XML for system files. Therefore, after running the converer, you'll want to do the following:
  1. Stop mailservice.exe
  2. Find the domains.json file
  3. Enter all of your domains
  4. Re-start mailservice.exe
Once you re-start the mail service, the domains listed in that JSON file will be converted to the new version.  We will be releasing a new iMail converter in the near future, but for now, these are your options.

Before running the converter:
  • Run the converter in test mode before attempting the real conversion. The test mode option is shown on the "Ready to Start Conversion" page.
  • The converter must be run on the server that is running IMail. SmarterMail does not have to be on the same server. If SmarterMail is on a different computer you will want to map a network drive on the IMail server to the SmarterMail server.
  • Make sure to activate SmarterMail beforehand and that the license supports the number of domains/users that will be converted. If either limit is exceeded SmarterMail won’t run.
  • Stop all IMail services during the conversion. Otherwise mail may come in after an account has been converted and that mail will be lost. Also it is preferable that the IMail files don’t change while the converter is running for obvious reasons.
Running the converter:
  1. After agreeing to the license agreement the wizard will present a list of all the IMail domains. Select which ones you wish to convert and click ‘Next’.
  2. The wizard will now ask for information it needs to do the conversion. The first field is the domainList.xml path. Every SmarterMail server has a domainList.xml file that tells SmarterMail what domains it controls and where the root directory to each domain can be found. This file is found in the Service directory in the SmarterMail installation directory. By default this is found at “c:\program files\smartertools\smartermail\service\domainList.xml”.
  3. The next field is the domain path which is where the converter will write the SmarterMail domain and user files (including email). If you mapped a drive ‘z’ from the IMail server to the SmarterMail server this path may be ‘z:\SmarterMail\Domains’.The next field is relative domain path. This is what will be entered into the domainList.xml file SmarterMail will use to locate domains. This must be the path to the root domain folder on the SmarterMail server. If you mapped a drive ‘z’ on the IMail server to the SmarterMail servers drive ‘d’, you would use the d drive letter for this path. If the domain path was set to ‘z:\SmarterMail\Domains’ the relative domain path would be ‘d:\SmarterMail\Domains’.
  4. The next field is the ‘Default Domain IP’. This is the ip address on which SmarterMail will listen for SMTP, POP3, and IMAP connections. If the domains in IMail are set to listen on different ip’s you will want to check the ‘Try to keep each domain’s original IP’ radio button. Otherwise you will want to leave the ‘Force all domains to this IP’ checked which will be the setting for a majority of cases.
  5. Processing threads is recommended to be set to 2 times the number of processors on the server.
  6. The destination server ip field is only used with the “Update the SmarterMail Service…” check box. This will activate domains as soon as they are converted.
  7. Click Next. You will have a few pop up boxes on the way. Just click ok to those. One more page will ask that IMail be stopped. Click Next one more time to start the conversion.
  8. If SmarterMail was running during the conversion, it is recommended that you restart it when the conversion has completed.
NOTE: All the information SmarterMail needs to run is in the root domain directory and two xml files named domainList.xml and mailConfig.xml in the Service directory located in the SmarterMail installation folder. By default the root domain directory is found in “c:\SmarterMail\Domains” and the xml files are located in “c:\Program Files\SmarterTools\SmarterMail\Service”. To copy a conversion to a new computer you would just copy these files over. Make sure the destination SmarterMail server is stopped while the files are being copied. If the path to the root domain directory was changed, you will have to manually edit the domainList.xml file to reflect this change. You will also have to reactivate SmarterMail because the computer name changed. You may have to call SmarterTools to allow for another activation.
Source code is released under the GNU Lesser Public License.


I'm unable to get this to work on Imail 11.5.

I getting the following error:

System.Exception: Invalid File Length: ## on every *.uid file.

Judy Chapman (8/3/2015 at 11:35 AM)
Sorry to hear that, Judy! Please submit a ticket to our support department for further troubleshooting on this issue. To do so, head over to the Tickets tab. You'll need a support ticket available on your account and to be logged in at this portal to access the Support Department.
Andrea Rogers (8/3/2015 at 2:32 PM)