Welcome to the imapsync web site!
Ten years old since release 1.1!
(on Friday 29 July 2011)
What is imapsync?
imapsync software is a command line tool allowing incremental and
recursive imap transfers from one mailbox to another, both anywhere on the internet
or in your local network.
imapsync is useful for imap account migration or imap account backup.
imapsync is not adequate for maintaining two active imap accounts in synchronization
where the user plays independently on both sides. Use offlineimap
(written by John Goerzen) for this purpose.
Some numbers
- Number of imapsync users per month: between 2 and 3 thousands users
- Number of imapsync transfers per month: between 3 and 8 millions transfers
- Pourcentage of Windows users : 10%
- Biggest user usage: 5 millions of IMAP mailbox transfers in a month (one every 2 seconds)
Latest release is imapsync
Written on
See ChangeLog to know what's new in details since 2001.
New features or bugfixes since previous releases:
- 1.452
- New feature: Added --search option allowing to select messages with the powerful IMAP SEARCH command.
- Bugfix: Date reference to select messages with --maxdate --mindate is the beginning of imapsync run now.
- Bugfix: Fixed ps call to work with Solaris 10. Thanks to Daniel Rohde.
- Success: Kerio 7.2.0P1 success story.
- Success: MDaemon 12.0.3 success story.
- 1.446
- Bugfix: Better --idatefromheader behavior (thank to Dax Kelson patches).
- Usability: Now --delete2 sets --uidexpunge2 instead of --expunge2 if possible.
- Usability: Adapted the usage output multiline character to Unix or Win, \ or ^
- Bugfix: Avoid a "not a number" warning when size is null.
- Bugfix: Added "Date" in the default --useheader list. It is ("Message-Id", "Message-ID", "Date")
- Bugfix: allows bad header beginning with a blank character.
- 1.434
- Bugfix: Changed the way imapsync knows whether a folder exists or not. Exchange might be happy and stop deconnecting for this reason.
- Bugfix: Reconnections are well done in TLS mode now.
- Bugfix: IMAP RFC 3501 and some imap servers require internal dates have a zone data. Default to +0000 when host1 doesn't give it.
- Bugfix: Options --maxsize --minsize now really work with --useuid (1.422 had a cache issue).
- Bugfix: Improved the way imapsync deals with headers:
- Stopped getting first 2KB body of message. Not a good idea in practice.
- If massive get headers fails then take the whole header one by one (instead of body).
- Default is like --useheader "Message-Id" --useheader "Message-ID" (instead of just "Message-Id").
- Use header "Message-Id" and header "Date" as md5 signature when taking the whole header.
Who is the author?
Gilles LAMIRAL
Email: gilles.lamiral@laposte.net
Good feedback is always welcome, bad feedback is often welcome.
Where to talk about imapsync?
A nice place to talk about imapsync is the public
imapsync mailing-list (see below section Mailing-List).
Buy imapsync source code
The Perl imapsync source code will run anywhere a Perl interpreter can run: any Unix, Linux, Windows, or Mac OS operating system.
Buy latest imapsync Perl source code for 30 EUR
30 EUR is equal to around 45 USD, no problem to pay in USD (or any currency) with paypal:
You will receive a download link just after the payment.
One year of imapsync updates without extra payment.
30 days money-back guarantee!
Buy professional support for imapsync
For 180 EUR buy imapsync support by the developper who wrote and maintains imapsync.
180 EUR is equal to around 260 USD, no problem to pay in USD (or any currency) with paypal:
Then you will be able to expose your issues by email or phone and to converse until your issues are solved.
Buy standalone imapsync.exe for win32
Struggle free from source code and Perl installation by
buying the latest win32 standalone imapsync.exe for 10 EUR
30 EUR is equal to around 45 USD, no problem to pay in USD (or any currency) with paypal:
You will receive a download link just after the payment.
One year of imapsync updates without extra payment.
30 days money-back guarantee!
Documentation
Read the INSTALL file to know how to install imapsync on your system.
The README file has many tips to understand imapsync and succeed in your migration or backup.
The FAQ file presents Frequently Asked Questions (and not so frequently asked ones).
The TODO file list what may be coded or done in the future.
See also the wanted section.
All the people I thank are in the CREDITS file.
What you can do with imapsync is listed in COPYING.
The imapsync mailing list
The public mailing-list may be the best way to get free support.
You can write to the mailing-list even if you're not subscribed to it.
In that case you will receive a confirmation message each time you post (to avoid spam).
To write on the mailing-list, the address is:
imapsync@linux-france.org
To subscribe, send a message to:
imapsync-subscribe@listes.linux-france.org
To unsubscribe, send a message to:
imapsync-unsubscribe@listes.linux-france.org
To contact the person in charge for the list:
imapsync-request@listes.linux-france.org
The list archives are available at
http://linux-france.org/prj/imapsync_list/
So consider that the list is public, anyone can see your post.
Use a pseudonym or do not post to
this list if you want to stay private.
Thank you for your participation to the imapsync mailing-list!
WANTED!
I code new features and fix bugs for free when I have time and when I find it useful.
If you really want a feature or a fix you can donate money and my next development time
will be to code it or fix it.
On april 2011: 1 EUR ~ 1.48 USD.
Some features and their time/money to be done evaluation:
| DONE | Feature | Time guessed | Time spent | Money received | Money still needed |
|---|
| No | Backup to files | 20 hours | 60 min | 0 $ | 800 $ |
| No | Efficient Gmail backup | 20 hours | 80 min | 0 $ | 800 $ |
| No | Better error reporting | 5 hours | 0 min | 0 $ | 200 $ |
| Yes | Add cache | 10 hours | 1310 min | 400 $ | 0 $ |
| Yes | Speedup 50% | 10 hours | 80 min | 10 $ | 0 $ |
| Yes | --delete2folders | 3 hours | 270 min | 90 $ | 0 $ |
| Yes | NTLM auth | 3 hours | 300 min | 15 $ | 0 $ |
| Yes | Win32 imapsync.exe | 8 hours | 520 min | 45 $ | 0 $ |
| Yes | Win32 bug fixes | various | 370 min | 100 $ | 0 $ |
| Yes | Fix capability changes | 1 hour | 80 min | 0 $ | 0 $ |
| Yes | Large mailbox --maxage | 4 hours | 270 min | 0 $ | 0 $ |
| Yes | dkimap support | 3 hours | 120 min | 0 $ | 0 $ |
| No | gratis from here | 4 hours | 0 min | 0 $ | 60000 $ |
Lists of imap server software failures and success stories
Let's start with reported failure stories over the past.
Maybe new imapsync releases can run successfully with them.
Don't hesitate to have a try, I will help you and make efforts to switch them to the success list.
- DBMail 0.9, 2.0.7 (GPL). But most other DBMail releases are supported (see below)
- Imail 7.04 (maybe).
- MailEnable 1.54 (Proprietary) but MailEnable 4.23 is supported.
- (2011) MDaemon 12.0.3 as host2 but MDaemon is supported as host1. MDaemon is simply buggy with the APPEND IMAP command with any IMAP email client.
Now the long reported success stories list: 44 different imap server softwares supported!
([host1] means "source server", [host2] means "destination server"):
- 1und1 H mimap1 84498 [host1]
- Archiveopteryx 2.03, 2.04, 2.09, 2.10 [host2], 3.0.0 [host2]
(OSL 3.0) http://www.archiveopteryx.org/
- BincImap 1.2.3 (GPL) (http://www.bincimap.org/)
- CommuniGatePro server (Redhat 8.0) (Solaris), CommuniGate Pro 5.2.17[host2] (CentOS 5.4)
- Courier IMAP 1.5.1, 2.2.0, 2.1.1, 2.2.1, 3.0.8, 3.0.3, 4.1.1 (GPL)
(http://www.courier-mta.org/)
- Critical Path (7.0.020)
- Cyrus IMAP 1.5, 1.6, 2.1, 2.1.15, 2.1.16, 2.1.18
2.2.1, 2.2.2-BETA, 2.2.10, 2.2.12,
v2.2.3-Invoca-RPM-2.2.3-8,
2.3-alpha (OSI Approved),
v2.2.12-Invoca-RPM-2.2.12-3.RHEL4.1,
2.2.13,
v2.3.1-Invoca-RPM-2.3.1-2.7.fc5,
v2.3.1-Invoca-RPM-2.3.1-2.8.fc5 [host1],
v2.3.7,
(http://asg.web.cmu.edu/cyrus/)
- David Tobit V8.
- DBMail 1.2.1, 2.0.4, 2.0.9, 2.2rc1 (GPL) (http://www.dbmail.org/).
2.0.7 seems buggy.
- Deerfield VisNetic MailServer 5.8.6 [host1]
- dkimap4 [host1]
- Domino (Notes) 4.61[host1], 6.5, 5.0.6, 5.0.7, 7.0.2, 6.0.2CF1, 7.0.1[host1], 8.0.1[host1]
- Dovecot 0.99.10.4, 0.99.14, 0.99.14-8.fc4, 1.0-0.beta2.7,
1.0.0 [dest/source] (LGPL) (http://www.dovecot.org/)
- Eudora WorldMail v2
- Gimap (Gmail imap) [host1] [host2]
- GMX IMAP4 StreamProxy.
- Godaddy IMAP (since Godaddy runs Courier)
- Groupwise IMAP (Novell) 6.x and 7.0. Buggy so see the FAQ.
- hMailServer 5.3.3 [host2], 4.4.1 [host1], HMAILSERVER 5.3.2-B1769 on windows 2003 [hsot2]
- iPlanet Messaging server 4.15, 5.1, 5.2
- IMail 7.15 (Ipswitch/Win2003), 8.12, 11.03 [host1]
- Kerio 7.2.0P1 [host1]
- MailEnable 4.23 [host1][host2], 4.26 [host1][host2]
- MDaemon 7.0.1, 8.0.2, 8.1, 9.5.4 (Windows server 2003 R2 platform), 12 [host2], 12.0.3 [host1]
- Mercury 4.1 (Windows server 2000 platform)
- Microsoft Exchange Server 5.5, 6.0.6249.0[host1], 6.0.6487.0[host1],
6.5.7638.1 [host2], 6.5 [host1], Exchange 2007 SP1 (with Update Rollup 2),
Exchange2007-EP-SP2,
Exchange 2010 RTM (Release to Manufacturing) [host2],
Exchange 2010 SP1 RU2 [host2]
- Mirapoint server
- Netscape Mail Server 3.6 (Wintel)
- Netscape Messaging Server 4.15 Patch 7
- OpenMail IMAP server B.07.00.k0
- OpenWave
- Oracle Beehive [host1]
- Qualcomm Worldmail (NT)
- Rockliffe Mailsite 5.3.11, 4.5.6
- Samsung Contact IMAP server 8.5.0
- Scalix v10.1, 10.0.1.3, 11.0.0.431
- SmarterMail, Smarter Mail 5.0 Enterprise, Smarter Mail 5.5 [host1].
- SunONE Messaging server 5.2, 6.0 (SUN JES - Java Enterprise System)
- Sun Java(tm) System Messaging Server 6.2-2.05, 6.2-7.05, 6.3
- Surgemail 3.6f5-5
- UW-imap servers (imap-2000b) rijkkramer IMAP4rev1 2000.287
(RedHat uses UW like 2003.338rh), v12.264 Solaris 5.7 (OSI Approved)
(http://www.washington.edu/imap/)
- UW - QMail v2.1
- VMS, Imap part of TCP/IP suite of VMS 7.3.2
- Zimbra-IMAP 3.0.1 GA 160, 3.1.0 Build 279, 4.0.5, 4.5.2, 4.5.6,
Zimbra 5.0.24_GA_3356.RHEL4 [host1], 5.5, 6.x
This document last modified on
($Id: index.shtml,v 1.86 2011/08/03 01:26:05 gilles Exp gilles $)