Name | Modified | Size | Downloads / Week |
---|---|---|---|
sources.zip | 2010-06-14 | 6.9 kB | |
readme.txt | 2010-06-14 | 6.3 kB | |
me2hmail.zip | 2010-06-14 | 265.0 kB | |
iniManager.bat | 2010-06-14 | 107 Bytes | |
mailenable2hmail.exe.bat | 2010-06-14 | 262 Bytes | |
iniManager.cs | 2010-06-14 | 1.9 kB | |
mailenable2hmail.exe.aspx.cs | 2010-06-14 | 23.3 kB | |
Totals: 7 Items | 303.6 kB | 0 |
***************************************** Mail Enable to hMailServer Migtation Tool v1.2 by: Andrew Gregory | Dragon Design info@dragondesign.co.uk http://dragondesign.co.uk ***************************************** REQUIREMENTS ------------ DOT NET Framework This has been developed and tested using: Mailenable v2.37 and hMailServer v4.4.1 DESCRIPTION ----------- This tool will go through the folder structure and files of the Mailenable install directory and use the information found to add settings to the hMailServer standard database for mySQL. This makes no changes to the existing Mailenable file structure as it is reads only. I have found however, when copying my mailenable directory structure that files are often locked so stopping the services during a migration might be extremely advisable. During update any settings not specified or migrated are set at the defaults normally set when adding anything using the hMailserver admin tool.. UPDATE ------ 14th June 2010 Moved data access code into main file for release. 10 Sept '08: Added the ability to configure and run ImapCopy.exe to import mail and message folders. Release: This migration tool is at its first stage of development and has been built for me to migrate to hmailserver from mailenable. I may be willing to develop it further if there is sufficient interest in this tool. If there are small issues such as different folder structures in newer versions of mailenable then just ask for an update.. NOTES ----- Exceptions will be thrown for incomplete folder structures in mailenable.. The following settings are transfered in this version (%MEROOT% implies the root folder of your mailenable install, eg C:\Program Files\Mailenable): Domains ------- Domain Names are added to hMailServer using the post office name from Mailenable, specifically the list of folders in %MEROOT%/Postoffices/. I have made an assuption here as i named my postoffices the same as the primary domain, getting the required file to convert the post office name to the primary domain name was a pain so i have skipped that for now. It still works but you may have to go through changing the domain name in hMailServer Admin. Will only insert new records. Accounts -------- Are added using the existing ME mailboxes stored in %MEROOT%/Postoffices/<domain name>/MAILROOT/ Last Login Times are set to the time of migration. Will only insert new records. Account Disabled ---------------- Disabled accounts are marked as so. Passwords --------- These are taken in plain text format from %MEROOT%/Config/auth.tab. There is an option in the .ini file to either apply the MD5 hashing or leave as un-encrypted (plain text) Will insert new records and update existing records. Forwarders ---------- Forwarding addresses are taken from the first entry (mailenable allows more than one) from %MEROOT%/Config/Postoffices/<domainname>/MAILBOX.tab. Will insert new records and update existing records Forwarding Addresses -------------------- Are inserted regardless of status (if they exist) Will insert new records and update existing records. Forwarding Active ----------------- If forwarding address is active. Will insert new records and update existing records. KEEP LOCAL COPY OF EMAIL ------------------------ If copy to be kept locaaly after forwarding is set. Will insert new records and update existing records. USAGE ----- There is a supplied mailenable2hmail.ini file to change some settings of the migration, as follows (This files must sit in the same directory as mailenable2hmail.exe) : [FILES] MEPostofficePath: The Folder path to your Mailenable instal file, eg. "C:\Program Files\Mailenable\" The path must be enclosed in quotes and MUST have a backslash at the end. [DATA] hMailmySQLServer: Your mySQL server Address for hMailserver. This should run ok from a different computer. I suspect the built in mySQL server is set to only accept local connections, still testing.. hMailmySQLDB: The hmailserver database name (default:hmailserver) hMailmySQLUser: The authenticated user (default:root) hMailmySQLPass: The unencrypted password for your login. See hmailserver docs on DecryptBlowfish for more info on getting this password. hMailmySQLPort: hmailserver mySQL port (default:3307) meSourceServer: Required to run ImapCopy, this fills out the source server for your message and folder migration. [SETTINGS] These are all true/false options so far. addDomainNames: Add domain names to hmailserver database, pretty much required to run the rest of the processes unless the domains already exist. addMailBoxes: Add mailboxes to each domain. As above, essential for further processing. addPasswords: Add passwords, the next setting is an add-on to this to encrypt the passwords using an MD5 hash algorithm (the default for hmailserver) The Passwords are only added or encrypted if the email address is found. The report at the end of the process shows how many read. encryptPass: Insert passwords in encrypted state (true) or as plain text(false). addForwarders: This will add forwarding addresses, tick whether forwarders are active and also runs the process for keeping a copy of forwarded message in the mailbox. copyMailandFolders: This will build a config file for and run ImapCopy.exe. You must download this seperately from: http://home.arcor.de/armin.diehl/imapcopy/imapcopy.html **ImapCopy.exe must be copied to the same directory as mailenable2hmail.exe** The process will create a new imapcopy.cfg using standard settings. With Pause Processes on you have the opportunity to edit the config file before running the import process. pauseBetweenProcesses: This pauses between each of the above processes, or not..! THE REST -------- This is provided as/is, use at your own risk, i/we accept no responsibility for any loss or unexpected results due to the use of this tool. You may use for publication or domestic or commercial use but may not sell it on without express permission from the developer. You must provide this read me file unedited with any redistribution. Released under GNU General Public License.