diff --git a/ChangeLog b/ChangeLog index d8c56d8..590e685 100644 --- a/ChangeLog +++ b/ChangeLog @@ -1,17 +1,58 @@ RCS file: RCS/imapsync,v Working file: imapsync -head: 1.555 +head: 1.564 branch: locks: strict - gilles: 1.555 + gilles: 1.564 access list: symbolic names: keyword substitution: kv -total revisions: 555; selected revisions: 555 +total revisions: 564; selected revisions: 564 description: ---------------------------- -revision 1.555 locked by: gilles; +revision 1.564 locked by: gilles; +date: 2013/08/18 19:28:47; author: gilles; state: Exp; lines: +114 -22 +Adapted behavior for allowing --maxdate --mindate with --noabletosearch. Use internat date instead of Date: header. +---------------------------- +revision 1.563 +date: 2013/08/16 00:59:30; author: gilles; state: Exp; lines: +8 -7 +Added QQMail success. +---------------------------- +revision 1.562 +date: 2013/08/16 00:41:48; author: gilles; state: Exp; lines: +38 -16 +Speed fix. Does not resync the flags when flags on host2 do not respect RFC. \Seen -> \SEEN. imapsync detects this as same flag. +Atmail 6.x [host1] success. +Fix for QQMail IMAP4Server. With --noabletosearch the previous fetch with 1:999999 is replaced by an uidnext request. +---------------------------- +revision 1.561 +date: 2013/08/09 23:49:23; author: gilles; state: Exp; lines: +15 -8 +Added --timeout in the --help output. +Default timeout is 120 seconds now (was nothing by imapsync, 600 with underlying modules). +---------------------------- +revision 1.560 +date: 2013/08/09 23:06:04; author: gilles; state: Exp; lines: +7 -7 +Added --addheader suggestion for messages with no header found. +---------------------------- +revision 1.559 +date: 2013/08/06 11:33:53; author: gilles; state: Exp; lines: +7 -7 +Apply same treatment to --delete2duplicates as --delete2. If --uidexpunge2 can be done, do it, else do --expunge2 (unless --nouidexpunge2 or --noexpunge2). +---------------------------- +revision 1.558 +date: 2013/08/03 01:13:37; author: gilles; state: Exp; lines: +18 -16 +Bugfix. SSL_version was not well treated. +---------------------------- +revision 1.557 +date: 2013/08/01 19:28:09; author: gilles; state: Exp; lines: +7 -7 +Bugfix. max_line_length('a') was wrong. +---------------------------- +revision 1.556 +date: 2013/08/01 00:10:03; author: gilles; state: Exp; lines: +42 -28 +Added --ssl1_SSL_version ssl2_SSL_version option to change default SSL_version. +For example --ssl2_SSL_version SSLv3 fix connection to cmail.cmich.edu on Windows. +Fixed a warning about regex with \E on Perl >= 5.16 +---------------------------- +revision 1.555 date: 2013/07/23 11:41:10; author: gilles; state: Exp; lines: +7 -6 Fix warning for extract_header() ---------------------------- diff --git a/FAQ b/FAQ index 59ad635..2a30202 100644 --- a/FAQ +++ b/FAQ @@ -1,5 +1,5 @@ #!/bin/cat -# $Id: FAQ,v 1.136 2013/08/03 02:07:30 gilles Exp gilles $ +# $Id: FAQ,v 1.138 2013/08/16 01:03:32 gilles Exp gilles $ +------------------+ | FAQ for imapsync | @@ -181,7 +181,7 @@ R. Search the internet. Q. Is is legal to find imapsync gratis (or not) elsewhere? R. Yes, the license permits it - http://imapsync.lamiral.info/LICENSE + http://imapsync.lamiral.info/NOLIMIT ======================================================================= Q. I use --useuid which uses a cache in /tmp or --tmpdir, the hostnames @@ -798,15 +798,24 @@ R. Use imapsync release 1.172 or at least 1.166 with options or a old old imapsync (before 1.94) ======================================================================= -Q. Does imapsync support IMAP over TLS (IMAPS)? +Q. Does imapsync support IMAP TLS? + +R. Use --tls1 and/or --tls2 options + +--tls1 tells imapsync to use tls on host1. +--tls2 tells imapsync to use tls on host2. + + +======================================================================= +Q. Does imapsync support IMAP over SSL (IMAPS)? R. Yes natively since release 1.161. still, 2 ways, at least : -a) Use --ssl1 and/or --ssl2 options +a) Use native --ssl1 and/or --ssl2 options ---ssl1 tells imapsync to use ssl on host1 ---ssl2 tells imapsync to use ssl on host2 +--ssl1 tells imapsync to use ssl on host1. +--ssl2 tells imapsync to use ssl on host2. b) Use stunnel @@ -817,6 +826,8 @@ b) Use stunnel or using names instead of numbers stunnel -c -d 143 -r imap.foo.org:993 then use imapsync on localhost (or bar machine) imap (143) port. + If the local port 143 is already taken then use a free one, 10143. + ======================================================================= Q. On windows ssl use to work with imapsync.exe 1.536 or previous then @@ -1770,6 +1781,12 @@ imapsync ... --sep1 '.' --prefix1 '' \ --noabletosearch --nocheckmessageexists --addheader (Thanks to Andrew Tucker) + +====================================================================== +Q. From or to QQMail IMAP4Server + +R. imapsync ... --noabletosearch + ====================================================================== Q: How can I write an .rpm with imapsync diff --git a/GOOD_PRACTICES.html b/GOOD_PRACTICES.html new file mode 100644 index 0000000..bb741db --- /dev/null +++ b/GOOD_PRACTICES.html @@ -0,0 +1,159 @@ + + +
+ + + + + + ++You are not supposed to have read the TUTORIAL documentation but it +reading it should help to understand and master the following best practices. +
+ ++By principle, imapsync does not change any single byte of messages, +unless --regexmess or --addheader is used. +But since imapsync identifies messages with "Message-Id" and "Received" headers, +it ignores messages that lack those headers; +most of the time it happens with the "Sent" folders. +A way to sync those messages is to add option --addheader. +Before appending a message on host2, and only when needed, +--addheader option adds a Message-Id header like "Message-Id: <123456789@imapsync>" +where 123456789 is the host1 folder message UID. Messages on host1 stay untouched. +This way, multiples runs will not generate duplicates as long as UIDs stay +the same on host1, which is the case for most imap servers. +
++Unix: +
++ imapsync \ + --host1 imap.truc.org --user1 foo --password1 secret1 \ + --host2 imap.trac.org --user2 bar --password2 secret2 \ + --addheader ++
+Windows: +
++ imapsync ^ + --host1 imap.truc.org --user1 foo --password1 secret1 ^ + --host2 imap.trac.org --user2 bar --password2 secret2 ^ + --addheader ++ + +
+Assertions for this example: +
++ imapsync \ + --host1 imap.truc.org --user1 foo --password1 secret1 \ + --host2 imap.trac.org --user2 bar --password2 secret2 \ + --delete2 --delete2folders ++Windows: +
+ imapsync ^ + --host1 imap.truc.org --user1 foo --password1 secret1 ^ + --host2 imap.trac.org --user2 bar --password2 secret2 ^ + --delete2 --delete2folders ++
+Have in mind +
++Restoring is not the exact reverse of backupping +since between a backup and a mistake, the context has changed, +some things went wrong but not all, for examples new messages arrived. +So synchronize an active account identical from a backup might not be the best idea. +
++The context can be a crash or equivalent like some if a +bad admin or service closed definitevely access to your messages. +Even in that case an exact restore, with --delete2 --delete2folders, should not be ok, +just because new messages arrive in INBOX all the time. +Plus, if the mailbox is a brand new one then --delete2 --delete2folders options are useless, +since there is nothing to delete. +
+ ++Presync is like a backup except deleting folders on host2 that +are not on host1 is not always wanted. Presync means a new +different imap server will host messages and folders. +Often this new imap server has predefined folders that +should be kept for proper use, so I suggest to not use +option --delete2folders. +
++Unix: +
++ imapsync \ + --host1 imap.truc.org --user1 foo --password1 secret1 \ + --host2 imap.trac.org --user2 bar --password2 secret2 \ + --delete2 ++
+Windows: +
++ imapsync ^ + --host1 imap.truc.org --user1 foo --password1 secret1 ^ + --host2 imap.trac.org --user2 bar --password2 secret2 ^ + --delete2 ++ + + + + diff --git a/GOOD_PRACTICES.t2t b/GOOD_PRACTICES.t2t new file mode 100644 index 0000000..d14ce22 --- /dev/null +++ b/GOOD_PRACTICES.t2t @@ -0,0 +1,129 @@ + + + +% $Id: GOOD_PRACTICES.t2t,v 1.5 2013/08/16 01:12:21 gilles Exp gilles $ + += Best practices for imapsync = + +You are not supposed to have read the TUTORIAL documentation but it +reading it should help to understand and master the following best practices. + + +== Simple transfer == + +By principle, imapsync does not change any single byte of messages, +unless --regexmess or --addheader is used. +But since imapsync identifies messages with "Message-Id" and "Received" headers, +it ignores messages that lack those headers; +most of the time it happens with the "Sent" folders. +A way to sync those messages is to add option --addheader. +Before appending a message on host2, and only when needed, +--addheader option adds a Message-Id header like "Message-Id: <123456789@imapsync>" +where 123456789 is the host1 folder message UID. Messages on host1 stay untouched. +This way, multiples runs will not generate duplicates as long as UIDs stay +the same on host1, which is the case for most imap servers. + + +Unix: +``` + imapsync \ + --host1 imap.truc.org --user1 foo --password1 secret1 \ + --host2 imap.trac.org --user2 bar --password2 secret2 \ + --addheader +``` +Windows: +``` + imapsync ^ + --host1 imap.truc.org --user1 foo --password1 secret1 ^ + --host2 imap.trac.org --user2 bar --password2 secret2 ^ + --addheader +``` + + +== Exact backup == + +Assertions for this example: + +- The target account at host2 is considered like inactive. +- Everything a user does on host1 will be synced, folders, messages, flags. +- Everything a user does on host2 will be erased by the sync. + +Two options are good for an exact backup, --delete2 and --delete2folders. + +- --delete2: deletes messages in host2 that are not in host1 server. +- --delete2folders: deletes folders in host2 that are not in host1 server. + +Unix: +``` + imapsync \ + --host1 imap.truc.org --user1 foo --password1 secret1 \ + --host2 imap.trac.org --user2 bar --password2 secret2 \ + --delete2 --delete2folders +``` +Windows: +``` + imapsync ^ + --host1 imap.truc.org --user1 foo --password1 secret1 ^ + --host2 imap.trac.org --user2 bar --password2 secret2 ^ + --delete2 --delete2folders +``` + + + +Have in mind + +- Backupping without restoring at least one time to check the process + is like pissing in a violin or throwing away your messages. +- Manual backups are useless, this way you will never have the ones you need to restore. +- Automatic backups are the way to go. They never forget to start. They may fail. +- Automatic backups can fail. How? Hard disks get fully filled, they crash. Networks fail too. +- Monitor the backups. +- Remenber you have backups. +- Document the restoring process or consider the backup is a just a lost trash. +- Think twice at least before running any restoring command. + + +== Restore == + +Restoring is not the exact reverse of backupping +since between a backup and a mistake, the context has changed, +some things went wrong but not all, for examples new messages arrived. +So synchronize an active account identical from a backup might not be the best idea. + +The context can be a crash or equivalent like some if a +bad admin or service closed definitevely access to your messages. +Even in that case an exact restore, with --delete2 --delete2folders, should not be ok, +just because new messages arrive in INBOX all the time. +Plus, if the mailbox is a brand new one then --delete2 --delete2folders options are useless, +since there is nothing to delete. + + + + + +== Presync == + +Presync is like a backup except deleting folders on host2 that +are not on host1 is not always wanted. Presync means a new +different imap server will host messages and folders. +Often this new imap server has predefined folders that +should be kept for proper use, so I suggest to not use +option --delete2folders. + + +Unix: +``` + imapsync \ + --host1 imap.truc.org --user1 foo --password1 secret1 \ + --host2 imap.trac.org --user2 bar --password2 secret2 \ + --delete2 +``` +Windows: +``` + imapsync ^ + --host1 imap.truc.org --user1 foo --password1 secret1 ^ + --host2 imap.trac.org --user2 bar --password2 secret2 ^ + --delete2 +``` + + diff --git a/Makefile b/Makefile index db879c8..24f59ea 100644 --- a/Makefile +++ b/Makefile @@ -1,5 +1,5 @@ -# $Id: Makefile,v 1.125 2013/08/03 17:25:50 gilles Exp gilles $ +# $Id: Makefile,v 1.129 2013/08/16 01:21:14 gilles Exp gilles $ .PHONY: help usage all @@ -56,8 +56,15 @@ VERSION: imapsync perl -I./$(IMAPClient) ./imapsync --version > ./VERSION touch -r ./imapsync ./VERSION +GOOD_PRACTICES.html: GOOD_PRACTICES.t2t + txt2tags -i GOOD_PRACTICES.t2t -t html --toc -o GOOD_PRACTICES.html -.PHONY: clean clean_tilde clean_test +TUTORIAL.html: TUTORIAL.t2t + txt2tags -i TUTORIAL.t2t -t html --toc -o TUTORIAL.html + +doc: README ChangeLog TUTORIAL.html GOOD_PRACTICES.html + +.PHONY: clean clean_tilde clean_test doc clean: clean_tilde clean_man @@ -259,7 +266,7 @@ DIST_PATH := ./dist/$(DIST_SECRET) lalala: echo $(DIST_SECRET) -dist: cidone test clean all INSTALL dist_prepa dist_prepa_exe +dist: cidone test clean all perlcritic dist_prepa dist_prepa_exe dist_prepa: tarball dist_dir @@ -299,16 +306,16 @@ upload_ks: ci tarball root@ks.lamiral.info:/var/www/imapsync/ rsync -lptvHzP $(PUBLIC_FILES_W) \ root@ks.lamiral.info:/var/www/imapsync/W/ - rsync -lptvHzP $(PUBLIC_FILES_IMAGES) \ + rsync -lptvHzPr $(PUBLIC_FILES_IMAGES) \ root@ks.lamiral.info:/var/www/imapsync/W/images/ rsync -lptvHzP ./W/ks.htaccess \ root@ks.lamiral.info:/var/www/imapsync/.htaccess - rsync -lptvHzrP ./dist/ \ + rsync -lptvHzPr ./dist/ \ root@ks.lamiral.info:/var/www/imapsync/dist/ - rsync -lptvHzrP ./examples/ \ + rsync -lptvHzPr ./examples/ \ root@ks.lamiral.info:/var/www/imapsync/examples/ -publish: upload_ks ksa +publish: dist upload_ks ksa echo Now ou can do make ml PUBLIC_FILES = ./ChangeLog ./NOLIMIT ./LICENSE ./CREDITS ./FAQ \ @@ -321,7 +328,7 @@ PUBLIC_FILES_W = ./W/style.css \ ./W/paypal.shtml ./W/paypal_return.shtml ./W/paypal_return_support.shtml -PUBLIC_FILES_IMAGES = ./W/images/logo_imapsync.png ./W/images/logo_imapsync_s.png +PUBLIC_FILES_IMAGES = ./W/images/ ml: dist_dir m4 -P W/ml_announce.in | mutt -H- diff --git a/README b/README index b5ee957..dc0a480 100644 --- a/README +++ b/README @@ -4,7 +4,7 @@ NAME More than 52 different IMAP server softwares supported with success, few failures. - $Revision: 1.555 $ + $Revision: 1.564 $ SYNOPSIS To synchronize imap account "foo" on "imap.truc.org" to imap account @@ -92,7 +92,7 @@ USAGE [--nofoldersizes] [--nofoldersizesatend] [--dry] [--debug] [--debugimap][--debugimap1][--debugimap2] - [--timeout
+Three Internet protocols share the big pie +access of almost all email accounts : POP, IMAP, HTTP. +
++The oldest one is POP, Post Office Protocol, it allows only +one main box, also called INBOX. +The second protocol is IMAP, Internet Message Access Protocol, which allows +a hierarchy of mailboxes also called folders, allows also concurrent accesses, +tagging with flags, search by many criterium like date, subject, size etc. +The third protocol is HTTP, HyperText Transfer Protocol, via webmails. +Webmails often offer the same features than imap servers and, +since webmails background is often an imap server, +a parallel access via IMAP. +
++Software imapsync is a command line tool to +copy, migrate, backup or synchronize IMAP mailboxes. +
++Command line means imapsync is not graphical, it is textual, +you have to type characters on your keyboard. +Your fingers will not suffer anyway because +I wrote examples nearly ready to go. +Most of the time you only have to change values +and adapt them to your context. +
++Do not be afraid, the mouse will not be forsaken. +You can still use the mouse to launch an editor, +select/copy/paste complete examples +and run the little script you edit with a doubleclick. +
++Imapsync runs on Unix or Windows. +It is because imapsync is written in the Perl language +and thanks to the Perl creators Perl runs everywhere. +Outside imapsync life is different; +Historically Windows came after Unix and the marvelous designers +of this old time decided it would be very cool +to not share the same syntax for doing the same things. +Thanks guys, great thinking! +
++To avoid you to learn by headaches a system you do not master +I will give all examples in both worlds, Unix and Windows. +Macintosh users are in the Unix world now but do not tell them, +it can hurt the olders. +
+ ++Imapsync has many options but you can ignore most of them +and still make great transfers. +
++In this documentation I write all the examples as a complete example. +In order to simplify the reading or the printing, +the command is written on several lines. +It could be written on one single line; +if you prefer the whole command on one line then +just remove the last character of each line, +it is the "\" character on Unix examples +or the "^" character on Windows examples. +
++For example, on Unix +
++ imapsync \ + --host1 imap.truc.org \ + --user1 foo \ + --password1 secret1 \ + ... ++
+is equivalent to +
++ imapsync --host1 imap.truc.org --user1 foo --password1 secret1 ... ++ +
+and on Windows +
++ imapsync ^ + --host1 imap.truc.org ^ + --user1 foo ^ + --password1 secret1 ^ + ... ++
+is equivalent to +
++ imapsync --host1 imap.truc.org --user1 foo --password1 secret1 ... ++ + + + + diff --git a/TUTORIAL.t2t b/TUTORIAL.t2t new file mode 100644 index 0000000..996a2c1 --- /dev/null +++ b/TUTORIAL.t2t @@ -0,0 +1,97 @@ + + + +% $Id: TUTORIAL.t2t,v 1.2 2013/08/16 00:48:57 gilles Exp gilles $ + += Tutorial for imapsync = + +== Introduction == + +Three Internet protocols share the big pie +access of almost all email accounts : POP, IMAP, HTTP. + +The oldest one is POP, Post Office Protocol, it allows only +one main box, also called INBOX. +The second protocol is IMAP, Internet Message Access Protocol, which allows +a hierarchy of mailboxes also called folders, allows also concurrent accesses, +tagging with flags, search by many criterium like date, subject, size etc. +The third protocol is HTTP, HyperText Transfer Protocol, via webmails. +Webmails often offer the same features than imap servers and, +since webmails background is often an imap server, +a parallel access via IMAP. + + +Software imapsync is a command line tool to +copy, migrate, backup or synchronize IMAP mailboxes. + + +Command line means imapsync is not graphical, it is textual, +you have to type characters on your keyboard. +Your fingers will not suffer anyway because +I wrote examples nearly ready to go. +Most of the time you only have to change values +and adapt them to your context. + +Do not be afraid, the mouse will not be forsaken. +You can still use the mouse to launch an editor, +select/copy/paste complete examples +and run the little script you edit with a doubleclick. + +Imapsync runs on Unix or Windows. +It is because imapsync is written in the Perl language +and thanks to the Perl creators Perl runs everywhere. +Outside imapsync life is different; +Historically Windows came after Unix and the marvelous designers +of this old time decided it would be very cool +to not share the same syntax for doing the same things. +Thanks guys, great thinking! + +To avoid you to learn by headaches a system you do not master +I will give all examples in both worlds, Unix and Windows. +Macintosh users are in the Unix world now but do not tell them, +it can hurt the olders. + + +== Conventions == + +Imapsync has many options but you can ignore most of them +and still make great transfers. + +In this documentation I write all the examples as a complete example. +In order to simplify the reading or the printing, +the command is written on several lines. +It could be written on one single line; +if you prefer the whole command on one line then +just remove the last character of each line, +it is the "\" character on Unix examples +or the "^" character on Windows examples. + +For example, on Unix + +``` + imapsync \ + --host1 imap.truc.org \ + --user1 foo \ + --password1 secret1 \ + ... +``` +is equivalent to +``` + imapsync --host1 imap.truc.org --user1 foo --password1 secret1 ... +``` + +and on Windows +``` + imapsync ^ + --host1 imap.truc.org ^ + --user1 foo ^ + --password1 secret1 ^ + ... +``` +is equivalent to +``` + imapsync --host1 imap.truc.org --user1 foo --password1 secret1 ... +``` + + + diff --git a/VERSION b/VERSION index 0a92d41..4b5d34e 100644 --- a/VERSION +++ b/VERSION @@ -1 +1 @@ -1.555 +1.564 diff --git a/VERSION_EXE b/VERSION_EXE index 35f5e47..4b5d34e 100644 --- a/VERSION_EXE +++ b/VERSION_EXE @@ -1 +1 @@ -1.558 +1.564 diff --git a/W/.BUILD_EXE_TIME b/W/.BUILD_EXE_TIME index c35dff0..bc03f25 100644 --- a/W/.BUILD_EXE_TIME +++ b/W/.BUILD_EXE_TIME @@ -224,3 +224,7 @@ 1375497013 END 1.558 : samedi 3 août 2013, 04:30:13 (UTC+0200) 1375534760 BEGIN 1.558 : samedi 3 août 2013, 14:59:20 (UTC+0200) 1375536286 END 1.558 : samedi 3 août 2013, 15:24:46 (UTC+0200) +1376617407 BEGIN 1.563 : vendredi 16 août 2013, 03:43:27 (UTC+0200) +1376618294 END 1.563 : vendredi 16 août 2013, 03:58:14 (UTC+0200) +1376856084 BEGIN 1.564 : dimanche 18 août 2013, 22:01:24 (UTC+0200) +1376856924 END 1.564 : dimanche 18 août 2013, 22:15:24 (UTC+0200) diff --git a/W/learn/imapbyhand b/W/learn/imapbyhand index fc8e169..ce04934 100644 --- a/W/learn/imapbyhand +++ b/W/learn/imapbyhand @@ -1,4 +1,5 @@ +# $Id: $ # How to remove a message by hand. telnet imap.truc.com 143 @@ -10,3 +11,21 @@ a64 STORE 1:1 +FLAGS (\DELETED) a75 EXPUNGE a86 LOGOUT +# When no SEARCH ALL available +1 LOGIN test@coook.cn 1234@com +3 SELECT INBOX +4 UID SEARCH 1:11638 +5 UID FETCH 11620:11637 (RFC822.SIZE) +6 UID FETCH 11000:11637 (RFC822.SIZE) +7 UID FETCH 2:11637 (RFC822.SIZE) +8 UID FETCH 1:11637 (RFC822.SIZE) +9 UID FETCH 1:11638 (RFC822.SIZE) +10 UID FETCH 1:11639 (RFC822.SIZE) +10 UID FETCH 11000:11640 (RFC822.SIZE) BAD + +10 UID FETCH 1:11639 (RFC822.SIZE) OK + +11 STATUS INBOX MESSAGES +11 STATUS INBOX (MESSAGES) +11 STATUS INBOX (MESSAGES UIDNEXT) + diff --git a/W/paypal_reply/paypal_build_invoices b/W/paypal_reply/paypal_build_invoices index 19111f3..9cf0810 100755 --- a/W/paypal_reply/paypal_build_invoices +++ b/W/paypal_reply/paypal_build_invoices @@ -1,6 +1,6 @@ #!/bin/sh -# $Id: paypal_build_invoices,v 1.54 2013/07/28 04:19:32 gilles Exp gilles $ +# $Id: paypal_build_invoices,v 1.55 2013/08/17 23:43:38 gilles Exp gilles $ # usage: sh paypal_build_invoices /g/var/paypal_invoices/???? @@ -39,7 +39,8 @@ cp /home/gilles/public_html/AGIL/factures/000/facture_imapsync-000.tex /g/var/pa #/g/public_html/imapsync/W/paypal_reply/paypal_bilan --write_invoices --first_in 2519 /g/paypal/paypal_2013_04_complet.csv #/g/public_html/imapsync/W/paypal_reply/paypal_bilan --write_invoices --first_in 2572 /g/paypal/paypal_2013_05_complet.csv #/g/public_html/imapsync/W/paypal_reply/paypal_bilan --write_invoices --first_in 2627 /g/paypal/paypal_2013_06_complet.csv -/g/public_html/imapsync/W/paypal_reply/paypal_bilan --write_invoices --first_in 2682 /g/paypal/paypal_2013_07_complet.csv +#/g/public_html/imapsync/W/paypal_reply/paypal_bilan --write_invoices --first_in 2682 /g/paypal/paypal_2013_07_complet.csv +/g/public_html/imapsync/W/paypal_reply/paypal_bilan --write_invoices --first_in 2741 /g/paypal/paypal_2013_08_complet.csv : /g/public_html/imapsync/W/paypal_reply/paypal_bilan --first_in 147 /g/paypal/paypal_2010_11_complet.csv : /g/public_html/imapsync/W/paypal_reply/paypal_bilan --first_in 214 /g/paypal/paypal_2010_12_complet.csv @@ -73,9 +74,10 @@ cp /home/gilles/public_html/AGIL/factures/000/facture_imapsync-000.tex /g/var/pa : /g/public_html/imapsync/W/paypal_reply/paypal_bilan --first_in 2519 /g/paypal/paypal_2013_04_complet.csv : /g/public_html/imapsync/W/paypal_reply/paypal_bilan --first_in 2572 /g/paypal/paypal_2013_05_complet.csv : /g/public_html/imapsync/W/paypal_reply/paypal_bilan --first_in 2627 /g/paypal/paypal_2013_06_complet.csv +: /g/public_html/imapsync/W/paypal_reply/paypal_bilan --first_in 2682 /g/paypal/paypal_2013_07_complet.csv set -x -: /g/public_html/imapsync/W/paypal_reply/paypal_bilan --first_in 2682 /g/paypal/paypal_2013_07_complet.csv +: /g/public_html/imapsync/W/paypal_reply/paypal_bilan --first_in 2741 /g/paypal/paypal_2013_08_complet.csv set +x # La totale diff --git a/imapsync b/imapsync index 4c8a44b..7bc80e1 100755 --- a/imapsync +++ b/imapsync @@ -22,7 +22,7 @@ Synchronises mailboxes between two imap servers. Good at IMAP migration. More than 52 different IMAP server softwares supported with success, few failures. -$Revision: 1.558 $ +$Revision: 1.564 $ =head1 SYNOPSIS @@ -114,7 +114,7 @@ The option list: [--nofoldersizes] [--nofoldersizesatend] [--dry] [--debug] [--debugimap][--debugimap1][--debugimap2] - [--timeout
Now the long reported success stories list:
-53 different imap server softwares supported!
+55 different imap server softwares supported!
[host1] means "source server" and [host2] means "destination server":