first commit

FAQ

@@ -0,0 +1 @@
+FAQ.d/FAQ.General.txt

FAQ.d/.htaccess

@@ -0,0 +1 @@
+htaccess.txt

FAQ.d/FAQ.APPEND_errors.txt

@@ -0,0 +1,81 @@
+#!/bin/cat
+$Id: FAQ.APPEND_errors.txt,v 1.6 2019/02/16 22:38:49 gilles Exp gilles $
+
+This document is also available online at
+https://imapsync.lamiral.info/FAQ.d/
+https://imapsync.lamiral.info/FAQ.d/FAQ.APPEND_errors.txt
+
+=======================================================================
+              Dealing with Imapsync APPEND errors.
+=======================================================================
+
+Questions answered in this FAQ are:
+
+Q. For some messages, the imapsync log says 
+   "could not append", sometimes followed by an explicit message 
+   describing what went wrong, or sometimes followed by a not very
+   useful message "socket closed while reading data from server"
+   What can I do?
+
+R0. Well, the problem is that the "socket closed ..." error message happens
+    in several different issues. So I list here several potential issues
+    and their solutions if they exist.
+
+R1. On Windows, add --regexmess "s,(.{9900}),$1\r\n,g"
+
+Some messages have too long lines; for example, 
+Exchange supports only 9900 characters line length.
+Use this option to add "new line" characters (also called CRLF)
+to wrap lines longer than 9900 characters. 
+The regex means "add one CRLF every 9900".
+
+  imapsync.exe ... --regexmess "s,(.{9900}),$1\r\n,g"
+
+R2. On Unix, add --pipemess "reformime -r7". The command reformime
+    usually belongs to the package called "maildrop".
+
+  imapsync ... --pipemess "reformime -r7"
+
+I reproduce here the "reformime" manual part explaining what does 
+the option "-r7" 
+
+$ man reformime |more
+REFORMIME(1)                Double Precision, Inc.                REFORMIME(1)
+
+NAME
+       reformime - MIME E-mail reformatting tool
+
+SYNOPSIS
+       reformime [options...]
+
+DESCRIPTION
+       reformime is a utility for reformatting MIME messages.
+
+       Generally, reformime expects to see an RFC 2045[1] compliant message on
+       standard input
+...
+OPTIONS
+...
+       -r
+           Rewrite message, adding or standardizing RFC 2045[1] MIME headers.
+
+       -r7
+           Like -r but also convert 8bit-encoded MIME sections to
+           quoted-printable.
+...
+   Adding RFC 2045 MIME headers
+       The -r option performs the following actions:
+
+       If there is no Mime-Version:, Content-Type:, or
+       Content-Transfer-Encoding: header, reformime adds one.
+
+       If the Content-Transfer-Encoding: header contains 8bit or raw, but only
+       seven-bit data is found, reformime changes the
+       Content-Transfer-Encoding header to 7bit.
+
+       -r7 does the same thing, but also converts 8bit-encoded content that
+       contains eight-bit characters to quoted-printable encoding.
+
+       
+R2. 
+       

FAQ.d/FAQ.Admin_Authentication.txt

@@ -0,0 +1,54 @@
+#!/bin/cat
+$Id: FAQ.Admin_Authentication.txt,v 1.10 2019/10/31 23:13:50 gilles Exp gilles $
+
+This documentation is also available online at
+https://imapsync.lamiral.info/FAQ.d/
+https://imapsync.lamiral.info/FAQ.d/FAQ.Admin_Authentication.txt
+
+
+=======================================================================
+            Imapsync tips about imap admin authentication.
+=======================================================================
+
+It can be useful to authenticate without knowing each user password.
+
+Using an admin account to authenticate is not a standard feature
+supported by all imap servers. Sometimes it is implemented via the 
+--authuser1 option, sometimes not. It depends on the imap software
+server and its configuration.
+
+You have to follow this road:
+ * Determine what is the imap software server
+ * Find out wether it supports an admin account or not
+ * If no, leave this reading, take an handkerchief and cry
+ * If yes, search how the imap software server supports 
+   an admin account (see below)
+ * Figure out wether an admin account is actually configured or not,
+ * If not then configure it,
+ * Finally, check an imapsync authentication via this admin account for
+   a standard user, option --justlogin is nice for doing this.
+ * Use it for all users.
+ * Next, read their email messages, enter their personnal life etc. 
+   I'm kidding.
+
+Good luck!
+
+Known imap software servers supporting imap admin authentication:
+
+  * Exchange 2003/2007/2010/2013/2016. See the file FAQ.Exchange.txt
+  * Office365.  See the file FAQ.Exchange.txt
+  * Gmail.      See the file FAQ.XOAUTH2.txt
+  * Dovecot.    See the file FAQ.Dovecot.txt
+  * Zimbra.     See the file FAQ.Zimbra.txt
+  * Kerio       See the file FAQ.Kerio.txt
+  * UW-imap.    See the file FAQ.General.txt
+  * Cyrus-imap. See the file FAQ.General.txt
+  * Sun Java Enterprise System/SunOne/iPlanet. See the file FAQ.General.txt
+
+Known imap software servers NOT supporting imap admin authentication:
+
+  * Domino Lotus Notes. See FAQ.Handkerchief.txt
+  * SmartCloud Notes.   Same joke.
+
+=======================================================================
+=======================================================================

FAQ.d/FAQ.Archiving.txt

@@ -0,0 +1,143 @@
+#!/bin/cat
+$Id: FAQ.Archiving.txt,v 1.18 2019/10/23 17:56:28 gilles Exp gilles $
+
+This documentation is also available online at
+https://imapsync.lamiral.info/FAQ.d/
+https://imapsync.lamiral.info/FAQ.d/FAQ.Archiving.txt
+
+=======================================================================
+          Imapsync issues and tips about archiving
+=======================================================================
+
+Questions answered in this FAQ are:
+
+Q. How can I archive different accounts on the same destination account,
+   each account on a separate folder?
+
+Q. How can I restore a complete account archived in a subfolder, like
+   with the option --subfolder2?
+
+Q. How to move emails from one IMAP folder to another either on the 
+   same IMAP server or a different one?
+   For example, all messages older than 1 year, move from INBOX to Archive.
+
+Q. Can imapsync be used to maintain and restore a local offline copy 
+   of a mailbox, eg for backup purposes, using Mbox or Maildir 
+   format, so that if the server fails, then the mailbox could be 
+   reinstated?
+
+Q. How to archive a whole year in a subfolder?
+
+Q. How to archive a whole year in subfolders but without subsubfolders?
+
+https://imapsync.lamiral.info/FAQ.d/FAQ.Archiving.txt
+=======================================================================
+Q. How can I archive different accounts on the same destination account,
+   each account on a separate folder?
+
+R. Use --subfolder2 
+
+ --subfolder2   str  : Syncs the whole host1 folders hierarchy under the
+                       host2 given folder str.
+                       (It does it internally by adding two --regextrans2 
+                       options before all others.)
+
+Examples:
+
+  imapsync ... --user1 Foo --subfolder2 FooArchiv
+
+  imapsync ... --user1 Bar --subfolder2 BarArchiv
+
+In case you need a very strict sync, add options 
+--delete2 --delete2foldersonly "FooArchiv"
+(or "BarArchiv" for the second example).
+It will delete on account2 what is not on account1 but only in the right place, 
+ie, the subfolder "FooArchiv".
+
+Examples:
+  
+  imapsync ... --user1 Foo --subfolder2 FooArchiv --delete2 --delete2foldersonly "FooArchiv" 
+
+  imapsync ... --user1 Bar --subfolder2 BarArchiv --delete2 --delete2foldersonly "BarArchiv" 
+
+=======================================================================
+Q. How can I restore a complete account archived in a subfolder, like
+   with the option --subfolder2?
+
+R. Use --subfolder1
+
+ --subfolder1   str  : Syncs the host1 folders hierarchy under folder str
+                        to the root hierarchy of host2.
+                        It's the couterpart of a sync done by --subfolder2
+                        when doing it in the reverse order. 
+                        Backup/Restore scenario:
+                        Use --subfolder2 str for a backup to the folder str
+                        on host2. Then use --subfolder1 str for restoring 
+                        from the folder str, after inverting 
+                        host1/host2 user1/user2 values.
+
+Examples:
+
+  imapsync ... --user2 Foo --subfolder1 FooArchiv
+
+  imapsync ... --user2 Bar --subfolder1 BarArchiv
+
+
+=======================================================================
+Q. How to move emails from one IMAP folder to another either on the 
+   same IMAP server or a different one?
+   For example, all messages older than 1 year, move from INBOX to Archive.
+ 
+R1. Solution:
+
+  imapsync ... --minage 365 --folder Inbox --f1f2 INBOX=Archive --delete1 --noexpungeaftereach
+
+Add option --noexpungeaftereach if speed is a concern.
+Add option --delete1 if you want to move messages, instead of just copy/sync them.
+
+R2. See also file FAQ.Folders_Mapping.txt
+
+
+https://imapsync.lamiral.info/FAQ.d/FAQ.Archiving.txt
+=======================================================================
+Q. Can imapsync be used to maintain and restore a local offline copy 
+   of a mailbox, eg for backup purposes, using Mbox or Maildir 
+   format, so that if the server fails, then the mailbox could be 
+   reinstated?
+
+R1. No. Imapsync plays with IMAP servers only.
+
+R2. Imapsync can't but rick-sanders-imap-tools can!
+    See https://github.com/andrewnimmo/rick-sanders-imap-tools
+    
+    Back up and restore IMAP accounts with imapdump.pl and dumptoIMAP.pl
+    It looks like imapdump.pl has options to avoid duplicates and be
+    in an update mode. There are options -u -U
+    [-u] Don't dump messages already dumped
+    [-U] Don't dump message if it already exists in the dump directory
+    I wonder the difference, I've never used Rick's tools.
+
+    Remember that doing backups without trying the restore process
+    is more dangerous than doing no backups at all. No backups makes
+    people act in a safer way, well, usually...
+    
+R3. Use ImportExportTools for Mozilla Thunderbird by Paolo Kaosmos. 
+    ImportExportTools does not do IMAP as a destination.
+
+=======================================================================
+Q. How to archive a whole year in a subfolder?
+
+R.
+
+  imapsync ... --search "SENTSINCE 1-Jan-2018 SENTBEFORE 31-Dec-2018" \
+      --folder2 ARCHIVE_2018 --justfolders --dry
+
+=======================================================================
+Q. How to archive a whole year in subfolders but without subsubfolders?
+
+
+  imapsync ... --search "SENTSINCE 1-Jan-2018 SENTBEFORE 31-Dec-2018" \
+             --sep2 _ --regextrans2 's{(.*)}{Archive_$1_2018}' --justfolders --dry
+
+=======================================================================
+=======================================================================

FAQ.d/FAQ.Authentication_failure.txt

@@ -0,0 +1,95 @@
+#!/bin/cat
+$Id: FAQ.Authentication_failure.txt,v 1.9 2019/01/11 13:13:08 gilles Exp gilles $
+
+This documentation is also available online at
+https://imapsync.lamiral.info/FAQ.d/
+https://imapsync.lamiral.info/FAQ.d/FAQ.Admin_Authentication.txt
+
+=======================================================================
+              Imapsync authentication issues
+=======================================================================
+
+Questions answered in this FAQ are:
+
+Q. Imapsync fails with the following error, what can I do?
+Host1 failure: Error login on [imap.example.com] with user [foo] auth [LOGIN]: 2 NO [AUTHENTICATIONFAILED] Authentication failed
+
+Q. Imapsync fails with the following error, what can I do?
+   Host2 failure: Error login on [imap.example.com] with user [foo] auth [LOGIN]: 2 BAD Invalid characters in atom 
+
+
+=======================================================================
+Q. Imapsync fails with the following error, what can I do?
+Host1 failure: Error login on [imap.example.com] with user [foo] auth [LOGIN]: 2 NO [AUTHENTICATIONFAILED] Authentication failed
+
+
+R. One over four imapsync syncs ends up quickly with the error message 
+   "Authentication failed" or "NO LOGIN failed" or similar. 
+   Authentication failure is the primary failure with imapsync
+   and since nothing tangible can be done without authentication, 
+   this stage must succeed to go further.
+
+Here are some advices to get you pass this difficult stage of authentication:
+
+  * Triple check each credential parameter, there are three parameters at each side:
+     * triple check --host1
+     * triple check --user1
+     * triple check --password1
+     * triple check --host2
+     * triple check --user2
+     * triple check --password2
+
+   * If you can authenticate successfully with an other imap client software 
+     like Thunderbird or Outlook or Sparrow then it is a very good sign to 
+     authenticate successfully with imapsync. Examine the parameters of 
+     this other imap client and copy them as is for imapsync.
+
+   * Use option --showpasswords
+     At the beginning of the output, imapsync dumps all its command
+     line parameters; it's the line after "Command line used:".
+     With --showpasswords, imapsync prints the passwords received 
+     instead of the string MASKED. It helps for debugging quoting issues.
+     Option --showpasswords shows passwords again when the IMAP dialog
+     is dumped by --debugimap option. Search for a line like 
+     "Sending: 2 LOGIN test1 secret1" (secret1 is the password here)
+
+
+   * It is sometimes very hard to quote correctly unusual characters,
+     especially on Windows. See 
+     https://imapsync.lamiral.info/FAQ.d/FAQ.Passwords_on_Windows.txt
+     https://imapsync.lamiral.info/FAQ.d/FAQ.Passwords_on_Unix.txt
+     The quickest trick may be to change the password temporally
+     with easy characters like the classical alphabet, a long
+     string still ensure strong security.
+
+   * Sometimes some servers announce they support LOGIN but it
+     actually fails because the authentication mechanism
+     working is something else like CRAM-MD5 or PLAIN. 
+     So:
+       * Try --authmech1 CRAM-MD5 (or --authmech2 CRAM-MD5)
+       * Try --authmech1 PLAIN    (or --authmech2 PLAIN)
+
+   * If you want to play manually the IMAP protocol on your server, 
+     here is an example with the command telnet, user test1
+     and password secret1 on the host test.lamiral.info.
+
+     telnet test.lamiral.info 143
+     c1 LOGIN test1 "secret1" 
+     c2 LOGOUT
+
+     Same example using an ssl conneection:
+     
+     telnet-ssl -z ssl test.lamiral.info 993
+     c1 LOGIN test1 "secret1" 
+     c2 LOGOUT
+   
+=======================================================================
+Q. Imapsync fails with the following error, what can I do?
+   Host2 failure: Error login on [imap.example.com] with user [foo] auth [LOGIN]: 2 BAD Invalid characters in atom 
+
+R. It might be a Dovecot imap server. The password string might 
+   contain special characters that Dovecot doesn't like. Change them.
+ 
+ =======================================================================
+ =======================================================================
+ 

FAQ.d/FAQ.Big_Mailbox.txt

@@ -0,0 +1,45 @@
+#!/bin/cat
+$Id: FAQ.Big_Mailbox.txt,v 1.4 2019/07/31 10:37:15 gilles Exp gilles $
+
+This document is also available online at
+https://imapsync.lamiral.info/FAQ.d/
+https://imapsync.lamiral.info/FAQ.d/FAQ.Big_Mailbox.txt
+
+
+=====================================================================
+            Imapsync tips to deal with huge mailboxes
+=====================================================================
+
+Questions answered in this FAQ are:
+
+Q. How to deal with huge mailboxes, whose size is over dozens of GB?
+
+Now the questions again with their answers.
+
+=====================================================================
+Q. How to deal with huge mailboxes, whose size is over dozens of GB?
+
+R1. It should be ok with imapsync.  
+
+In case imapsync seems to stall when sizing the folders or before
+syncing a huge folder and you wander wether it is doing something or
+just frozen, you can add option --debugimap. Option --debugimap shows
+what is currently done, it's quite a big output but it helps waiting,
+saying to ourselves "ok it's long but it's working, let's wait a
+little more".  The real purpose of --debugimap is to show genuine IMAP
+commands used and their responses. The problem with --debugimap is
+that it is very verbose and so with a big mailbox it generates a very
+BIG logfile.
+
+R2. If it is not ok with imapsync then consider spliting the whole 
+sync into smaller chunks using --search
+
+For example, select messages only for a given year:
+
+...
+..imapsync ... --search "SENTSINCE 1-Jan-2017 SENTBEFORE 31-Dec-2017"
+  imapsync ... --search "SENTSINCE 1-Jan-2018 SENTBEFORE 31-Dec-2018"
+  imapsync ... --search "SENTSINCE 1-Jan-2019 SENTBEFORE 31-Dec-2019"
+
+=====================================================================
+=====================================================================

FAQ.d/FAQ.Contacts_Calendars.txt

@@ -0,0 +1,106 @@
+#!/bin/cat
+$Id: FAQ.Contacts_Calendars.txt,v 1.12 2019/04/30 13:04:18 gilles Exp gilles $
+
+This documentation is also available online at
+https://imapsync.lamiral.info/FAQ.d/
+https://imapsync.lamiral.info/FAQ.d/FAQ.Contacts_Calendars.txt
+
+=======================================================================
+           Imapsync issues about syncing Contacts & Calendars.
+=======================================================================
+
+Questions answered in this FAQ are:
+
+Q. Can I copy or sync Calendars or Contacts with imapsync?
+Q. Can I copy or sync Chat messages with imapsync?
+Q. How can I avoid copying Calendar or Contacts folders?
+Q. How can I copy or synchronize Calendars or Contacts?
+
+Now the questions again with their answers.
+
+=======================================================================
+Q. Can I copy or sync Calendars or Contacts with imapsync?
+
+R. No, Imapsync can't migrate Contacts and Calendars. 
+  It's because most IMAP servers don't get contacts and calendars 
+  events via IMAP. In other words, messages synced by imapsync from 
+  Calendars or Contacts folders are not used by email servers to set 
+  or get the contacts or calendars. 
+  No way via IMAP, no way via imapsync.
+  
+  So it's a good idea to avoid syncing contacts and calendars when
+  using imapsync. See below
+  "How can I avoid copying Calendar or Contacts folders?"
+  
+  But see also the question at the end of this document
+  "How can I copy or synchronize Calendars or Contacts?".
+
+=======================================================================
+Q. Can I copy or sync Chat messages with imapsync?
+
+R. No, Imapsync can't migrate Chat messages (those in GSuite for example).
+   The explanation is the same as with Calendars or Contacts.
+
+=======================================================================
+Q. How can I avoid copying Calendar or Contacts folders?
+
+R. You can avoid synchronizing Calendar or Contacts folders with
+  the --exclude option. First you have to search what is their
+  exact name. The folders listing printed by imapsync at the
+  beginning of a run will surely help to find their names. 
+  Assuming their names are "Calendars" and "Contacts" use then:
+
+    imapsync ... --exclude "Calendar" --exclude "Contacts" 
+
+  Be aware that this syntax will exclude all folders that have
+  Calendar or Contacts in their names, as a substring,
+  like "MyCalendarZ" or "TheContactsImDoneWith". 
+  Also, case matters: "calendar" does not match "Calendar".
+  
+  To stritly avoid only "Calendar" or "Contacts" use 
+  the following
+
+  On windows:
+  
+    imapsync ... --exclude "^Calendar$" --exclude "^Contacts$" 
+
+  On Unix:
+  
+    imapsync ... --exclude '^Calendar$' --exclude '^Contacts$'
+    or
+    imapsync ... --exclude "^Calendar\$" --exclude "^Contacts\$" 
+
+
+=======================================================================
+Q. How can I copy or synchronize Calendars or Contacts?
+
+R1. Synchronizing Calendars or Contacts can't be done with imapsync. 
+    For detailed explanations, see the question above
+    "Can I copy or sync Calendars or Contacts with imapsync?".
+
+R2. Synchronizing Calendars or Contacts can be done, not
+    with imapsync, depending on the imap server software tool used.
+
+a) From Exchange to Exchange, export contacts and calendar to
+   PST format files on host1 and import them on host2.
+
+b) From Gmail to Gmail, export and import calendars in ical format, 
+   extension for those files is .ics.
+   Contacts can be copied using a csv file. See the help page
+   http://support.google.com/mail/bin/topic.py?hl=en&topic=1669027
+
+c) Etc. Search the web. There's also specific tools and paid services.
+   There's no silver bullet to migrate Calendars and Contacts,
+   if you find one, tell me!
+   Also consider asking experts at Sumatra company 
+   https://twitter.com/sumatra_dev
+   http://sumatra.com/
+   
+d) I plan to make tools for that but so far nothing has began
+   more than this discussion:
+http://www.linux-france.org/prj/imapsync_list/msg01797.html
+http://www.linux-france.org/prj/imapsync_list/msg01811.html
+
+
+=======================================================================
+=======================================================================

FAQ.d/FAQ.Dates.txt

@@ -0,0 +1,122 @@
+#!/bin/cat
+$Id: FAQ.Dates.txt,v 1.11 2019/12/23 12:46:50 gilles Exp gilles $
+
+This documentation is also available online at
+https://imapsync.lamiral.info/FAQ.d/
+https://imapsync.lamiral.info/FAQ.d/FAQ.Dates.txt
+
+=======================================================================
+               Imapsync tips about dates.
+=======================================================================
+
+Questions answered in this FAQ are:
+
+Q. We have found that the time and date displayed have been changed to 
+   the time at which the file was synchronized. What happened? Any fix?
+
+Q. Is there a way to set any message with 
+   "Date: (Invalid)" to a valid one like 
+   "Date: Thu, 1 Jun 2017 23:59:59 +0000"?
+
+
+=======================================================================
+Q. We have found that the time and date displayed have been changed to 
+   the time at which the file was synchronized. What happened? Any fix?
+
+R. This is the case by default with some email readers like:
+   - Outlook 2003
+   - Ipad
+   - Iphone
+   - spark https://sparkmailapp.com/  (iphone app)
+   - Edison mail  https://apps.apple.com/us/app/email-edison-mail/id922793622 (iphone app)
+   - ...
+   
+but not with:
+
+   - Mutt
+   - Thunderbird
+   - Zimbra
+   - Gmail
+
+First, a thing to keep in mind. 
+
+Imapsync does not touch any byte of messages unless told to do so by
+special and rarely used options like --regexmess or --pipemess.
+Messages on both parts should be exactly identical because imapsync 
+does a verbatim sync of all messages, by default.
+
+Now I explain the whole picture about dates of messages.
+
+There are several different dates attached to any message.
+
+First, there is the "Date:" header, which belongs to the message itself.
+You can see this "Date:" header line by asking "View->Message Source"
+in most email client software (Ctrl-u in Thunderbird).
+Most of the time, this "Date:" header date is set by the MUA, 
+MUA stands for "Mail User Agent".
+MUA can be Outlook, Thunderbird, a webmail or Mutt etc. 
+The "Date:" header is usually the date the message was written 
+or sent the first time, at the writer side. 
+This "Date:" header line is never changed by any transfer or copy.
+
+If an email reader uses the "Date:" header for displaying the date of
+a message then no problem should arise.
+
+Another date is the "internal date". In IMAP, the internal date is
+handled by the imap server and normally it corresponds to the arrival
+date in the mailbox.  This date is not part of the email message
+itself, it is a metadata kept by the imap server.
+
+The IMAP protocol allows the internal date to be set by an email client
+when a message is delivered by the imap APPEND command.
+Imapsync synchronizes these internal dates, by default, so internal dates 
+on host2 should then be the same as the internal dates on host1.
+
+If an email reader uses the internal date for displaying the date of a
+message then the sync date problem only occurs when the host2 imap
+server ignores the internal date given by imapsync during the APPEND
+imap command. It happens with some imap servers. Bad luck.
+
+There are also the "Received:" header lines. Each time a message
+travels a SMTP server, this one adds a "Received:" header
+line. Sometimes some email clients use the last "Received:" header
+date as the date of the message. And some IMAP servers software add a
+"Received:" line after and imap transfer. If those both conditions are
+met then the date displayed become the transfer date even if imapsync
+has done its best to keep all the dates synchronized. Bad luck.
+
+
+Solutions: 
+a) Use another email client or configure it in order that it sorts messages
+   by sent dates, the "Date:" header line.
+
+b) Use a imap server that respects the imap RFC and accepts 
+   the internal date set by imapsync.
+
+c) Try to understand why the email client software shows another date 
+   than the "Date:" header line.
+
+=======================================================================
+Q. Is there a way to set any message with 
+   "Date: (Invalid)" to a valid one like 
+   "Date: Thu, 1 Jun 2017 23:59:59 +0000"?
+
+R. Yes, there is a way with option --regexmess 
+
+First, let's select only messages with a buggy Date header:
+  
+  --search "HEADER Date Invalid"
+
+Second, let's change this line by a valid one,
+
+on windows:
+
+  --regexmess "s{\A(.*?(?! ^$))^Date:\ \(Invalid\)(.*?)$}{$1Date: Thu, 1 Jun 2017 23:59:59 +0000}xms"
+
+on Unix (replaced  enclosing double-quotes " by single quotes ' ):
+
+  --regexmess 's{\A(.*?(?! ^$))^Date:\ \(Invalid\)(.*?)$}{$1Date: Thu, 1 Jun 2017 23:59:59 +0000}xms'
+  
+
+=======================================================================
+=======================================================================

FAQ.d/FAQ.David_Tobit.txt

@@ -0,0 +1,54 @@
+#!/bin/cat
+$Id: FAQ.David_Tobit.txt,v 1.4 2019/03/28 17:58:53 gilles Exp gilles $
+
+This documentation is also available online at
+https://imapsync.lamiral.info/FAQ.d/
+https://imapsync.lamiral.info/FAQ.d/FAQ.David_Tobit.txt
+
+
+=======================================================================
+             Imapsync tips for David Tobit imap server
+=======================================================================
+
+
+
+=======================================================================
+Q. Migrating to David Tobit V12
+   (Banner: "* OK IMAP4rev1 David.fx Mail Access Server MA-12.00a (0271)")
+
+  imapsync ... --sep2 / --create_folder_old
+
+Thanks to Ludwig Behm
+
+=======================================================================
+Q. Migrating from David Tobit V10 (DvISE Mail Access Server MA-...)
+
+R. Use the following options:
+
+  imapsync ... --prefix1 ""    --sep1 /  --idatefromheader ^
+               --nofoldersizes --useuid --nocheckmessageexists
+
+=======================================================================
+Q. Migrating from David Tobit V8
+   (Banner: "* OK IMAP4rev1 DvISE Mail Access Server MA-8.10a (0126)")
+
+First try above V10 solution since improvments have been made
+to support Tobit.
+
+R. Use the following options :
+
+  imapsync ... --prefix1 INBOX. --sep1 / --subscribe --subscribed 
+
+=======================================================================
+Q. Migrating from Tobit David Server 6 
+   (Banner: "* OK IMAP4rev1 DvISE Mail Access Server MA-6.60a (0118)")
+
+First try above V10 solution since improvments have been made
+to support Tobit.
+
+R. Look at the discussion:
+http://www.linux-france.org/prj/imapsync_list/msg00583.html
+http://www.linux-france.org/prj/imapsync_list/threads.html#00583
+patch saved in ./patches/imapsync-1.337_tobit_V6.patch
+
+=======================================================================

FAQ.d/FAQ.Docker.txt

@@ -0,0 +1,65 @@
+#!/bin/cat
+# $Id: FAQ.Docker.txt,v 1.6 2019/12/11 15:39:14 gilles Exp gilles $
+
+This document is also available online at
+https://imapsync.lamiral.info/FAQ.d/
+https://imapsync.lamiral.info/FAQ.d/FAQ.Docker.txt
+
+=======================================================================
+            Installing and using imapsync docker image
+=======================================================================
+
+Questions answered in this FAQ are:
+
+Q. How can I install and use the imapsync Docker image on my system?
+
+Q. How can I install or update only the imapsync Docker image on my system?
+
+Q. Where is the imapsync Docker hub location?
+
+Q. Any tips for the Docker Mailcow distribution?
+
+
+Now the questions again with their answers.
+
+=======================================================================
+Q. How can I install and use the imapsync Docker image on my system?
+
+R. Install Docker on your system. Once Docker is installed on your system,
+   all you have to do in order to run imapsync is the command line:
+
+  docker run gilleslamiral/imapsync imapsync <usual imapsync arguments>
+
+=======================================================================
+Q. How can I install or update only the imapsync Docker image on my system?
+
+R. To install or update the imapsync image, run:
+
+  docker pull gilleslamiral/imapsync
+
+=======================================================================
+Q. Where is the imapsync Docker hub location?
+
+R. Here:
+
+  https://hub.docker.com/r/gilleslamiral/imapsync/
+
+=======================================================================
+Q. Any tips for the Docker Mailcow distribution?
+
+R. With the Mailcow distribution, imapsync is running inside a Docker 
+   container. Quoting Mathilde:
+
+To make it work with Mailcow, options should be added like this:
+
+  --regexflag=s/\\Indexed//gi
+
+Without spaces, without quotes.
+
+See the original Mathilde's comment:
+
+https://github.com/imapsync/imapsync/issues/201#issuecomment-559500077
+
+
+=======================================================================
+=======================================================================

FAQ.d/FAQ.Domino.txt

@@ -0,0 +1,130 @@
+#!/bin/cat
+# $Id: FAQ.Domino.txt,v 1.12 2019/10/31 23:13:31 gilles Exp gilles $
+
+This documentation is also available online at
+https://imapsync.lamiral.info/FAQ.d/
+https://imapsync.lamiral.info/FAQ.d/FAQ.Domino.txt
+
+
+=======================================================================
+               Imapsync tips for Domino.
+=======================================================================
+
+Questions answered in this FAQ are:
+
+Q. How to use imapsync from Domino Notes to XXX?
+
+Q. How to use imapsync from XXX to Domino Notes?
+
+Q. Whan I use --maxage imapsync sees no messages at all.
+   What can I do?
+
+Q. My usual email software client like Thunderbird sees more messages
+   than imapsync. How can it be possible?
+
+Now the questions again with their answers:
+
+
+=======================================================================
+Q. How to use imapsync from Domino Notes to XXX?
+
+R1. Use --domino1, like this:
+
+  imapsync ... --domino1
+
+
+R2. Or use the following options:
+
+On Windows use:
+
+  imapsync.exe ... --sep1 "\\" --prefix1 "" --messageidnodomain
+
+On Unix use:
+
+  imapsync ... --sep1 '\' --prefix1 '' --messageidnodomain
+
+=======================================================================
+Q. How to use imapsync from XXX to Domino Notes
+
+R1. Use --domino2, like this:
+
+  imapsync ... --domino2
+
+
+R2. Or follow this:
+
+Domino doesn't accept INBOX subfolders. 
+
+On Windows:
+
+  imapsync.exe ... ^
+    --sep2 "\\" --prefix2 "" --messageidnodomain ^
+    --regextrans2 "s,^Inbox\\(.*),$1,i"  
+
+On Unix:
+
+  imapsync ... \
+    --sep2 '\' --prefix2 '' --messageidnodomain \
+    --regextrans2 's,^Inbox\\(.*),$1,i'
+
+If you want to sync the complete host1 mailbox in a subfolder called OLDBOX use:
+
+On Windows:
+  imapsync.exe ... ^
+    --sep2 "\\" --prefix2 "" --messageidnodomain ^
+    --subfolder2 "OLDBOX" --justfolders --dry
+
+On Unix:
+  imapsync ... \
+  --sep2 '\' --prefix2 '' --messageidnodomain \
+  --subfolder2 'OLDBOX' --justfolders --dry
+    
+If the output is correct for you then remove --dry and have a run.
+Verify the folder hierarchy is good on host2 then remove --justfolders to
+sync the messages.
+
+For Domino with imapsync and Domino on Linux:
+(Thanks to Zafer)
+
+R. We've migrated about 5000 users from cyrus to lotus domino 853! 
+Mails are being copied into the new created lotus domino mailbox 
+retaining the existing folder structure from the old mail database.
+This means that sent mails can be found in the sent folder and 
+mails from the old inbox are copied into the new inbox
+We also marked migrated mails with the header Migratedbyus
+
+For Domino 853FP6 on Linux, we used this command on Unix:
+
+  imapsync \
+  --host1 hhh1  --user1 uuu1  --password1 ppp1 \
+  --host2 hhh2  --user2 uuu2  --password2 ppp2 \
+  --exclude "^INBOX/Trash"  --exclude 'Junk|Drafts' \
+  --regextrans2 's#^INBOX/Sent$#^Sent#' \
+  --prefix2 ""  --sep2 "\/" --messageidnodomain \
+  --regexmess 's{\A(.*?(?! ^$))^Date:(.*?)$}{$1Migratedbyus:$2\nx-MailDate:$2}gxms'
+
+=======================================================================
+Q. Whan I use --maxage imapsync sees no messages at all.
+   What can I do?
+
+R. Use --noabletosearch
+
+  imapsync ... --noabletosearch
+
+Same thing with --minage
+
+=======================================================================
+Q. My usual email software client like Thunderbird sees more messages
+   than imapsync. How can it be possible?
+
+R. (Issue given and solved by Falko Veith)
+   "As you might know, it is possible to replicate databases, aka mailboxes,
+   across domino servers. THAT is the explanation. Thunderbird and some Notes 
+   clients may be connected to one server and imapsync to another.
+   As funny and simply the solution is, as mysterious is why those two 
+   databases are not completely in sync - new emails are replicated but not
+   the old ones. One mystery solved - and a new one to go.
+
+Thanks to Falko Veith for this question and the answer!
+
+=======================================================================

FAQ.d/FAQ.Dovecot.txt

@@ -0,0 +1,52 @@
+#!/bin/cat
+$Id: FAQ.Dovecot.txt,v 1.7 2019/09/25 09:25:52 gilles Exp gilles $
+
+This documentation is also available online at
+https://imapsync.lamiral.info/FAQ.d/
+https://imapsync.lamiral.info/FAQ.d/FAQ.Dovecot.txt
+
+
+=======================================================================
+      Imapsync tips for Dovecot. Specific issues and solutions.
+=======================================================================
+
+
+Questions answered in this FAQ are:
+
+Q. Subfolders are not created by imapsync and the error is
+   "Mailbox doesn't allow inferior mailboxes"
+
+Q. How to migrate to Dovecot with an admin/MasterUser account?
+
+Now the questions again with their answers.
+
+=======================================================================
+Q. How to migrate to Dovecot with an admin/MasterUser account?
+
+R. Dovecot uses the same syntax as uw-imap
+
+  imapsync ... --user2="loginuser*admin_user" --password2 "admin_user_password"
+
+To setup a Dovecot MasterUser see 
+http://wiki2.dovecot.org/Authentication/MasterUsers
+
+=======================================================================
+Q. Subfolders are not created by imapsync and the error is
+   "Mailbox doesn't allow inferior mailboxes"
+
+R. Dovecot usually supports subfolders with messages and subfolders,
+   it's a Dovecot configuration issue.
+
+If you can change the Dovecot configuration dovecot.conf, 
+then try this:
+
+mail_location = maildir:~/Maildir:LAYOUT=fs
+
+See details at:
+https://superuser.com/questions/813362/sub-folders-in-dovecot
+https://wiki2.dovecot.org/MailLocation/Maildir
+
+
+
+=======================================================================
+=======================================================================

FAQ.d/FAQ.Duplicates.txt

@@ -0,0 +1,203 @@
+#!/bin/cat
+$Id: FAQ.Duplicates.txt,v 1.20 2019/05/17 10:10:30 gilles Exp gilles $
+
+This documentation is also available online at
+https://imapsync.lamiral.info/FAQ.d/
+https://imapsync.lamiral.info/FAQ.d/FAQ.Duplicates.txt
+
+=======================================================================
+            Imapsync tips about duplicated messages issues.
+=======================================================================
+
+=======================================================================
+Q. How can I know if imapsync will generate duplicates on a second run?
+
+R. To see if imapsync will generate duplicates on a second run, start
+   a second run with --dry option added. With --dry, imapsync will 
+   show whether it would mistakenly copy messages again, but without 
+   really copying them:
+
+     imapsync ... --dry 
+
+   The final stats should also show a positive value for the line 
+   "Messages skipped:" since most of the skipped messages are skipped 
+   because they are already on host2. Example of final stats:
+   
+++++ Statistics
+Transfer started on               : Thu Aug 31 04:28:32 2017
+Transfer ended on                 : Thu Aug 31 04:28:44 2017
+Transfer time                     : 11.7 sec
+Folders synced                    : 1/1 synced
+Messages transferred              : 0 
+Messages skipped                  : 1555
+
+=======================================================================
+Q: Multiple copies, duplicates, when I run imapsync twice ore more. 
+
+R0. First, some explanations to understand the issue. 
+Normally and by default, imapsync doesn't generate duplicates.
+So, if it does  generate duplicates it means a problem occurs
+with message identification. It happens sometimes with IMAP 
+servers changing the "Message-Id" header line or one or more
+of the "Received:" header lines in the header part of messages. 
+By default, Imapsync uses "Message-Id" header line and 
+"Received:" header lines to identify messages on both sides.
+
+R1. This solution is R3 simplified.
+A quick practical solution is to change the way imapsync
+identify messages that works most of the time. But since
+you're reading this because you encountered duplicates issue,
+let's check this solution in a safe way.
+
+First use the same commmand with additionnal options:
+
+     imapsync ... --useheader "Message-Id" --dry 
+
+The previous command does nothing real but it will show you
+if imapsync handles duplicates in a better way.
+The criterium is to search at the end of the sync for a line
+like this one:
+Messages skipped                  : 1555
+where 1555 is an example but reflects mostly the number
+of all messages already transferred.
+
+If you end with: 
+Messages skipped                  : 0
+don't go on, it means imapsync is still suffering to
+identify messages.
+
+If you end with many messages skipped then it's very
+good and now you can safely resync the mailbox
+and get rid of the dupplicates messages on host2 with:
+
+    imapsync ... --useheader "Message-Id" --delete2duplicates
+
+End of the problem!
+
+R2. 
+A second solution is to use option --useuid. 
+With option --useuid, imapsync  doesn't use header lines 
+to identify and compare messages in folders.
+Instead of some headers,  --useuid tell imapsync to use 
+the imap UIDs given by imap servers on both sides.
+To avoid duplicates on next runs, imapsync uses a local cache
+where it keeps UIDs already transferred. 
+
+  imapsync ... --useuid
+
+There is an issue when --useuid is not used the first time.
+A big issue with --useuid is that it doesn't generate duplicates if 
+used from the first time but it does generate duplicates after a previous
+run without --useuid (because it then uses a different method to identify 
+the messages). 
+
+A solution? Two solutions.
+
+The easiest is --delete2 if you are permitted to use it. 
+Option --delete2 removes messages on host2
+that are not on host1. So, with --delete2 you go for resyncing all 
+messages again. All previously transferred messages are deleted,
+but also messages previously there without imapsync.
+So --useuid --delete2 is an easy way to remove duplicates but it
+is not suitable in all contexts. The good context is that the host2 
+account must be considered as a strict replication of the host1 
+account, ie, host2 not active yet.
+
+A second solution, better if R3 works (see R3 below), is to build
+the cache before using --useuid
+
+First sync:
+
+  imapsync ... --useheader "Message-Id" --addheader --usecache
+
+Next syncs:
+
+  imapsync ... --useuid
+  imapsync ... --useuid
+  ...
+
+R3. 
+Best way if you can follow it. 
+Multiple copies of the emails on the destination server. Some IMAP
+servers (Domino for example) change some headers for each message
+transferred. All messages are transferred again and again each time you
+run imapsync. This is bad of course. The explanation is that imapsync
+considers messages are not the same on each side, default headers used
+to identify the messages have changed.
+
+You can look at the headers found by imapsync by using the --debug
+option (and search for the message on both part), Header lines from
+the source server begin with a "FH:" prefix, Header lines from the
+destination server begin with a "TH:" prefix. Since --debug is very
+verbose I suggest to isolate a email in a specific folder in case you
+want to forward me the output.
+
+A way to avoid this problem is by using option --useheader with
+a different set than the default ones used by imapsync.
+
+The default set is equivalent to:
+
+  imapsync ... --useheader "Message-Id" --useheader "Received"
+
+The problem now is that what can be used instead of Message-Id
+and Received lines? Often standalone Message-Id works:
+
+  imapsync ... --useheader "Message-Id"
+
+Once imapsync does not generate duplicates, the previous duplicates
+can be deleted with option --delete2duplicates
+
+  imapsync ... --useheader "Message-Id" --delete2duplicates
+
+Another good way toward a solution is to isolate two or three messages
+in a BUG folder and send me the --debug output by email to
+gilles@lamiral.info
+
+  imapsync ... --debug  --folder BUG
+
+I will take a close look at the log and modify imapsync to fix
+this faulty duplicate behavior.
+
+Remark. (Trick found by Tomasz Kaczmarski)
+
+Option --useheader "Message-Id" asks the server to send only header
+lines beginning with "Message-Id".  Some (buggy) servers send the whole
+header (all lines) instead of the "Message-Id" line. In that case, a
+trick to keep the --useheader filtering behavior is to use
+--skipheader with a negative lookahead pattern:
+
+  imapsync ... --skipheader "^(?!Message-Id)"
+
+ Read it as "skip every header except Message-Id".
+
+=======================================================================
+Q. imapsync calculates 479 messages in a folder but only transfers 400 
+   messages. What's happen?
+
+R1. Unless --useuid is used, imapsync considers a header part 
+   of a message to identify a message on both sides.
+   By default the header part used is lines "Message-Id:" "Message-ID:" 
+   and "Received:" or specific lines depending on --useheader 
+   --skipheader. Whole header can be set by --useheader ALL
+
+Consequences:
+
+  1) Duplicate messages on host1 (identical header) are not transferred.
+
+The result is that you can have more messages on host1 than on host2.
+
+R2. With option --useuid imapsync doesn't use headers to identify
+    messages on both sides but it uses their imap uid identifier.
+    In that case duplicates on host1 are also transferred on host2.
+
+=======================================================================
+Q. How can I remove duplicates in a lone account?
+
+R. In order to remove duplicates in a lone account, just run imapsync 
+   on the same account as source and destination, plus the 
+   option --delete2duplicates, ie, with 
+   host1 == host2, user1 == user2, password1 == password2
+   
+
+=======================================================================
+=======================================================================

FAQ.d/FAQ.Emptying.txt

@@ -0,0 +1,40 @@
+#!/bin/cat
+$Id: FAQ.Emptying.txt,v 1.8 2019/04/30 12:52:10 gilles Exp gilles $
+
+This documentation is also available online at
+https://imapsync.lamiral.info/FAQ.d/
+
+https://imapsync.lamiral.info/FAQ.d/FAQ.Emptying.txt
+
+=======================================================================
+               Imapsync tip to empty an account.
+=======================================================================
+
+=======================================================================
+Q. How to delete all emails of all folders of an account with imapsync?
+
+R. Use the same account on both sides with option --delete1
+   --noexpungeaftereach
+
+Option --noexpungeaftereach is just to speed up the deletions.
+
+Example (real example):
+
+  ./imapsync \
+    --host1 test.lamiral.info --user1 empty --password1 secret \
+    --host2 test.lamiral.info --user2 empty --password2 secret \
+    --delete1 --noexpungeaftereach
+
+=======================================================================
+Q. How to delete all folders of an account with imapsync?
+
+R. Use the same account on both sides with the options 
+    --delete1 --noexpungeaftereach --delete1emptyfolders
+    
+  ./imapsync ... --delete1 --noexpungeaftereach --delete1emptyfolders
+
+It won't delete the folder INBOX since INBOX is mandatory in imap.
+
+
+=======================================================================
+=======================================================================

FAQ.d/FAQ.Exchange.txt

@@ -0,0 +1,755 @@
+
+$Id: FAQ.Exchange.txt,v 1.57 2019/12/04 18:26:28 gilles Exp gilles $
+
+This documentation is also available online at
+https://imapsync.lamiral.info/FAQ.d/
+https://imapsync.lamiral.info/FAQ.d/FAQ.Exchange.txt
+
+
+=======================================================================
+            Imapsync tips for Exchange 20xx and Office365.
+=======================================================================
+
+Questions answered in this FAQ are:
+
+Q. Can I use imapsync to transfer from or to Exchange or Office365 accounts?
+
+Q. How to sync from XXX to Exchange 2010/2013/2016
+
+Q. How to sync from Office365 to XXX?
+
+Q. How to sync from XXX to Office365
+
+Q. For Office365 I have double and triple checked the username and 
+   password spelling but I still get a "LOGIN failed". Any clue?
+
+Q. I see "NO Maximum size of appendable message has been exceeded"
+   What can I do with that? Happens with Office365 or Exchange 2016.
+
+Q. Office365 throttles the sync and says: 
+   "Request is throttled. Suggested Backoff Time: 299961 milliseconds".
+   What can I do with that?
+
+Q. Office365 refuses to create the folder named "Files" with the error
+   "NO Folder name is reserved". What happens?
+
+Q. Office365 users complain that a folder named "Files" contains 
+   messages with no sender.
+
+Q. Exchange fails with "User is authenticated but not connected".
+
+Q. Exchange fails with "BAD Command received in Invalid state".
+
+Q. From XXX to Exchange 2013 or Office365, read receipts are all
+   resent again after a sync. Even for old messages. How can I fix that?
+
+Q. DEBUG: IO/Socket/SSL.pm:1043: local error: SSL read error
+   DEBUG: IO/Socket/SSL.pm:1043: local error: SSL read error   
+
+Q. From XXX to Exchange 2010/2013 or Office365 I get this error message
+   sometimes: "BAD Command Argument Error 11". What does it mean?
+
+Q. From XXX to Exchange 2010 or 2013 or Office365 the flag Flagged does 
+   not seem to be well synced. What can I do?
+
+Q. How to migrate from or to Exchange 2007/2010/2013 with an 
+   admin/authuser account?
+
+Q. How to migrate from or to Exchange 2016 with an admin/authuser account?
+
+Q. How to migrate from or to Office 365 with an admin/authuser account?
+
+Q. How to migrate from or to Exchange 2003 with an admin/authuser 
+   account?
+
+Q. Couldn't create folder [trash] "Mailbox already exists".
+
+Q. Migrating to Exchange 201O, messages get date of the transfer,
+   this is bad for sorting and listing. What can I do?
+
+Q. How to sync from any to Exchange 2007?
+
+Q. Exchange 2007 folders ending with a space cause an imapsync crash.
+   "Could not select: socket closed while reading data from server"
+
+Q. How to sync from Microsoft Exchange 2000 IMAP4rev1 server?
+
+
+Now the questions again with their answers.
+
+=======================================================================
+Q. Can I use imapsync to transfer from or to Exchange or Office365 accounts?
+
+R. Yes. But IMAP access to a Exchange or Office365 account is not always 
+   allowed by default so it has to be allowed in the server configuration 
+   part.
+
+   Exchange:  https://docs.microsoft.com/en-us/exchange/enable-imap4-in-exchange-2013-exchange-2013-help
+   Office365: https://docs.microsoft.com/en-us/exchange/troubleshoot/configure-mailboxes/pop3-imap-owa-activesync-office-365
+
+=======================================================================
+Q. How to sync from XXX to Exchange 2010/2013/2016
+
+R0. IMAP is not enable by default on Exchange, see how to enable it:
+https://docs.microsoft.com/en-us/exchange/enable-imap4-in-exchange-2013-exchange-2013-help
+
+
+R1. Following is a command line resume that solves most encountered 
+    issues when migrating to Exchange. To fully understand or change 
+    the details you have to read the next Q/R sections.
+
+
+On Windows, use:
+
+  imapsync.exe ... --exchange2
+
+which is equivalent in imapsync release 1.970 to:
+
+  imapsync.exe ... ^
+    --maxsize 10_000_000 ^
+    --maxmessagespersecond 4 ^
+    --disarmreadreceipts ^
+    --regexflag "s/\\Flagged//g" ^
+    --regexmess "s,(.{10239}),$1\r\n,g"
+
+On Unix, use:
+
+  imapsync ... --exchange2
+
+which is equivalent in imapsync release 1.970 to:
+
+  imapsync ... \
+    --maxsize 10_000_000 \
+    --maxmessagespersecond 4 \
+    --maxlinelength 10239 \
+    --regexflag 's/\\Flagged//g' \
+    --disarmreadreceipts \
+    --regexmess 's,(.{10239}),$1\r\n,g'
+
+
+
+On Linux, you can also try the "reformime" command 
+that can be used like:
+
+  imapsync ... --maxlinelengthcmd "reformime -r7"
+
+To get reformime, install the "maildrop" package.
+
+=======================================================================
+Q. How to sync from Office365 to XXX?
+
+R. On Windows, use:
+
+  imapsync.exe ... --office1
+
+On Unix, use:
+
+  imapsync ... --office1
+
+Option --office1 is like (release 1.970):
+  
+  imapsync ... --host1 outlook.office365.com \
+               --ssl1 \
+               --exclude "^Files$" 
+  
+=======================================================================
+Q. How to sync from XXX to Office365
+
+R0. IMAP is not enable by default on Office365, see how to enable it:
+https://docs.microsoft.com/en-us/exchange/troubleshoot/configure-mailboxes/pop3-imap-owa-activesync-office-365
+https://docs.microsoft.com/en-us/exchange/allow-pop3-imap4-and-smtp-server-settings-to-be-viewed-by-end-users-in-outlook-web-app-exchange-2013-help
+https://support.context.io/hc/en-us/articles/213586243-Enabling-IMAP-for-Office365
+
+R. Here is a command line resume that solves most encountered issues when 
+   migrating to Office365. It's similar with Exchange except for some 
+   values. To understand or change the details you have to read 
+   next Q/R sections.
+
+
+  imapsync ... --office2
+
+which is equivalent to (in imapsync release 1.870):
+
+  imapsync ... \
+    --host2 outlook.office365.com \
+    --ssl2 \
+    --maxsize 45000000 \
+    --maxmessagespersecond 4 \
+    --disarmreadreceipts \
+    --regexmess "s,(.{10239}),$1\r\n,g" \
+    --f1f2 "Files=Files_renamed_by_imapsync"
+
+
+On Linux, you can also try the "reformime" command 
+that can be used like:
+
+  imapsync ... --maxlinelengthcmd "reformime -r7"
+
+To get reformime, install the "maildrop" package.
+
+
+=======================================================================
+Q. For Office365 I have double and triple checked the username and 
+   password spelling but I still get a "LOGIN failed". Any clue?
+
+R1. Triple check the hostname then. Try all of these:
+ * imap-mail.outlook.com
+ * imap.outlook.com
+ * outlook.office365.com
+
+R2. Also triple check a license is assigned to that account 
+    in Office365.
+
+R3. Try with a classic email client like Thunderbird and the same
+    parameters.   
+
+=======================================================================
+Q. Exchange fails with "User is authenticated but not connected".
+
+R1. "The message User is authenticated but not connected is due to a 
+   bug in the Exchange server's IMAP implementation. If the client 
+   presents a valid user name but an invalid password, the server 
+   accepts the login, but subsequent commands fail with the 
+   aforementioned error message." Source:
+https://unix.stackexchange.com/questions/164823/user-is-authenticated-but-not-connected-after-changing-my-exchange-password
+Thanks to James Abbottsmith for this link and explanation at
+https://github.com/imapsync/imapsync/issues/32#issuecomment-153561647
+
+R2. Miguel Alameda reported understanding and solving this issue 
+    like this, the context was admin/authuser:
+    "The admin user had not permission in the target mailbox."
+
+=======================================================================
+Q. I see "NO Maximum size of appendable message has been exceeded"
+   What can I do with that? Happens with Office365 or Exchange 2016
+
+R0. It happens with Office365 and Exchange 2016.
+    See R1 for Office365
+    See R2 for Exchange 2016
+
+R1. Office365 supports send/receive max message sizes of up to 150MB 
+   but you need to make changes in your tenant(s) to support it.
+
+The following PowerShell command will increase the message sizes that 
+can be sent/received.  The trick in getting IMAPSync to work is to 
+apply these settings to the accounts performing the migration,
+NOT the accounts associated with the target mailbox (assuming you're
+using service accounts to perform transfers on behalf of users).
+
+  Set-mailbox -Identity $UPN -MaxReceiveSize 150mb -MaxSendSize 150mb
+
+e.g. 
+
+  Set-mailbox -Identity "migrationaccount@testtenant.onmicrosoft.com" -MaxReceiveSize 150mb -MaxSendSize 150mb
+
+We're transferring data between Office 365 tenants so we set these 
+values on the migration acounts in the source and target tenants.
+
+Thanks to Sean McDougall, Ian Thomas & Matt Wilks from Toronto 
+for this FAQ item.
+
+R2. With Exchange 2016
+
+Thanks to Torsten Bergemann from Germany:
+
+In order to have exchange accept big e-mails via imap, several size 
+limitations have to be removed on several levels of the exchange 
+software: For the organization (within exchange admin panel), 
+for each connector (with exchange admin panel), for each Postfach 
+(using exchange management shell).
+
+For details and instructions, check 
+https://docs.microsoft.com/en-us/Exchange/mail-flow/message-size-limits?view=exchserver-2019
+https://docs.microsoft.com/en-us/Exchange/architecture/client-access/client-message-size-limits?view=exchserver-2019
+
+Unfortunately, the second link does not give instructions to remove the limit from imap4 service.
+
+To solve it for Exchange 2013/2016, add the line
+
+<add key="MaxReceiveSize" value="1024000000" />
+
+to the file 
+C:\Program Files\Microsoft\Exchange Server\V14 [or V15]\ClientAccess\PopImap\Microsoft.Exchange.Imap4.exe.config
+
+Please note that this change may be lost each time you install an 
+cumulative update. After the change, restart the services exchange 
+transport role, exchange information store and exchange imap4 Backend.
+
+(Source: https://social.technet.microsoft.com/Forums/de-DE/2c07cf43-fe0e-4d22-b061-676a67c6d58d/exchange-2013-max-mailgre-per-imap?forum=exchange_serverde)
+
+This change made our Exchange installation accept bigger e-mails 
+in order to remove the imapsync Exchange error message
+"NO Maximum size of appendable message has been exceeded"
+
+
+=======================================================================
+Q. Office365 throttles the sync and says: 
+   "Request is throttled. Suggested Backoff Time: 299961 milliseconds".
+   What can I do with that?
+   
+
+R. Exchange and Office365 have throttle mechanisms to limit any huge 
+   usage. Sometimes imapsync transfers are too stressful for servers.
+   The message 
+   "Request is throttled. Suggested Backoff Time: 299961 milliseconds"
+   comes from the imap Office365 server, imapsync just reports it
+   before being disconnected from it.
+
+   To solve the throttles issues from 0365, there are two solutions
+   at least:
+
+R1. Call Microsoft Office365 and ask them to remove the limits on your 
+  mailboxes. That's not a joke, they do it for 90 days usually, 
+  sometimes only after you reach the second technician you call, 
+  the first one usually been not enough competent to understand 
+  what you're talking about (I would be glad to remove this bad
+  fact).
+
+R2. Play with options --maxbytespersecond or --maxmessagespersecond
+    or --exitwhenover
+
+  imapsync ... --maxbytespersecond 100_000
+
+  imapsync ... --maxmessagespersecond 2
+
+  imapsync ... --exitwhenover 1_000_000_000
+
+I don't know the upper value that avoid the default throttling from 0365
+and I guess it changes over time.
+
+R3. For Exchange, in case throttle appears anyway, fix them with:
+  https://docs.microsoft.com/en-us/exchange/change-user-throttling-settings-for-specific-users-exchange-2013-help
+  See also:
+  http://www.linux-france.org/prj/imapsync_list/msg02072.html
+
+  Sometimes restarting the Exchange server is needed to take
+  into account the change in the configuration.
+
+=======================================================================
+Q. Office365 refuses to create the folder named "Files" with the error
+   "NO Folder name is reserved". What happens?
+
+R. The folder Files is a standard folder in Office365. It should not
+   be synced in IMAP. See the next question.
+
+=======================================================================
+Q. Office365 users complain that a folder named "Files" contains 
+   messages with no sender.
+
+R0. To fix this, add --exclude Files
+
+  imapsync ... --exclude Files
+
+  If you use --office1 then imapsync will add this exclusion 
+  automatically like using  the option:
+  
+  imapsync ... --exclude "^Files$" 
+
+  If you use --office2 then imapsync will add a renaming of any
+  "Files" folder on host1, like using the option:
+  
+  imapsync ... --f1f2 "Files=Files_renamed_by_imapsync"
+
+  The host2 account ends up with a folder named 
+  "Files_renamed_by_imapsync", but no complaining.
+
+R1. This folder "Files" seems to be a standard folder in Exchange Online, 
+   but it is not. The folder contains all attachments in every email 
+   that is in the mailbox, but without any headers.
+   This causes some confusion for users as these appear in their 
+   search results as duplicate lines but without the sender details 
+   or even the message body.
+
+   This folder seems to be usually hidden so IMAP clients can’t see it, 
+   but for some reason sometimes it becomes visible.
+
+R2. It looks to be a common problem with Exchange Online. 
+    I’m not sure what causes the folder to appear.
+
+   More info here:
+https://answers.microsoft.com/en-us/msoffice/forum/msoffice_o365admin-mso_exchon-mso_o365b/exclude-the-exchange-online-system-folder-called/2adbdf84-db4a-4c7f-ac29-738757980a0d
+https://answers.microsoft.com/en-us/msoffice/forum/msoffice_o365admin-mso_dep365-mso_o365b/no-sender-emails-in-files-folder/534bae8f-a7d7-4f5f-8ed7-5bad0d5fa23f
+
+  (This question/answer is taken quasi verbatim from Perttu Aaltonen)
+=======================================================================
+Q. Exchange fails with "BAD Command received in Invalid state".
+
+R1. This message might happen when authenticating without ssl nor tls,
+   wich is rare now since imapsync tries to do ssl then tls by default.
+   Add --tls1 or else --ssl1 if this error message comes from host1.
+   Add --tls2 or else --ssl2 if this error message comes from host2.
+
+R2. This message might also happen when authenticating with ssl and tls.
+   Don't use --tlsX and --sslX on the same side X (1 or 2), since it 
+   asks for a double encryption, an encryption inside an encryption.
+   It won't work, you can't do a direct double encryption, few 
+   servers allow that.
+
+=======================================================================
+Q. From XXX to Exchange 2013 or Office365, read receipts are all
+   resent again after a sync. Even for old messages. How can I fix that?
+
+R. imapsync can remove the header containing this read receipt request.
+
+On Unix or Windows use:
+
+  imapsync ... --disarmreadreceipts
+
+Since read receipts should be sent for unseen messages that will go 
+to a seen state after the migration, you could be strict and apply 
+the regex only to seen messages. 
+Selecting seen message can be done with:
+
+  imapsync ... --search1 "SEEN" --disarmreadreceipts
+
+Of course a second run has to be run without the --disarmreadreceipts
+for unseen messages:
+
+  imapsync ... --search1 "UNSEEN" 
+
+If fact --disarmreadreceipts is just an option equivalent to:
+
+  --regexmess 's{\A(.*?(?! ^$))^Disposition-Notification-To:(.*?)$}{$1X-Disposition-Notification-To:$2}igxms' 
+
+That regex changes the header Disposition-Notification-To. It prefixes
+it with an X- so that it becomes inactive.
+Disposition-Notification-To: blabla
+becomes
+X-Disposition-Notification-To: blabla
+
+Thanks to David Karnowski for pointing and solving this issue.
+
+=======================================================================
+Q. DEBUG: IO/Socket/SSL.pm:1043: local error: SSL read error
+   DEBUG: IO/Socket/SSL.pm:1043: local error: SSL read error   
+
+R1. "SSL read or write error" happens sometimes, it isn't related to 
+    imapsync directly but to the ssl underlying library when communicating
+    with Exchange in TLS/SSL encrypted mode. 
+    Next runs should put the sync further, so rerun the syncs 
+    until it is well completed.
+
+R2. Another solution is to remove --tls or --ssl options for Exchange
+    and accept a clear text sync.
+
+R3. See also the FAQ FAQ.SSL_errors.txt
+    https://imapsync.lamiral.info/FAQ.d/FAQ.SSL_errors.txt
+
+=======================================================================
+Q. From XXX to Exchange 2010/2013 or Office365 I get this error message
+   sometimes: "BAD Command Argument Error 11". What does it mean?
+
+R. This error message comes from Exchange IMAP server when it 
+   encounters any problem. Most of the time it is one of the following:
+
+  * Some messages are bigger than the size limit. 10 MB by default
+    on Exchange. It can be upped by configuration for Exchange.
+	Sometimes a reboot is needed to take configuration changes 
+	into account.
+    If you can't fix this limit on Exchange then use option
+    --maxsize 10000000 for 10 MB, change it if needed) to tell
+    imapsync to skip those messages.
+    This value is 45 MB by default for Office365
+
+  imapsync ... --maxsize 10000000 # 10 MB for Exchange
+
+  imapsync ... --maxsize 45000000 # 45 MB for Office365
+  
+
+  * Quota reached. The whole account is full.
+    It can be upped by configuration.
+
+  * Some messages have some lines too long. Use option --maxlinelength
+    to skip messages whose max line length is over a number of bytes.
+    --maxlinelength 1000 is a RFC2822 must but most server support
+    higher values. 
+    Exchange supports 9900 characters line length:
+
+  imapsync ... --maxlinelength 9900 
+
+    Office365 supports 10500 characters line length:
+
+  imapsync ... --maxlinelength 10500
+
+  In case you prefer fixing messages with long lines the hard way,
+  instead of skipping them with --maxlinelength 9900, just use:
+
+  On Windows
+  imapsync ... --regexmess "s,(.{9900}),$1\r\n,g"
+
+  On Unix
+  imapsync ... --regexmess 's,(.{9900}),$1\r\n,g'
+  
+Have also in mind that Exchange closes the connection after 10 errors
+encountered so you might also see "BYE Connection closed" errors from
+Exchange, which means Exchange leaves the session and say goodbye,
+come back later. Rerun a sync then.
+
+On Linux, there is a good Python script in the tarball that can 
+fix several things that Exchange or O365 have issues with.
+
+Use it like this:
+
+  ./imapsync ... --pipemess W/tools/fix_email_for_exchange.py
+
+It often does some miracles on messages.
+
+=======================================================================
+Q. From XXX to Exchange 2010 or 2013 or Office365 the flag Flagged does 
+   not seem to be well synced. What can I do?
+
+R. Use the following trick. Run imapsync twice, one with --regexflag
+   and one without, like this:
+
+1) imapsync ... --regexflag "s/\\Flagged//g"
+2) imapsync ...
+
+You can add --debugflags if you want to see what imapsync gets and 
+does in details with flags.
+
+The magic of this trick is on ignoring the \Flagged flag on the first 
+sync and setting it on the second sync, with STORE instead of APPEND.
+This Exchange bug seems that Exchange gets and sets well the Flagged 
+flag with APPEND in IMAP but then it forgets it with other protocols;
+With STORE it sets and gets the "\Flagged" flag everywhere.
+
+Thanks to Dave Murray and Simon Savva for reporting and solving 
+this issue.
+
+======================================================================
+Q. How to migrate from or to Exchange 2007/2010/2013 with an 
+   admin/authuser account?
+   
+R. The tricks comes from Michele Marcionelli and Benjamin Priestman:
+
+This doesn't work:
+  imapsync ... --user2 user2 --authuser2 admin2 --password2 adminpassword2 ...
+
+This might works:
+  imapsync ... --user2 "domain\admin2\user2" --password2 adminpassword2 ...
+or 
+  imapsync ... --user2 "admin2@domain\user2" --password2 adminpassword2 ...
+
+where "domain" is set be the user's UPN in Active Directory
+or the NETBIOS or DNS name of the domain.
+
+The exact format might vary depending on local configuration and you
+should experiment with the different formats.
+
+PLAIN authentication is the only way to go with --authuser1 for now.
+So don't use --authmech1 SOMETHING with --authuser1 admin_user,
+it will not work.
+Same behavior with the --authuser2 option.
+
+A little note from Michael Scherer. 
+The previous workaround in the FAQ seems to be obsolete.
+I can confirm that
+
+  imapsync ... --host2 exchange_server \
+               --authuser2 admin@domain --user2 user_alias
+
+is working without any glitches, running Exchange 2010 SP2 here.
+Explanation, Exchange knows a) about a username 
+and b) about a mailNickname which can be different to the username. 
+As it seems you need to use the mailNickname (e.g. alias) defined 
+for user2, not the username itself.
+https://techcommunity.microsoft.com/t5/exchange-team-blog/understanding-login-strings-with-pop3-imap/ba-p/610683
+
+A little note from John Becker.
+After you pointed out that I had issues with authorization, I realized that
+as an admin user I don't have all the rights on the mailboxes.
+So I added myself to the user mailbox with full rights.
+I also changed the login type on the Exchange CAS to type 1, plain text.
+The command that I used for imapsync is:
+   imapsync ... ^
+       --host2 exchange-server ^
+       --user2 "windows-domain\admin-user\aaaa" ^
+       --password2 admin-password ...
+
+
+
+======================================================================
+Q. How to migrate from or to Exchange 2016 with an admin/authuser account?
+
+R. This might work:
+
+  imapsync ... --user2 user2 --authuser2 admin2 --password2 adminpassword2 ...
+
+Note from
+https://github.com/imapsync/imapsync/issues/136#issuecomment-397020248
+
+The key is to not use the built-in Administrator account which 
+Microsoft seems to have blocked access to in imap. 
+I'm doing a sync to Exchange 2016 accounts and this works:
+
+  imapsync ... --ssl2 --user2 account@domain.com ^
+               --authuser2 accountwfullaccess@domain.com ^
+               --password2 "accountwfullaccesspw"
+
+The admin account you use needs to have full access to the account(s) 
+you want to sync which you can setup in the gui or via powershell 
+and again - don't use administrator@domain.com - as that will never 
+work because IMAP LOGIN is disabled for that account apparently
+under all circumstances.
+
+Note from Noxyron
+https://github.com/imapsync/imapsync/issues/136#issuecomment-543761463
+
+Hi guys. For a long time I could not start synchronization, I use admin rights 
+and the --authuser2 switch when I migrated from Mdaemon to Exchange2016. 
+I always got the error:
+"Host2 failure: Error login on [my.exchange.com] with user [mydomainuser] auth [PLAIN]: 2 NO AUTHENTICATE failed."
+In order for ImapSync to login to the user’s mailbox using administrator rights,
+you need to give for the administrator the permissions to the mailbox of this
+user with the command:
+“Add-MailboxPermission -Identity DomainUser -User DomainAdmin -AccessRights FullAccess -InheritanceType All -AutoMapping $false”
+using Exchange Management Shell. 
+Without this, synchronization will not work. 
+Please, add this comment to the FAQ.Exchange.txt
+(done!)
+
+======================================================================
+Q. How to migrate from or to Office 365 with an admin/authuser account?
+
+Note from Yago Torres Fernandez:
+(a working command using admin/authuser on host2 Office 365)
+
+  imapsync ... --authuser2 user_admin@domain.com --user2 user_to_be_migrated@domain.com  ^
+               --password2 XXXX --ssl2  ^
+
+but previously in Office365 you must do something like that, using powershell:
+
+  Add-MailboxPermission -identity user_to_be_migrated@domain.com -user user_admin@domain.com -accessrights fullaccess -inheritancetype all
+
+PLAIN authentication is the only way to go with --authuser1 for now.
+So don't use --authmech1 SOMETHING with --authuser1 admin_user,
+it will not work.
+Same behavior with the --authuser2 option.
+
+Note from Martin Paulucci:
+I had to remove the domain part for the user
+but not for the admin.  Example:
+
+  imapsync ... --authuser2 user_admin@domain.com --user2 user_to_be_migrated
+
+See also:
+http://www.linux-france.org/prj/imapsync_list/msg02203.html
+
+======================================================================
+Q. How to migrate from or to Exchange 2003 with an admin/authuser 
+   account?
+
+R. Thomas Edgar wrote the following
+
+In case you can glean something from this snippet which allowed us 
+to migrate from Exchange 2003 t0 Cyrus Imap 2.4 (you would reverse 
+the flow to go the other way):
+
+  imapsync --dry --host1 ExchangeServer.mycompany.com \
+    --user1 Some.User@mycompany.com --authuser1 ExchangeAdminAccount \
+    --proxyauth1 --password1 '$pass_with_dollars$' \
+    --host2 cyrusimapbackend.mycompany.com \
+    --user2 SameOrDiffererentUser@mycompany.com \
+    --authuser2 CyrusAdminAccount --password2 CyrusAdminPassword
+
+We also needed to:
+
+- Ensure the Exchange Admin Acct had IMAP4 enabled in it's 
+  profile (it initially didn't!)
+- Ensure the Some.User Exchange Acct had IMAP4 enabled 
+  in it's profile (it initially didn't!)
+- Add the CyrusAdminAccount to admins line in /etc/imapd.conf
+- Give CyrusAdminAccount lrswipkxtecda to the Cyrus Imap account 
+  being migrated to (- or in your case, from)
+
+In case you are not aware:
+
+- It will prompt for a password if you don't supply it
+- the domain part of the fully-qualified email could be 
+  omitted in our case
+- Use --debugimap when testing initial connectivity, if necessary
+
+=======================================================================
+Q. Couldn't create folder [trash] "Mailbox already exists".
+
+R. Some servers take care about character case in folder names, 
+   some servers do not, like Exchange. Since non-respecting case 
+   can merge two different folders into one then imapsync respects case. 
+
+   For example, if a host1 server has a folder name called "trash"
+   and the host2 server already has a folder "Trash" or "TRASH"
+   then imapsync will try to create the folder "trash" on host2,
+   because trash and Trash are different strings. But if host2
+   does not respect character case it will consider folder "trash"
+   already exists and will say it, that's the error message 
+   reported by imapsync: "Mailbox already exists", message coming 
+   from the server.
+
+   The folder creation fails but messages are well transferred in
+   so take a look at this warning, understand why it happens
+   and it should be fine most of the time.
+
+   To avoid this warning use --regextrans2 to map the folder names
+
+   imapsync ...  --regextrans2 "s/^trash$/Trash/"
+
+   If there are two folders Trash and trash on host1 then both
+   will be merge into only one Trash folder on host2. 
+   In case option --delete2 is used the regextans2 above becomes
+   mandatory, otherwise imapsync will sync messages from the
+   first Trash and then delete them when syncing trash.
+
+   In order to avoid merging folders that are considered different 
+   on host1 but the same on destination host2 because of case 
+   sensitivities and insensitivities, use  --nomixfolders
+
+======================================================================
+Q. Migrating to Exchange 201O, messages get date of the transfer,
+   this is bad for sorting and listing. What can I do?
+
+R1. Be sure to have at least Exchange 2010 SP2 Rollup 5
+https://tribalchicken.net/imap-sync-issues-with-exchange-2010/
+
+R2. See also the Outlook side (thanks to Martin Hochreiter for this solution)
+https://www.howto-outlook.com/faq/archivenotworking.htm
+by changing Archive to sent/receive date
+
+It's often shorter to change one server than thousands clients
+so R1 might be easier to do.
+
+======================================================================
+Q. How to sync from any to Exchange 2007?
+
+Several problems:
+- Big messages: increase the "send- and receive-connector" 
+  in exchange2007 to 40 MB.
+
+R. 2 solutions
+
+R1. With imapsync (only partial success)
+--skipheader 'Received' \
+--regexmess 's{\A(.*?(?!^$))^Date:(.*?)$}{$1Date:$2\nReceived: From; $2}gxms'
+Any user having time to spend to debug Exchange 2007 with imapsync
+is welcome.
+
+R2. Other solution
+Two users succeeded by using "MS Transporter Suite" (which is closed
+expensive non-free software).
+
+=======================================================================
+Q. Exchange 2007 folders ending with a space cause an imapsync crash.
+   "Could not select: socket closed while reading data from server"
+
+R. Using another imap tool like Thunderbird or Outlook, change the 
+   folder name to exclude the trailing space.
+
+See  https://github.com/imapsync/imapsync/issues/154
+
+======================================================================
+Q. How to sync from Microsoft Exchange 2000 IMAP4rev1 server?
+
+R. imapsync ...  --prefix1 "INBOX."
+
+
+=======================================================================
+=======================================================================

FAQ.d/FAQ.Flags.txt

@@ -0,0 +1,303 @@
+#!/bin/cat
+$Id: FAQ.Flags.txt,v 1.21 2019/03/08 19:04:32 gilles Exp gilles $
+
+This documentation is also available online at
+https://imapsync.lamiral.info/FAQ.d/
+https://imapsync.lamiral.info/FAQ.d/FAQ.Flags.txt
+
+=======================================================================
+               Imapsync tips about flags.
+=======================================================================
+
+Questions answered here are:
+
+Q. How to debug flag issues?
+
+Q. Is there a way to only sync messages with a specific flag set,
+   for example, the \Seen flag?
+
+Q. How to convert flags?
+
+Q. Exchange sends an email to any sender whose email is deleted 
+   without reading. It's called "unread notifications".
+   How to set the \Seen flag on host1 (source system) before syncing?
+
+Q. Does imapsync retain the \Answered and $Forwarded flags?
+
+Q. How to fix this error: BAD Invalid system flag \FORWARDED
+   
+Q. How to convert flags with $ to \ character?
+
+Q. imapsync fails with the following error:
+flags from : [\Seen NonJunk]
+Error trying to append string: 58 NO APPEND Invalid flag list   
+
+Q. Flags are not well synchronized. Is it a bug?
+
+Q. Flags are resynced at each run for already synced/copied messages, 
+   how can I avoid this feature?
+
+Q. Is it possible to sync labels and stars made by Thunderbird to
+   Exchange categories? Or a way in Outlook to show labels created by
+   Thunderbird?
+
+=======================================================================
+Q. How to debug flag issues?
+
+R. Use --debugflags
+
+  imapsync ... --debugflags
+
+
+=======================================================================
+Q. Is there a way to only sync messages with a specific flag set,
+   for example, the \Seen flag?
+
+R. use --search 
+
+  imapsync ... --search SEEN
+
+or
+
+  imapsync ... --search UNSEEN
+
+or ...
+
+The complete list of search things related to flags are listed below
+
+http://www.faqs.org/rfcs/rfc3501.html
+
+6.4.4.  SEARCH Command
+...
+      ANSWERED
+         Messages with the \Answered flag set.
+
+      DELETED
+         Messages with the \Deleted flag set.
+
+      DRAFT
+         Messages with the \Draft flag set.
+
+      FLAGGED
+         Messages with the \Flagged flag set.
+
+      KEYWORD <flag>
+         Messages with the specified keyword flag set.
+
+      NEW
+         Messages that have the \Recent flag set but not the \Seen flag.
+         This is functionally equivalent to "(RECENT UNSEEN)".
+
+      NOT <search-key>
+         Messages that do not match the specified search key.
+
+      OLD
+         Messages that do not have the \Recent flag set.  This is
+         functionally equivalent to "NOT RECENT" (as opposed to "NOT
+         NEW").
+
+      OR <search-key1> <search-key2>
+         Messages that match either search key.
+
+      RECENT
+         Messages that have the \Recent flag set.
+
+      SEEN
+         Messages that have the \Seen flag set.
+
+      UNANSWERED
+         Messages that do not have the \Answered flag set.
+
+      UNDELETED
+         Messages that do not have the \Deleted flag set.
+
+      UNDRAFT
+         Messages that do not have the \Draft flag set.
+
+      UNFLAGGED
+         Messages that do not have the \Flagged flag set.
+
+      UNKEYWORD <flag>
+         Messages that do not have the specified keyword flag set.
+
+      UNSEEN
+         Messages that do not have the \Seen flag set. 
+
+=======================================================================
+Q. How to convert flags?
+
+R. use --regexflag
+For example to convert flag IMPORTANT to flag CANWAIT
+
+  imapsync ... --regexflag "s/IMPORTANT/CANWAIT/g" --debugflags
+
+option --debugflags is usefull to see in details what imapsync
+does with flags.
+
+
+=======================================================================
+Q. Exchange sends an email to any sender whose email is deleted 
+   without reading. It's called "unread notifications".
+   How to set the \Seen flag on host1 (source system) before syncing?
+
+R. You can add \Seen (if missing) to the host1 account by applying a 
+   first sync to the same account, same at source and destination, 
+   and the help of option --regexflag. It can also be done on the fly
+   from account1 to account2 in case account1 has to stay as it is.
+   
+Add the \Seen flag to all messages like this:
+
+On Winwows:
+
+  imapsync.exe ... --regexflag "s,\\Seen,," --regexflag "s,,\\Seen ,"
+                   
+On Unix:
+
+  imapsync ... --regexflag 's,\\Seen,,' --regexflag 's,,\\Seen ,'
+
+R2. You can also filter with --search1 UNSEEN and use only one
+    of the regexes:
+
+On Unix:
+
+  imapsync ... --search1 UNSEEN --regexflag 's,,\\Seen ,'
+
+On Winwows:
+
+  imapsync.exe ... --search1 UNSEEN  --regexflag "s,,\\Seen ,"
+
+R3. Fix it on the server Exchange:
+Google translate: 
+https://translate.google.com/translate?sl=auto&tl=en&u=https%3A%2F%2Fwww.ci-solution.com%2Fblog%2Fartikel%2Fungelesen-geloescht-verhindern.html
+German original:
+https://www.ci-solution.com/blog/artikel/ungelesen-geloescht-verhindern.html
+(Link from Oliver B.)
+=======================================================================
+Q. Does imapsync retain the \Answered and $Forwarded flags?
+
+R. It depends on the destination server.
+
+a) If the destination server honours the "PERMAENTFLAGS \*" 
+directive (meaning it accepts any flag) or no PERMAENTFLAGS at all 
+then imapsync synchronizes all flags except the \Recent flag
+(RFC 3501 says about \Recent flag "This flag can not be 
+altered by the client.").
+
+b) If the destination server honours the "PERMAENTFLAGS without the 
+special "\*"  then imapsync synchronizes only the flags listed 
+in PERMANENTFLAGS.
+
+Some imap servers have problems with flags not beginning with
+the backslash character \ 
+(see next question to find a solution to this issue)
+
+
+=======================================================================
+Q. How to fix this error: BAD Invalid system flag \FORWARDED
+
+R. Filter flag \FORWARDED with --regexflag like this:
+
+On Windows:
+
+  imapsync.exe ... --regexflag "s/\\FORWARDED//gi" 
+
+On Unix:
+
+  imapsync ... --regexflag 's/\\FORWARDED//gi' 
+
+or
+
+  imapsync ... --regexflag "s/\\\\FORWARDED//gi" 
+
+Other related flags to remove are \Indexed and \ATTACHED
+
+Windows:   imapsync.exe ... --regexflag "s/\\Indexed//gi" 
+Unix:      imapsync ...     --regexflag 's/\\Indexed//gi' 
+
+Windows:   imapsync.exe ... --regexflag "s/\\ATTACHED//gi" 
+Unix:      imapsync ...     --regexflag 's/\\ATTACHED//gi' 
+
+All usually problematic flags in one line:
+
+Windows:   imapsync.exe ... --regexflag "s/\\FORWARDED|\\Indexed|\\ATTACHED//gi" 
+Unix:      imapsync ...     --regexflag 's/\\FORWARDED|\\Indexed|\\ATTACHED//gi' 
+
+
+=======================================================================
+Q. How to convert flags with $ to \ character?
+
+R. $ and \ are special characters we have to "escape" them.
+For example to convert flag $label1 to \label1
+
+  imapsync ... --regexflag "s/\$label1/\\label1/g" --debugflags
+
+
+======================================================================
+Q. imapsync fails with the following error:
+flags from : [\Seen NonJunk]
+Error trying to append string: 58 NO APPEND Invalid flag list
+
+R. For some servers, flags have to begin with a \ character.
+The flag "NonJunk" may be a invalid flag for your server 
+so use for example:
+
+imapsync ...    --regexflag "s/NonJunk//g"
+
+Remark (thanks to Arnt Gulbrandsen): 
+IMAP system flags have to begin with \ character.
+Any other flag must begin with another character.
+System flags are just flags defined by an RFC instead of by users.
+Conclusion, some imap server coders don't read the RFCs (so do I).
+
+Recent imapsync deals with this issue by filter with PERMANENTFLAGS
+automatically.
+
+=======================================================================
+Q. Flags are not well synchronized. Is it a bug?
+
+R. It happens with some servers on the first sync. 
+Also, it was a bug from revision 1.200 to revision 1.207
+
+Two solutions: 
+
+* Run imapsync a second time. imapsync synchronizes flags on each run.
+
+* Use option --syncflagsaftercopy. With this option imapsync will 
+  also sync flags after each message transfer. Flags are already 
+  synced during the transfer with the imap APPEND command but 
+  option --syncflagsaftercopy does it again using the imap STORE 
+  command.
+
+=======================================================================
+Q. Flags are resynced at each run for already synced/copied messages, 
+   how can I avoid this feature?
+
+R. Use the option --noresyncflags
+
+
+=======================================================================
+Q. Is it possible to sync labels and stars made by Thunderbird to
+   Exchange categories? Or a way in Outlook to show labels created by
+   Thunderbird?
+
+R. Imapsync syncs all flags possible by default, so if it doesn't do 
+that it might means there are not on the server but stay only on the 
+client or that the host2 server claims to accept only a given set 
+of flags.
+
+Check those claims by accessing the same mailbox on the same server 
+from another thunderbird on another host, you should not retrieve
+those labels. If you do find them it then might mean that host2 
+server don't want them, try --nofilterflags
+
+  imapsync ... --nofilterflags
+
+You can try --nofilterflags straightaway without the 
+"other thunderbird" proposal.
+
+There is also the possibility to map flags across servers 
+with --regexflags
+
+
+=======================================================================
+=======================================================================

FAQ.d/FAQ.Folders_Mapping.txt

@@ -0,0 +1,281 @@
+#!/bin/cat
+$Id: FAQ.Folders_Mapping.txt,v 1.20 2019/07/27 20:04:57 gilles Exp gilles $
+
+This documentation is also available online at
+https://imapsync.lamiral.info/FAQ.d/
+https://imapsync.lamiral.info/FAQ.d/FAQ.Folders_Mapping.txt
+
+
+
+=======================================================================
+             Imapsync tips about changing folders names.
+=======================================================================
+
+By default, imapsync syncs all folders, one by one, in alphanumeric order.
+
+By default, folders names from host1 are reproduced identical on host2,
+except for the prefix and the separator which are automatically adapted
+for host2.
+
+The IMAP protocol has a specific way to code folders names,
+especially when these names use non-ascii 7bit characters.
+This encoding is called utf7imap. 
+
+Imapsync uses the same encoding as IMAP: utf7imap.
+
+In order to well specify folders names on the command line, imapsync
+prints the complete folder list of both sides at the beginning of each run.
+
+The left column is the encoding you have to use, without the first enclosing 
+square brackets [], the right column is the human utf8 view.
+
+This document gives most examples with the powerful but complex
+option --regextrans2. Before using --regextrans2 you should 
+consider using --automap and --f1f2 because they are simpler 
+to understand and use.
+
+ --automap           : guesses folders mapping, for folders like
+                       "Sent", "Junk", "Drafts", "All", "Archive", "Flagged".
+
+ --f1f2    str1=str2 : Force folder str1 to be synced to str2,
+                       --f1f2 overrides --automap and --regextrans2.
+
+ --subfolder2   str  : Syncs the whole host1 folders hierarchy under the
+                       host2 folder named str.
+                       (It does it internally by adding two 
+                       --regextrans2 options before all others.
+                       Add --debug to see what's really going on.)
+
+
+
+Things to know and understand before playing with --regextrans2
+
+*) --regextrans2 is used to transform folders names.
+
+*) --regextrans2 applies after the default 
+   inversion prefix1 <-> prefix2 and sep1 <-> sep2.
+   So, when elaborating the regex you should focus on
+   the right part of the default mapping printed by
+   imapsync, the part showing the host2 folder name.
+   The section to look at is either the folder size section
+   or within the folder loop located "Here" between the lines
+++++ Looping on each folder
+Here
+++++ End looping on each folder
+   
+*) Several --regextrans2 are possible, they will be applied in the order
+   of the command line, each one on the result of the previous one.
+
+*) --regextrans2 uses Perl regex mechanism so it may be hard to master
+   this part. It is powerful but not very simple.
+
+*) Windows vs Unix quotes. 
+
+   On windows don't use single quotes ' around the regex string, 
+   use double quotes instead, like --regextrans2 "myregex"
+
+   On Linux/Unix use single quotes ' around the regex string, it is
+   easier to get what we want with single quotes since the shell 
+   won't change the inner string. Use --regextrans2 'myregex'
+
+*) Good method to elaborate any --regextrans2 string
+
+   First, elaborate the --regextrans2 string with --dry --justfolders options. 
+
+     imapsync ... --dry --justfolders
+
+   With --dry imapsync shows the transformations it will do without 
+   really doing them, --dry is the "do nothing" mode.
+   With --justfolders imapsync will work only with folders, 
+   messages won't be taken into account, so it will be fast
+   and focused on the folders names.
+
+   When the output shows what you expect imapsync to do with folders
+   names, you can remove the --dry option. Keep the --justfolders 
+   option in order to see if the destination server host2 accepts
+   to create the folders.
+
+   When everything is ok with folders you might remove --justfolders,
+   imapsync will also transfer messages.
+   Showing folders sizes is good then transferring messages, it allows
+   ETA calculation and it's a supplementary check on folders.
+
+=======================================================================
+Q. Give examples about --regextrans2
+
+
+Examples: 
+
+1) To remove INBOX. in the name of destination folders
+
+  imapsync ... --regextrans2 's/^INBOX\.(.+)/$1/'
+
+2) To change only INBOX to Inbox_Migrated
+
+   imapsync ... --regextrans2 's{^INBOX$}{Inbox_Migrated}'
+
+
+2a) To sync all folders to INBOX
+
+  imapsync ... --regextrans2 "s/.*/INBOX/"
+
+
+2b) To sync a complete account in a subfolder called FOO
+
+With imapsync release 1.641 and former, simply use
+
+  imapsync ... --subfolder2 FOO
+  
+Examples to this subfolder problem for any release
+can be seen below, in another Q/R section.
+
+
+3) to substitute all characters dot "." by underscores "_"
+    --regextrans2 "s,\.,_,g"
+
+3b) to substitute all doublequotes " by underscores _
+
+On Linux/Unix:
+
+  --regextrans2 's,\",_,g' 
+
+On Windows:
+
+  --regextrans2 s,\^",_,g
+
+3c) to substitute all characters * % . and # by underscores _
+
+On Linux/Unix:
+
+  --regextrans2 'tr,*%.#,_,'
+
+On Windows:
+
+  --regextrans2 "tr,*%.#,_,"
+
+You can increase the *%.# list by any unwanted character,
+plus, the order doesn't count. See 3d) for &
+
+3d) It is a bad idea to substitute & characters since &
+is a character to encode non-ascii characters in IMAP folder names.
+
+
+4) to change folder names like this:
+[mail/Sent Items] -> [Sent]
+[mail/Test]       -> [INBOX/Test]
+[mail/Test2]      -> [INBOX/Test2]
+
+On Linux/Unix:
+
+    --regextrans2 's,^mail/Sent Items$,Sent,' \
+    --regextrans2 's,^mail/,INBOX/,'
+
+
+======================================================================
+Q. Is it possible to synchronize all messages from one server to 
+another without recreating the folder structure and the target server.
+
+R. Yes.
+
+For example, to synchronize all messages in all folders on host1
+to folder INBOX only on host2:
+
+1) First try (safe mode):
+
+  --regextrans2 "s/.*/INBOX/" --dry --justfolders
+
+2) See if the output says everything you want imapsync to do, 
+   --dry option is safe and does nothing real.
+   
+3) Remove --dry 
+   Check the imap folder tree on the target side, you should
+   only have one: the classical INBOX.
+
+4) Remove --justfolders
+
+
+=======================================================================
+Q. I would like to move emails from InBox to a sub-folder called,
+   say "2010-INBOX" based on the date. Like all emails received in the
+   year 2010 should be moved to the folder called "2010-INBOX".
+
+R. 2 ways :
+
+a) With imapsync:
+-----------------
+
+  imapsync ... \
+    --search "SENTSINCE 1-Jan-2010 SENTBEFORE 31-Dec-2010"
+    --f1f2 "INBOX=2010-INBOX" \
+    --folder INBOX
+
+See also the FAQ FAQ.Messages_Selection.txt
+https://imapsync.lamiral.info/FAQ.d/FAQ.Messages_Selection.txt
+to get more examples about how to select messages.
+
+b) Manually:
+------------
+
+1) You create a folder INBOX.2010-INBOX
+
+2) Mostly every email software allow sorting by date. In INBOX, you
+   select from 1 January to 31 December 2010 messages with the shift key.
+   (in mutt, use ~d)
+
+3) Cut/paste in INBOX.2010-INBOX
+
+
+=======================================================================
+Q. How to sync a complete account in a subfolder called FOO,
+   the hard way.
+
+R0. See the easy above using --subfolder2
+
+R1. Several ways to do it.
+
+  a) Separator is dot character "." and "INBOX" prefixes every folder
+
+On Linux/Unix:
+
+    --regextrans2 's,^INBOX(.*),INBOX.FOO$1,'
+
+On Windows:
+
+    --regextrans2 "s,^INBOX(.*),INBOX.FOO$1,"
+
+  or:
+  
+  b) Separator is the slash character "/" and there is no prefix 
+
+On Linux/Unix:
+
+   --regextrans2 's,(.*),FOO/$1,'
+   
+   or with doublequotes
+   
+   --regextrans2 "s,(.*),FOO/\$1,"
+
+On Windows:
+
+   --regextrans2 "s,(.*),FOO/$1,"
+   
+   or:
+
+  c) Any separator, any prefix solution, FOO is the subfolder:
+
+  It is a complicated line because every case is taken into account.
+  Type it in one line (or with the \ at the end of first line on Unix shells.
+
+On Linux/Unix:
+
+   --regextrans2 's,${h2_prefix}(.*),${h2_prefix}FOO${h2_sep}$1,' \
+   --regextrans2 's,^INBOX$,${h2_prefix}FOO${h2_sep}INBOX,'
+
+On Windows:
+
+  --regextrans2 "s,${h2_prefix}(.*),${h2_prefix}FOO${h2_sep}$1," ^
+  --regextrans2 "s,^INBOX$,${h2_prefix}FOO${h2_sep}INBOX,"
+
+  
+=======================================================================
+=======================================================================

FAQ.d/FAQ.Folders_Selection.txt

@@ -0,0 +1,112 @@
+#!/bin/cat
+$Id: FAQ.Folders_Selection.txt,v 1.8 2019/07/27 20:04:46 gilles Exp gilles $
+
+This documentation is also available online at
+https://imapsync.lamiral.info/FAQ.d/
+https://imapsync.lamiral.info/FAQ.d/FAQ.Folders_Selection.txt
+
+
+=======================================================================
+               Imapsync tips to select folders.
+=======================================================================
+
+By default, Imapsync syncs all folders, one by one, in alphanumeric order.
+
+The IMAP protocol has a specific way to code folders names,
+especially when these names use non-ascii 7bit characters.
+This encoding is called utf7imap. 
+
+Imapsync uses the same encoding as IMAP, utf7imap.
+
+In order to well specify folders names on the command line, imapsync
+prints the complete folder list of both sides at the beginning of each run.
+
+The left column is the encoding you have to use, without the first enclosing 
+square brackets [], the right column is the human utf8 view.
+
+
+
+=======================================================================
+Q. How can I sync only one folder?
+
+R. Use --folder option.
+
+  imapsync ... --folder MyFolder
+
+If you have more specific folders to sync just add several --folder 
+
+  imapsync ... --folder MyFolder --folder ThisFolder --folder ThatFolder
+
+
+=======================================================================
+Q. What are --subscribe and --subscribed for, and how can they be used?
+
+R. In the IMAP protocol each user can subscribe to one or more folders.
+   Then one can configure his email software to just see his subscribed
+   folders. That's an IMAP feature.
+
+   Imapsync can use this imap feature to select subscribed folders
+   and also subscribe to folders on host2. Here are the options:
+
+ --subscribed        : Transfers subscribed folders.
+ --subscribe         : Subscribe to the folders transferred on the
+                       host2 that are subscribed on host1. On by default.
+ --subscribeall      : Subscribe to the folders transferred on the
+                       host2 even if they are not subscribed on host1.
+
+
+=======================================================================
+Q. I want to exclude a folder hierarchy like "public"
+
+R. Use:
+
+--exclude "^public\."
+or maybe
+--exclude '^"public\.'
+
+In the example given the character "." is the folder separator, you
+can omit it. Just take the string as it appears on the imapsync
+output line :
+
+From folders list : [INBOX] [public.dreams] [etc.]
+
+
+=======================================================================
+Q. I want to exclude only INBOX
+
+R. Use:
+
+  imapsync ... --exclude "^INBOX$" 
+
+A good way to see what will be done is to first use:
+
+  imapsync ...  --exclude "^INBOX$" --justfolders --nofoldersizes --dry
+
+=======================================================================
+Q. I want to exclude folders matching SPAM no matter the case, 
+   aka how to be case insensitive
+
+R. Use:
+
+  imapsync ... --exclude "(?i)spam" 
+
+A good way to see what will be done is to first use:
+
+  imapsync ... --exclude "(?i)spam" --justfolders --nofoldersizes --dry
+
+
+=======================================================================
+Q. I want the --folder "MyFolder" option be recursive.
+
+Two solutions:
+
+R1. Use
+
+--folderrec "MyFolder"
+
+R2. Use --include "^MyFolder"
+   Then the folder "MyFolder" and all its subfolders will be handled
+   and only them.
+
+=======================================================================
+=======================================================================

FAQ.d/FAQ.Folders_Sizes.txt

@@ -0,0 +1,78 @@
+#!/bin/cat
+$Id: FAQ.Folders_Sizes.txt,v 1.3 2019/07/25 15:57:04 gilles Exp gilles $
+
+This documentation is also available online at
+https://imapsync.lamiral.info/FAQ.d/
+https://imapsync.lamiral.info/FAQ.d/FAQ.Folders_Sizes.txt
+
+=======================================================================
+  Imapsync tips to know folders sizes.
+=======================================================================
+
+Questions answered in this FAQ are:
+
+Q. How can I know the size of all folders before launching a sync?
+
+Q. The folders sizes and the number of messages don't match between
+   the source mailbox and the destination mailbox.
+   Why and what can I do?
+
+Now the questions again with their answers.
+
+
+=======================================================================
+Q. How can I know the size of all folders before launching a sync?
+
+R. Use --justfoldersizes option.
+
+With the --justfoldersizes option, imapsync evaluates and displays the 
+folders sizes on both sides and then exits without doing any transfer.
+Example:
+
+  imapsync ... --justfoldersizes
+
+=======================================================================
+Q. The folders sizes and the number of messages don't match between
+   the source mailbox on host1 and the destination mailbox on host2.
+   Why and what can I do?
+
+R. There are several reasons to explain the different counts between
+   source and destination after a sync.
+   
+1) The sync ended prematurely, before syncing all wanted folders.
+   Solution: run new syncs until completion.
+
+2) There are messages on host2 that are not on host1, so host2 is
+   bigger than host1. Imapsync doesn't delete any message by default. 
+   Solution: use --delete2 to have a strict sync by folder, ie, 
+   delete messages on host2 that are not on host1.
+   
+3) There are folders on host2 that are not on host1, so host2 is 
+   bigger. Imapsync doesn't delete any folder by default.
+   Solution: use --delete2folders to have a strict sync, ie, 
+   delete folders on host2 that are not on host1.
+
+4) There are duplicate messages on host1. Imapsync doesn't sync 
+   duplicates by default. But it counts them and presents the number
+   found at the end on the line "Messages found duplicate on host1". 
+   To sync duplicates, use option --useuid
+   --useuid has some caveats. See the documant FAQ.Duplicates.txt
+   for details about it at
+   https://imapsync.lamiral.info/FAQ.d/FAQ.Duplicates.txt
+
+5) There are duplicate messages on host2 so host2 is
+   bigger than host1. Solution: use --delete2duplicates to delete
+   the host2 duplicates.
+
+6) Cosmic rays...
+
+The important part to take into account is the last lines of imapsync
+if you encounter the line:
+"The sync looks good, all X identified messages in host1 are on host2."
+and also no unidentified messages.
+
+
+=======================================================================
+=======================================================================
+
+ 

FAQ.d/FAQ.GDPR.txt

@@ -0,0 +1,65 @@
+$Id: FAQ.GDPR.txt,v 1.4 2019/09/12 10:07:27 gilles Exp gilles $
+
+This document is also available online at
+https://imapsync.lamiral.info/FAQ.d/
+https://imapsync.lamiral.info/FAQ.d/FAQ.GDPR.txt
+
+=======================================================================
+ Imapsync and the GDPR, General Data Protection Regulation UE 2016/679
+=======================================================================
+
+Questions answered in this FAQ are:
+
+Q. Can you explain the compliance of imapsync with GDPR?
+   [General Data Protection Regulation UE 2016/679]
+
+
+Now the questions again with their answers.
+
+=======================================================================
+Q. Can you explain the compliance of imapsync with GDPR?
+   [General Data Protection Regulation UE 2016/679]
+
+R. 1) To know whether a newer imapsync exists or not, 
+      imapsync does a http GET to the file VERSION at
+      http://imapsync.lamiral.info/VERSION
+      
+ Via the HTTP User-agent header it also sends:
+  * the imapsync release
+  * the Perl version
+  * the Mail::IMAPClient version
+  * the Operating System
+  * the context ( Standard, CGI, or Docker )
+
+  You can remove this behavior by adding the option --noreleasecheck
+  on the command line or by setting $releasecheck = 0 in the source code. 
+  Check also https://nvd.nist.gov/vuln/detail/CVE-2013-4279
+
+  See also https://imapsync.lamiral.info/#NUMBERS
+
+2) Each imapsync run generates a logfile that corresponds exactly 
+   to the output printed on the console during the run. 
+   This log file contains data from the mailboxes, 
+   not the content messages, not the passwords but 
+   it contains the folders names and the login names.
+   Remove the log or use the option --nolog to avoid logging.
+
+3) In case you purchase imapsync:
+
+3.1) the data collected during the purchase,
+   Name, Company Name, Postal Address, VAT number, Price,
+   will be used to edit the invoice. I (Gilles LAMIRAL) keep a copy
+   of the invoice for accounting.
+   
+3.2)  Once in a while, I send an email to the buyers announcing 
+      a new imapsync is released and where to get it.
+   
+3.3) If the customer is a professional inside the EU, 
+   I also use his company VAT number and the amount to declare it
+   to the Customs each month, before the 10th of the month, at
+   https://pro.douane.gouv.fr/ 
+   It's mandatory, it's the law inside EU and the fine is 750 EUR/month
+   when it is not done or not well done a month.
+
+=======================================================================
+=======================================================================

FAQ.d/FAQ.General.txt

@@ -0,0 +1,775 @@
+#!/bin/cat
+# $Id: FAQ.General.txt,v 1.242 2019/12/11 20:28:33 gilles Exp gilles $
+
+=======================================================================
+                     General FAQ for imapsync 
+=======================================================================
+
+This document is also available online at
+https://imapsync.lamiral.info/FAQ.d/
+https://imapsync.lamiral.info/FAQ.d/FAQ.General.txt
+
+Questions answered in this FAQ are:
+
+Q. Do I need to create IMAP mailboxes at the destination platform?
+
+Q. Am I forced to publish the IMAP service on the Internet since the two
+   environment are not in the same location or same LAN?
+
+Q. What are the most important differences between the Unix shell syntax
+   and the Windows batch syntax.
+
+Q. How to install imapsync?
+
+Q. How to use imapsync?
+
+Q. Can you give some configuration examples?
+
+Q. How can I have commercial support?
+
+Q. How can I have gratis support?
+
+Q. Where I can find old imapsync releases?
+
+Q. Where I can find free open and gratis imapsync releases?
+
+Q. Is is legal to find imapsync gratis (or not) elsewhere?
+
+Q. How "Facts and figures" are known 
+   https://imapsync.lamiral.info/#NUMBERS
+
+Q. I use --useuid which uses a cache in /tmp or --tmpdir, the hostnames
+   host1 or host2 has changed but mailboxes are the same. Will imapsync
+   generate duplicate messages on next runs?
+
+Q. How can I speed up transfers?
+
+Q. I see warning messages like the following:
+   "Host1 Sent/15 size 1428 ignored (no header so we ignore this message.
+   To solve this: use --addheader)".
+   What can I do to transfer those messages?
+
+Q. How can I try imapsync with latest Mail::IMAPClient 3.xx perl module?
+
+Q. How can I use imapsync with Mail::IMAPClient 2.2.9 perl module?
+
+Q. How to verify imapsync.exe I got is the right file bit per bit?
+
+Q. Folders are not created on host2. What happens?
+
+Q. I am interested in creating a local clone of the IMAP on a LAN 
+   server for faster synchronizations, email will always be delivered 
+   to the remote server and so the synchronization will be one way - from 
+   remote to local. How suited is imapsync for continuous one-way 
+   synchronization of mailboxes? Is there a better solution?
+
+Q. I need to log every output on a file named log.txt
+
+Q. Quantifier in {,} bigger than 32766 in regex; marked by <-- HERE in 
+   m/(.{ <-- HERE 1,49947})(?:,|$)/ at Mail/IMAPClient.pm line 2121.
+
+Q. Couldn't create [INBOX.Ops/foo/bar]: NO Invalid mailbox name: 
+   INBOX.Ops/foo/bar 
+
+Q. Is it possible to sync also the UIDL of the POP3 server?
+
+Q. Is it possible to sync also the UIDs of the IMAP server?
+
+Q. The option --subscribe does not seem to work
+
+Q. With huge account (many messages) when it comes to reading the
+   destination server it comes out this error:
+   "To   Folder [INBOX.foobar] Not connected" 
+   What can I do?
+
+Q. Can Imapsync filter Spam during the sync?
+
+Q. How to migrate from uw-imap with an admin/authuser account?
+
+Q. How to migrate from cyrus with an admin account?
+
+Q: How to migrate from Sun Java Enterprise System / Sun One / iPlanet /
+   Netscape servers with an admin account?
+
+Q. Is there a way to delete the destination folder when the source 
+   folder is no longer there?
+
+Q. I would love to have a function to inject lines in the header. 
+   Things like "X-migrated-from-foo: 20100617"
+
+Q. I want to play with headers line and --regexmess but I want to leave
+   the body as is.
+
+Q. My imap server does not accept a message and warns
+   "Invalid header". What is the problem?
+
+Q. The contact folder isn't well copied. 
+   How to copy the contact folder?
+
+Q: How can I write an .rpm with imapsync
+
+Q. Where I can read up on the various IMAP RFCs?
+
+Now the questions again with their answers.
+
+=======================================================================
+Q. Do I need to create IMAP mailboxes at the destination platform?
+
+R. Yes!
+   Imapsync does only IMAP and there is no way to create an account 
+   with the standard IMAP protocol. So you have to create them first.
+
+=======================================================================
+Q. Am I forced to publish the IMAP service on the Internet since the two
+   environment are not in the same location or same LAN?
+
+R. The host where you run imapsync has to contact both servers via imap.
+   You are not obliged to publish the imap service on the Internet if 
+   the host running imapsync can contact both imap servers via imap. 
+   Use their names or their IP addresses.
+
+=======================================================================
+Q. What are the most important differences between the Unix shell syntax
+   and the Windows batch syntax.
+
+R. There are several differences between Unix and Windows
+in the command line syntax. 
+- Character \ on Unix versus ^ on Windows 
+- Character ' on Unix versus " on Windows 
+
+Details:
+
+A) \ versus ^
+
+On Unix shells you can write a single command on multiple lines
+by using the escape character \ at the end of each line 
+(except the last one). On Windows this character is ^
+
+Unix example:
+
+./imapsync \
+   --host1 imap.truc.org --user1 foo --password1 secret1 \
+   --host2 imap.trac.org --user2 bar --password2 secret2
+
+
+Windows example:
+
+imapsync ^
+   --host1 imap.truc.org --user1 foo --password1 secret1 ^
+   --host2 imap.trac.org --user2 bar --password2 secret2
+
+
+Of course you can write the command on a single line without 
+characters \ nor ^. I use them because the output is
+better, no truncation, pretty print. It's just sugar!
+
+In this FAQ I use \ for examples. Transcript to ^ if
+you're on a Windows system.
+
+B) Quote vs Double-quote, ie ' versus " 
+
+On Windows the single quote character ' doesn't work
+like on Unix so in the examples of this FAQ the 
+command containing single quotes ' will fail on Windows.
+To fix this, just replace single quotes ' by double quotes "
+
+Also on Windows, in examples with \$1, replace 
+any \$1 by $1 (remove the \ before $).
+
+=======================================================================
+Q. How to install imapsync?
+
+R. Read the INSTALL files in the tarball. also available at
+   https://imapsync.lamiral.info/#doc
+   https://imapsync.lamiral.info/INSTALL.d/
+
+=======================================================================
+Q. How to use imapsync?
+
+R. Read the TUTORIAL_Unix.txt file, maybe the README and, if you 
+   encounter problems, the  FAQ.d/* files in the tarball.
+   All are also available and updated at:
+   https://imapsync.lamiral.info/#doc
+
+=======================================================================
+Q. Can you give some configuration examples?
+
+R1. Basic usage is described there:
+    https://imapsync.lamiral.info/#DOC_BASIC
+
+It is:
+
+  imapsync --host1 test1.lamiral.info --user1 test1 --password1 secret1 \
+           --host2 test2.lamiral.info --user2 test2 --password2 secret2
+
+R2. Some FAQ files contains many examples for several scenarios
+    https://imapsync.lamiral.info/#doc
+    (Gmail, Office365, Exchange, Darwin, etc.)
+
+=======================================================================
+Q. How can I have commercial support?
+
+R. Buy support from imapsync author: Gilles LAMIRAL
+https://imapsync.lamiral.info/#buy_all
+
+=======================================================================
+Q. How can I have gratis support?
+
+R. Write to the imapsync author: Gilles LAMIRAL
+https://imapsync.lamiral.info/#AUTHOR
+
+I help all users as long as I have time to help them all, 
+users who bought the support get my help first.
+
+=======================================================================
+Q. Where I can find old imapsync releases?
+
+R. Search the internet or ask the author.
+
+=======================================================================
+Q. Where I can find free open and gratis imapsync releases?
+
+R. Search the internet or ask the author.
+
+Q. Is is legal to find imapsync gratis (or not) elsewhere?
+
+R. Yes, the license permits it
+   https://imapsync.lamiral.info/NOLIMIT
+
+=======================================================================
+Q. How "Facts and figures" are known 
+   https://imapsync.lamiral.info/#NUMBERS
+
+R. To know wether a newer imapsync exists or not, imapsync does a http 
+   GET to http://imapsync.lamiral.info/VERSION
+   Via the User-agent parameter it also send:
+
+    * imapsync release
+    * Perl version
+    * Mail::IMAPClient version
+    * Operating System
+
+You can remove this behavior by adding option --noreleasecheck on the
+command line (or by setting $releasecheck = 0 in the source code)
+or by using the github release.
+
+=======================================================================
+Q. I use --useuid which uses a cache in /tmp or --tmpdir, the hostnames
+   host1 or host2 has changed but mailboxes are the same. Will imapsync
+   generate duplicate messages on next runs?
+
+R. Yes
+
+Q. How can I fix this?
+
+R. The cache path reflects exactly hostnames or ip addresses given via
+   --host1 and --host2 values. So just change the directory names 
+   of host1 or host2. Use --dry to see if next runs will generate 
+   duplicates.
+   By default on Unix the cache is like 
+
+   /tmp/imapsync_cache/host1/user1/host2/user2/...
+
+=======================================================================
+Q. How can I speed up transfers?
+
+R. By using --useuid imapsync avoid getting messages headers and build
+   a cache. On Unix a good thing is to add also --tmpdir /var/tmp
+   to keep the cache since /tmp is often cleared on reboot.
+
+   imapsync ... --useuid 
+
+On Unix:
+
+   imapsync ... --useuid --tmpdir /var/tmp/
+
+R. Add also --nofoldersizes since the default behavior is to compute
+   folder sizes. Folder sizes are useless for the transfer, just 
+   useful to see what has to be done on each folder and guess when 
+   the transfer will end (ETA).
+
+R. Add also --noexpungeaftereach if you use --delete1. 
+   But be warn that an interrupted transfer can lose messages 
+   on host2 in a second run if you use a (silly) combination like:
+
+   imapsync ... --delete1 --noexpunge1 --noexpungeaftereach --expunge2
+
+Notes about --useuid
+
+Case where building the cache first is necessary (to avoid multiples transfers)
+
+If you run again imapsync with --useuid on a transfer  already done without 
+--useuid then, to avoid messages be copied again, first run imapsync 
+with --usecache but without --useuid, example scenario:
+
+A] Running with the default options, I began without --useuid 
+
+1) First run with default options
+
+  imapsync ...
+
+Too slow, I want to speed up!
+
+2) Build the cache
+
+ imapsync ... --usecache
+
+3) Speed up now
+
+  imapsync ... --useuid
+
+B] I began with --useuid from the first time
+
+1) First run and next runs with --useuid
+
+  imapsync ... --useuid
+
+
+Inodes number issue.
+
+The cache is simple, it uses the file-system natively, 
+it's just an empty file per message transfered.
+When mailboxes are huge the cache can exhaust the number of inodes 
+allowed in the filesystem, that's a limitation like limitation
+size but it's less often encountered.
+
+On Unix, to predict whether your tmpdir filesystem used by imapsync 
+will support the whole cache, just run the command "df -i /var/tmp", 
+if /var/tmp is the --tmpdir argument.
+
+On windows, search and drop me a note about how to count the number 
+of files allowed in the filesystem. 
+It seems FAT32 supports 268 435 445 clusters.
+
+Choosing the number of inodes allowed by a filesystem can be done 
+at the creation of it with "mkfs -N number-of-inodes ..."
+
+imapsync can predict how many messages have to be synced with the 
+option --justfoldersizes (no transfer will be done)
+
+  imapsync ... --justfoldersizes
+
+
+=======================================================================
+Q. I see warning messages like the following:
+   "Host1 Sent/15 size 1428 ignored (no header so we ignore this message.
+   To solve this: use --addheader)".
+   What can I do to transfer those messages?
+
+
+R1. Like suggested inline, use --addheader option. 
+Option --addheader will add an header line like 
+Message-Id: <15@imapsync>
+where 15 is the message UID number on host1.  
+Then imapsync will transfer the changed message on host2.
+Duplicates won't happen on next runs.
+
+   imapsync ... --addheader
+
+R2. Other solution. 
+Use --useuid then imapsync will avoid dealing with headers.
+
+   imapsync ... --useuid
+
+=======================================================================
+Q. How can I try imapsync with latest Mail::IMAPClient 3.xx perl module?
+
+Three solutions at least.
+
+R1 - Look at the script named "i3" in the tarball, it can be used to
+     run imapsync with the included Mail-IMAPClient-3.39/ wherever you 
+     unpacked the imapsync tarball
+
+R2 Run:
+
+   cpanm Mail::IMAPClient # this uses cpanminus
+
+   or
+
+   cpan -i Mail::IMAPClient 
+   
+   or
+
+   perl -MCPAN -e "install Mail::IMAPClient"
+   
+
+R3 If you want to install the Perl module locally in a directory
+
+   - Download latest Mail::IMAPClient 3.xx at
+     http://search.cpan.org/dist/Mail-IMAPClient/
+
+   - untar it anywhere:
+        tar xzvf Mail-IMAPClient-3.xx.tar.gz
+
+   - Get any imapsync (latest is better).
+
+   - run imapsync with perl and -I option tailing to use the perl
+     module Mail-IMAPClient-3.xx. Example:
+
+         perl -I./Mail-IMAPClient-3.39/lib  ./imapsync ...
+
+     or if imapsync is in directory /path/
+        perl -I./Mail-IMAPClient-3.39/lib   /path/imapsync ...
+
+
+=======================================================================
+Q. How can I use imapsync with Mail::IMAPClient 2.2.9 perl module?
+
+R. Mail::IMAPClient 2.2.9 is no longer supported.
+
+=======================================================================
+Q. How to verify imapsync.exe I got is the right file bit per bit?
+
+R. Use md5sum to check integrity of the file.
+   Get md5sum.exe at http://etree.org/md5com.html
+
+   md5sum imapsync.exe
+
+   Then compare the checksum with the one given by the author.
+
+=======================================================================
+Q. Folders are not created on host2. What happens?
+
+R. Do you use IMAP or POP3 with your client software?
+It looks like you use POP3 instead of IMAP, POP3 sees only INBOX.
+
+
+=======================================================================
+Q. I am interested in creating  a local clone of the IMAP on a LAN 
+   server for  faster synchronizations, email will always be delivered 
+   to the remote server and so the synchronization will be one way - from 
+   remote to local. How suited is imapsync for continuous one-way 
+   synchronization of mailboxes? Is there a better solution?
+
+R. If messages are delivered remotely and you play locally with the
+   copy, in order to have fast access, then the synchronization can't
+   be one way. You may change flags, you may move messages in 
+   different folders etc. The issue described is clearly 
+   two-ways sync.
+
+   A better tool with this scenario is offlineimap, 
+   designed for this issue, and faster than imapsync.
+
+
+=======================================================================
+Q. I need to log every output on a file named log.txt
+
+R1. imapsync logs on a file by default, its name is given at the 
+    beginning and the end of each run. This name is unique since
+    it is compound of the current date and time and user2 value. 
+
+R2. To change this default name, use --logfile log.txt
+
+  imapsync ... --logfile log.txt
+
+
+=======================================================================
+Q. Quantifier in {,} bigger than 32766 in regex; marked by <-- HERE in 
+   m/(.{ <-- HERE 1,49947})(?:,|$)/ at Mail/IMAPClient.pm line 2121.
+
+R. Do not use a bigger value than 3276 with --split1 or --split2
+ 
+=======================================================================
+Q. Couldn't create [INBOX.Ops/foo/bar]: NO Invalid mailbox name: 
+   INBOX.Ops/foo/bar 
+
+Let begin by an explanation.
+
+Example:
+sep1 = /
+sep2 = .
+
+imapsync reverts each separator automatically. 
+
+a) All / character coming from host1 are converted to . (convert the separator)
+b) All . character coming from host1 are converted to / (to avoid 
+intermediate unwanted folder creation). 
+
+So 
+INBOX/Ops.foo.bar (Ops.foo.bar is just one folder name) will be translated to 
+INBOX.Ops/foo/bar 
+
+Sometimes the sep1 character is not valid on host2 (character "/" usually)
+
+R. Try :
+
+  --regextrans2 "s,/,X,g"
+
+It'll convert / character to X 
+Choose X as you wish: _ or SEP or 
+any string (including the empty string).
+
+This issue is automatically fixed by default since imapsync 
+release 1.513, use --nofixslash2 to suppress the fix.
+
+=======================================================================
+Q. Is it possible to sync also the UIDL of the POP3 server?
+
+R. imapsync doesn't talk POP3 but I think you mean UID in IMAP.
+   See next question.
+
+=======================================================================
+Q. Is it possible to sync also the UIDs of the IMAP server?
+
+R. UIDs in IMAP are chosen and created by the server, not by the 
+   client software. imapsync is a client software. So UIDs cannot 
+   be synced by any imap method.
+
+   UIDs may be synced via a rsync command between the imap servers but
+   it implies they are the same software, among other constraints.
+
+=======================================================================
+Q. The option --subscribe does not seem to work
+
+R1. Use it with --subscribed
+
+R2. There is also the --subscribe_all option that subscribe
+    to all folders on host2.
+
+=======================================================================
+Q. With huge account (many messages) when it comes to reading the
+   destination server it comes out this error:
+   "To   Folder [INBOX.foobar] Not connected" 
+   What can I do?
+
+R. May be spending too much time on the source server, the connection 
+   timed out on the destination server.
+   Try options --nofoldersizes 
+
+======================================================================
+Q. Can Imapsync filter Spam during the sync?
+
+R. No, imapsync doesn't detect Spam by itself. But I've seen blogs and
+   Spamassassin documentation explaining solutions to apply Spamassassin
+   to a imap mailbox. So you can apply one of these solutions on the host1
+   source mailbox before the imapsync run or on the destination host2
+   mailbox after the imapsync transfer.
+
+http://www.stearns.org/doc/spamassassin-setup.current.html#isbg
+http://euer.krebsco.de/using-spamassassin-on-a-remote-imap-host.html
+https://github.com/ook/isbg
+
+   Imapsync can delegate this job during its IMAP syncs via the 
+   --pipemess option but the underlying spam tool has to be written.
+   
+======================================================================
+Q. How to migrate from uw-imap with an admin/authuser account?
+
+R. Use the following syntax:
+
+  imapsync ... --user1="loginuser*admin_user" --password1 "admin_user_password"
+
+
+======================================================================
+Q. How to migrate from cyrus with an admin account?
+
+R. Use:
+ 
+ imapsync ... \
+   --authuser1 admin_user  ----password1 admin_user_password \
+   --user1 foo_user --ssl1
+
+Instead of --ssl1 the alternative --tls1 can be used.
+With --authuser1, the option --authmech1 PLAIN is set
+automatically, you don't have to add it.
+
+PLAIN authentication is the only way to go with --authuser1 for now.
+So don't use --authmech1 SOMETHING with --authuser1 admin_user,
+it will not work.
+Same behavior with the --authuser2 option.
+
+Do not forget the option --ssl1 or --tls1 since PLAIN auth is only
+supported with ssl encryption most of the time. But it can
+work without --ssl1 nor --tls1 if PLAIN is permitted in clear text
+transmissions (the normal mode).
+
+Add the AdminAccount to admins line in /etc/imapd.conf
+Give AdminAccount lrswipkxtecda to the Cyrus Imap account 
+being migrated from, "joe" here.
+
+
+Here is an example:
+ imapsync \
+	--host1 server1 \
+	--user1 joe \
+	--authuser1 AdminAccount \
+	--password1 AdminAccountPassword \
+	--ssl1 \
+	--host2 server2 \
+	--user2 joe \
+	--password2 joespassonserver2 \
+	--exclude "^user\."
+
+======================================================================
+Q: How to migrate from Sun Java Enterprise System / Sun One / iPlanet /
+   Netscape servers with an admin account?
+
+R: Those imap servers don't allow the typical use of --authuser1 to use an
+administrative account. They expect the use of an IMAP command called
+proxyauth that is issued after login in as an administrative account.
+
+For example, consider the administrative account 'administrator' and your
+real user 'real_user'. The IMAP sequence would be:
+
+  OK [CAPABILITY IMAP4 IMAP4rev1 ACL QUOTA LITERAL+ NAMESPACE UIDPLUS
+  CHILDREN BINARY UNSELECT LANGUAGE STARTTLS XSENDER X-NETSCAPE XSERVERINFO
+  AUTH=PLAIN] imap.server IMAP4 service (Sun Java(tm) System Messaging
+  Server ...))
+  1 LOGIN administrator password
+  1 OK User logged in
+  2 PROXYAUTH real_user
+  2 OK Completed
+
+In imapsync, you can achieve this by using the following options:
+
+  --host1 source.imap.server \
+  --user1 real_user \
+  --authuser1 administrator \
+  --proxyauth1 \
+  --passfile admin.txt
+
+======================================================================
+Q. Is there a way to delete the destination folder when the source 
+   folder is no longer there?
+
+R. Yes, use --delete2folders
+
+--delete2folders       : Delete folders in host2 that are not in host1 server. 
+                         For safety, first try it like this (it is safe):
+			 --delete2folders --dry --justfolders --nofoldersizes
+--delete2foldersonly   <regex>: Deleted only folders matching regex.
+                         Example: --delete2foldersonly "/^Junk$|^INBOX.Junk$/"
+--delete2foldersbutnot <regex>: Do not delete folders matching regex.
+                         Example: --delete2foldersbutnot "/Tasks$|Contacts$|Foo$/"
+
+=======================================================================
+Q. I would love to have a function to inject lines in the header. 
+   Things like "X-migrated-from-foo: 20100617"
+
+R. You can do that with:
+
+  imapsync ... --regexmess 's/\A/X-migrated-from-foo: 20100617\n/'
+
+It will insert a first header line containing "X-migrated-from-foo: 20100617" 
+
+=======================================================================
+Q. I want to play with headers line and --regexmess but I want to leave
+   the body as is.
+
+R. The header/body separation is a blank line so an example:
+   --regexmess 's{\A(.*?(?! ^$))^Date:(.*?)$}{$1Date:$2\nX-Date:$2}gxms'
+
+Will replace the next three lines
+
+Message-ID: <499EF800.4030002@blabla.fr>
+Date: Fri, 20 Feb 2009 19:35:44 +0100
+From: Gilles LAMIRAL <lamiral@linux-france.org>
+
+by the next four lines
+
+Message-ID: <499EF800.4030002@blabla.fr>
+Date: Fri, 20 Feb 2009 19:35:44 +0100
+X-Date: Fri, 20 Feb 2009 19:35:44 +0100
+From: Gilles LAMIRAL <lamiral@linux-france.org>
+
+
+This example just add an header line "X-Date:" based on "Date:" line.
+
+=======================================================================
+Q. My imap server does not accept a message and warns
+   "Invalid header". What is the problem?
+
+R. You fall in the classical mbox versus Maildir/ format
+   problem. May be you use a misconfigured procmail rule.
+
+A header beginning like the following one is in the mbox
+format, header line 1 has no colon behind "From", header
+lines 2 through N do have a colon :
+
+From foo@yoyo.org  Sat Jun 22 01:10:21 2002
+Return-Path: <foo@yoyo.org>
+Received: ...
+
+Any Maildir/ configured imap server may refuse this message since its
+header is invalid. The first "From " line is not valid. It lacks a
+colon character ":". To solve this issue you have several solutions
+
+a) Remove manually this first "From " line for each message before
+   using imapsync. 
+
+b) Replace manually the whitespace by a colon in string "From " but you
+   might end with two "From:" lines (just have a look at the other 
+   header lines of the message)
+
+c) Run imapsync with the following option (this replaces "From "by "From:"):
+   --regexmess 's/\AFrom /From: /'
+
+or may be better (no other "From:" collision):
+
+d) Run imapsync with the following option (this replaces "From "by "X-om:"):
+   --regexmess 's/\AFrom /X-From: /'
+
+e) Run imapsync with the following option (this removes the whole "From " line):
+   --regexmess 's{\AFrom\ [^\n]*(\n)?}{}gxms'
+
+Solution e) is solution a) made by imapsync itself.
+Solutions c) and d) keep "From " lines information
+(normally it's useless to keep them)
+
+Best solutions are e) or d).
+
+=======================================================================
+Q. The contact folder isn't well copied. 
+   How to copy the contact folder?
+
+R. Forget the destination server (choose the same)
+Change the script around line 1426
+       # ITSD
+       $new_id = $from->copy($t_fold,$f_msg);
+       #$new_id = $to->append_string($t_fold,$string, $flags_f, $d);
+
+and tried a copy of the mail instead an append_string. Because we are
+using the same server, we can use $from->copy Therefore we seem to not
+download and upload the message and therefore we do not have any
+format issues. And now it works fine. (Thanks to Hansjoerg.Maurer)
+
+
+======================================================================
+Q: How can I write an .rpm with imapsync
+
+R. You'll find an RPM imapsync.spec file in the directory learn/rpm/
+   It has been downloaded from
+   https://svn.fysik.dtu.dk/projects/rpmbuild/trunk/SPECS/imapsync.spec
+   It has been tested with imapsync 1.434 (May 2011) on CentOS5 
+   and RedHat RHEL5 Linux. (Thanks to Ole Holm Nielsen).
+   This imapsync.spec is coming from Neil Brown work in 2007.
+
+=======================================================================
+Q. Where I can read up on the various IMAP RFCs?
+
+R. Here:
+
+RFC 3501 - INTERNET MESSAGE ACCESS PROTOCOL - VERSION 4rev1
+http://www.faqs.org/rfcs/rfc3501.html
+
+RFC 2683 - IMAP4 Implementation Recommendations
+http://www.faqs.org/rfcs/rfc2683.html
+
+RFC 2595 - Using TLS with IMAP, POP3 and ACAP
+http://www.faqs.org/rfcs/rfc2595.html
+
+RFC 2822 - Internet Message Format
+http://www.faqs.org/rfcs/rfc2822.html
+
+RFC 2342 - IMAP4 Namespace
+http://www.faqs.org/rfcs/rfc2342.html
+
+RFC 2180 - IMAP4 Multi-Accessed Mailbox Practice
+http://www.faqs.org/rfcs/rfc2180.html
+
+RFC 4549 - Synchronization Operations for Disconnected IMAP4 Clients
+http://www.faqs.org/rfcs/rfc4549.html
+
+
+=======================================================================
+=======================================================================

FAQ.d/FAQ.Gmail.txt

@@ -0,0 +1,610 @@
+#!/bin/cat
+$Id: FAQ.Gmail.txt,v 1.65 2019/12/04 18:26:00 gilles Exp gilles $
+
+This document is also available online at
+https://imapsync.lamiral.info/FAQ.d/
+https://imapsync.lamiral.info/FAQ.d/FAQ.Gmail.txt
+
+=======================================================================
+              Imapsync tips for Gmail accounts.
+=======================================================================
+
+Questions answered in this FAQ are:
+
+Q. Can I use imapsync to transfer from or to Gmail accounts?
+
+Q. Even after several syncs the number of messages differs
+   largely between imapsync and the Gmail web interface.
+   What can I do?
+
+Q. How many days does it take to transfer X GB?
+
+Q. How to synchronize from Gmail to Gmail?
+
+Q. How to synchronize from XXX to Gmail?
+
+Q. How to synchronize from Gmail to XXX?
+
+Q. I can't authenticate with Gmail via IMAP
+   and Gmail says "Please log in via your web browser"
+
+Q. Can not open imap connection on [imap.gmail.com]
+   Unable to connect to imap.gmail.com
+
+Q. Can I transfer "Chat" messages with imapsync?
+
+Q. Can I safely use --useuid for Gmail transfers?
+
+Q. Gmail does not really delete messages in folder [Gmail]/All Mail
+   What happens? What can I do?
+
+Q. Can I use the Extension of the SEARCH command: X-GM-RAW described at
+   https://support.google.com/mail/answer/7190?hl=en
+   https://developers.google.com/gmail/imap_extensions#extension_of_the_search_command_x-gm-raw
+
+Q. How to avoid the [IMAP] prefix on Gmail side?
+
+Q. Does imapsync have the capability to do 2 stage authentication?
+
+Q. How to use XOAUTH2 to globally authenticate gmail users?
+
+Q. How to use XOAUTH to globally authenticate gmail users?
+
+Q. How to use a Gmail account to backup several different imap accounts?
+
+Q. How to migrate email from gmail to google apps?
+
+
+Now the questions again with their answers.
+
+=======================================================================
+Q. Can I use imapsync to transfer from or to Gmail accounts?
+
+R. Yes. But IMAP access to a Gmail account is not allowed by default so 
+it has to be allowed in the Gmail configuration part:
+ -> Settings
+ -> Forwarding and POP/IMAP
+ -> IMAP Access
+ -> Enable IMAP
+
+Also, there is the authentication issue to consider.
+There are three different ways to authenticate to Gmail with Imapsync,
+either:
+
+* "Access for less secure apps"
+* "2-step verification"
+* XOauth
+
+For the last one, XOauth, see the document 
+https://imapsync.lamiral.info/FAQ.d/FAQ.XOAUTH2.txt
+
+1) "Access for less secure apps" is turned ON
+ 
+ -> Verify 2-step verification is OFF
+    https://myaccount.google.com/security?hl=en&pli=1&nlr=1#signin
+ -> Turn ON "Access for less secure apps"
+    https://www.google.com/settings/security/lesssecureapps
+    https://support.google.com/accounts/answer/6010255?hl=en
+
+Sometimes, with Gsuite, the login for the users are ok with imapsync
+for a while then they become forbidden with 
+"failure: Error login on [imap.gmail.com] with user [xxx] auth [LOGIN]: 
+2 NO [AUTHENTICATIONFAILED] Invalid credentials (Failure)"
+
+In that case, use:
+https://admin.google.com/AdminHome?hl=fr#ServiceSettings/notab=1&service=securitysetting&subtab=lesssecureappsaccess
+to allow "Access for less secure apps to all users"
+(Thanks to Sébastien R. for this input)
+
+2) "2-step verification" is turned ON
+
+Follow
+https://support.google.com/accounts/answer/185833?hl=en
+Even if Google says "Every App Password is only used once",
+it's false and the password can be used many times.
+
+
+=======================================================================
+Q. Even after several syncs the number of messages differs
+   largely between imapsync and the Gmail web interface.
+   What can I do?
+
+R. Turned off "Conversation views" on Gmail.
+With "Conversation views" turned off, Gmail shows the exact message 
+count for each folder and it matches what imapsync shows. 
+With "Conversation views" on, a single conversation can have 
+multiple messages and it doesn't match what imapsync presents.
+(Thanks to Karthik.V for this input)
+
+=======================================================================
+Q. How many days does it take to transfer X GB?
+
+R. Basically it takes X days to transfer X GB per account.
+   Gmail has usage limits per day and use throttles when
+   they are overtaken
+   http://support.google.com/a/bin/answer.py?hl=en&answer=1071518
+   From the previous link:
+
+   * it's 2X days to upload  X GB to Gmail, it's why I suggest to add
+   --maxbytespersecond 10000 --maxbytesafter 1_000_000_000
+   for uploading messages to Gmail
+   * it's X/2 days to download X BG from Gmail, it's why I suggest to add
+   --maxbytespersecond 20000 --maxbytesafter 1_000_000_000
+   for downloading messages from Gmail
+  
+   That's theoretical values that always work in practice. Try
+   upper values and see if they still work.
+
+   How Gmail says limits are reached?
+   This is either a disconnection with
+   "BYE Session expired, please login again"
+   or a very small rate, less than 1 Kib/s
+
+https://imapsync.lamiral.info/FAQ.d/FAQ.Gmail.txt
+=======================================================================
+Q. How to synchronize from Gmail to Gmail?
+
+R. Use the following example:
+
+imapsync  \
+           --user1 account1@gmail.com \
+           --password1 gmailsecret1 \
+           --user2 account2@gmail.com \
+           --password2 gmailsecret2 \
+           --gmail1 --gmail2 
+
+Or, replacing what does --gmail1 --gmail2 (values are from imapsync 1.970):
+
+imapsync \
+           --host1 imap.gmail.com \
+           --ssl1 \
+           --user1 account1@gmail.com \
+           --password1 gmailsecret1 \
+           --host2 imap.gmail.com \
+           --ssl2 \
+           --user2 account2@gmail.com \
+           --password2 gmailsecret2 \
+           --maxbytespersecond 20_000 \
+           --maxbytesafter 1_000_000_000 \
+           --automap \
+           --maxsleep 2 \
+           --synclabels \
+           --resynclabels \
+           --exclude "\[Gmail\]$" \
+           --folderlast  "[Gmail]/All Mail"
+
+With --gmail1 --gmail2 you can override the parameters
+that are activated by them, for example:
+
+imapsync ... --gmail1 --gmail2 --maxbytespersecond 50_000 --noautomap
+
+Explanations:
+
+
+--maxbytespersecond 20_000 ( 20 kBytes/s ) option is here to avoid 
+locking or errors when imap transfers exceed Gmail maximum limit. 
+See http://support.google.com/a/bin/answer.py?hl=en&answer=1071518
+--maxbytespersecond 20_000 is not mandatory in the sense Gmail may 
+allow you to use an upper value than 1 GBytes per 24h without 
+disconnections. If you count well, it should be 10_000, not 20_000.
+
+--maxbytesafter 1_000_000_000 option is there because 
+option --maxbytespersecond 20000 is unnecessarily slow if the Gmail 
+account size is less than 1 GB.
+
+--maxsleep 2 is to avoid sleeping more than 2 seconds when 
+the --maxbytespersecond value implies a long sleep between 2 copies.
+
+--automap is not mandatory but it's a feature to automatically
+map folder names based on the Gmail user configuration itself, par account.
+It will save manual folder names changes or the use of --regextrans2 
+or --f1f2 to map folder names.
+For example, imap folder "[Gmail]/Sent Mail" may be mapped as one of
+E-mails enviados
+Enviada
+Enviado
+Gesendet
+Gönderildi
+Inviati
+Sendt
+Skickat
+Verzonden
+etc.
+on both sides, host1 or host2, maybe differently, sometimes in 
+incomprehensible alphabets, a headache for imap sysadmins.
+See a listing here:
+http://stackoverflow.com/questions/2185391/localized-gmail-imap-folders/2185548#2185548
+
+--exclude "\[Gmail\]$"   is just there to avoid a warning error
+when selecting this not used folder.
+
+Be aware that --gmail1 --gmail2 is a special case, it's not what
+--gmail1 does plus what --gmail2 does when they are not invoked 
+together.
+
+
+https://imapsync.lamiral.info/FAQ.d/FAQ.Gmail.txt
+=======================================================================
+Q. How to synchronize from XXX to Gmail?
+
+R. Use the following example:
+
+imapsync --host1 mail.oldhost.com     \
+         --user1 my_email@oldhost.com \
+         --password1 passwordold   \
+         --user2 my_email@gmail.com \
+         --password2 gmailsecret \
+         --gmail2
+
+Or, replacing what does --gmail2 (values are from imapsync 1.970):
+(For Linux only because of the quotes)
+
+imapsync --host1 mail.oldhost.com     \
+         --user1 my_email@oldhost.com \
+         --password1 passwordold   \
+         --host2 imap.gmail.com \
+         --ssl2 \
+         --user2 my_email@gmail.com \
+         --password2 gmailsecret \
+         --maxbytespersecond 20_000 \
+         --maxbytesafter 1_000_000_000 \
+         --automap    \
+         --expunge1   \
+         --addheader  \
+         --maxsleep 2 \
+         --exclude "\[Gmail\]$"  \
+         --regextrans2 's,\[Gmail\].,,' \
+         --regextrans2 's,^ +| +$,,g'
+         --regextrans2 's,/ +| +/,/,g'
+         --regextrans2 's/['"'"'\\^"]/_/g'
+         --folderlast  "[Gmail]/All Mail"
+
+
+Starting from imapsync 1.926 a --regextrans2 replacing 
+all blanks, was:
+
+        --regextrans2 "s/[ ]+/_/g" 
+
+With --gmail2 you can override the parameters
+that are activated by them, for example:
+
+imapsync ... --gmail2 --maxbytespersecond 50_000 --noautomap --maxsleep 0
+
+Explanations:
+
+--maxbytespersecond 20_000 ( 20 kBytes/s ) option is here to avoid 
+locking or errors when imap transfers exceed Gmail maximum limit. 
+See http://support.google.com/a/bin/answer.py?hl=en&answer=1071518
+--maxbytespersecond 20_000 is not mandatory in the sense Gmail may 
+allow you to use an upper value than 1 GBytes per 24h without 
+disconnections. If you count well, it should be 10_000, not 20_000.
+
+--maxbytesafter 1_000_000_000 option is there because 
+option --maxbytespersecond 20000 is unnecessarily slow if the Gmail 
+account size is less than 1 GB. Counting well, it should 
+be 500_000_000, not 1_000_000_000, but 1GB is usually ok.
+
+--maxsleep 2 is to avoid sleeping more than 2 seconds when 
+the --maxbytespersecond value implies a long sleep between 2 copies.
+
+--maxsize 25_000_000 is mandatory since Gmail limits messages size
+up to 25 MB. This value increases over time, it was 10 MB some 
+years ago so you can try higher values. The Gmail page about
+this limit is https://support.google.com/mail/answer/6584
+
+--automap is optional but it will save manual folder names
+changes or the use of --regextrans2 or --f1f2 to map folder names.
+
+--expunge1 is optional. It deletes messages marked \Deleted on host1.
+Imapsync syncs messages with all their flags, Gmail takes the messages
+marked \Deleted but deletes or moves them just after.
+Option --expunge1 really removes messages marked \Deleted on host1 
+so they are not synced at all.
+
+
+The --addheader option is there because "Sent" folder messages 
+sometimes lack the "Message-Id:" and "Received:" headers needed 
+by imapsync to identify messages (only when --useuid is not used). 
+So option --addheader adds a "Message-Id" header consisting of
+the imap UID of the message on the host1 folder, like
+"Message-Id: 12345@imapsync".
+
+--exclude "\[Gmail\]$" is there to avoid a small examine/select error:
+"Could not examine: 43 NO [NONEXISTENT] Unknown Mailbox: [Gmail] 
+(now in authenticated state) (Failure)".
+
+--regextrans2 "s/[ ]+/_/g" is there to convert blank characters not 
+accepted by gmail to character _ underscore. In fact only leading
+and trailing blank characters are problems with gmail, and
+also successive blanks ending with the IMAP error 
+"NO [CANNOT] Folder contains excess whitespace (Failure)"
+If you want to change only leading and trailing blank characters
+then use the following instead
+On Linux/Unix:
+  --regextrans2 "s,(/|^) +,\$1,g" --regextrans2 "s, +(/|$),\$1,g"
+On Windows:
+  --regextrans2 "s,(/|^) +,$1,g" --regextrans2 "s, +(/|$),$1,g"
+
+
+--regextrans2 "s/[\^]/_/g" is mandatory.  It converts, since
+not accepted by gmail, character ^ to character _ underscore.
+
+--regextrans2 "s/['\"\\\\]/_/g" is optional. It converts 
+characters ' or " or \ to character _ underscore.
+
+You can select folders exported to imap within the gmail preferences.
+Select or unselect some "System labels", depending on your needs.
+
+
+https://imapsync.lamiral.info/FAQ.d/FAQ.Gmail.txt
+=======================================================================
+Q. How to synchronize from Gmail to XXX?
+
+R. Use this example:
+
+imapsync \
+           --user1 foo@gmail.com \
+           --password1 gmailsecret \
+           --host2 localhost \
+           --user2 tata \
+           --gmail1
+
+Or, replacing what does --gmail1 (values are from imapsync 1.970):
+
+imapsync \
+           --host1 imap.gmail.com \
+           --ssl1 \
+           --user1 foo@gmail.com \
+           --password1 gmailsecret \
+           --host2 localhost \
+           --user2 tata \
+           --password2 tatasecret \
+           --maxbytespersecond 40_000 \
+           --maxbytesafter 2_500_000_000
+           --automap \
+           --maxsleep 2 \
+           --skipcrossduplicates \
+           --useheader="X-Gmail-Received" \
+           --useheader "Message-Id" \
+           --regextrans2 "s,\[Gmail\].,," \
+           --folderlast  "[Gmail]/All Mail"
+
+With --gmail1 you can override the parameters
+that are activated by them, for example:
+
+imapsync ... --gmail1 --maxbytespersecond 50_000 --noskipcrossduplicates --noautomap
+
+Explanations:
+
+--maxbytespersecond 40_000 ( 40 kBytes/s ) option is here to avoid 
+locking or errors when imap transfers exceed Gmail maximum limit. 
+See http://support.google.com/a/bin/answer.py?hl=en&answer=1071518
+--maxbytespersecond 40_000 is not mandatory in the sense Gmail may 
+allow you to use an upper value than 2 GBytes per 24h without 
+disconnections.
+
+--useheader="X-Gmail-Received" --useheader "Message-Id" are not
+mandatory. I use them because I found (several years ago, it may
+have changed) that Gmail always adds a different header 
+"X-Gmail-Received:" to all messages it gets. So the identification
+by imapsync can not fail using this header. "Message-Id" is there
+for safety about this Gmail rule.
+
+--automap is optional but it will save manual folder names
+changes or the use of --regextrans2 to map folder names.
+
+--regextrans2 "s,\[Gmail\].,,"
+If your destination imap server doesn't like "[Gmail]" name, 
+get rid of this "[Gmail]" part with that.
+
+You can select folders exported to imap within the gmail preferences,
+for example you may unselect all "System labels".
+
+--skipcrossduplicates is optional but it can save Gigabytes of hard
+disk memory. Within imap protocol, Gmail presents Gmail labels as 
+folders, so a message labeled "Work" "ProjectX" "Urgent" ends up 
+in three different imap folders "Work" "ProjectX" and "Urgent"
+after an imap sync. Option --skipcrossduplicates prevent this behavior.
+
+An issue with --skipcrossduplicates is that the first label synced
+by imapsync goes to its corresponding folder but other labels are
+then ignored. You can choose what labels have the 
+priority by using the --folderfirst option. For example
+--folderfirst "Work" will sync messages labeled "Work" before
+messages labeled "CanWait" or "Urgent". By default imapsync 
+syncs folders (Gmail labels) using the classical alphanumeric order.
+
+--folderlast "CanWait" will sync only messages that have the
+label CanWait and only it.
+
+--folderlast "[Gmail]/All Mail", in conjunction with option 
+--skipcrossduplicates, will only put in "[Gmail]/All Mail"
+the messages that are not labeled at all.
+
+
+https://imapsync.lamiral.info/FAQ.d/FAQ.Gmail.txt
+=======================================================================
+Q. I can't authenticate with Gmail via IMAP
+   and Gmail says "Please log in via your web browser"
+
+R0. My current settings on two Gmail accounts are made
+with three steps 0) 1) 2)
+
+0) Login via a web browser to the Gmail account concerned.
+
+1) The 2-step verification is OFF
+https://myaccount.google.com/security?hl=en&pli=1&nlr=1#signin
+
+2) Access for less secure apps is turned ON
+https://www.google.com/settings/security/lesssecureapps
+https://support.google.com/accounts/answer/6010255?hl=en
+
+R1. See Coert Grobbelaar solution:
+https://web.archive.org/web/20150906230041/http://security.stackexchange.com/questions/86404/how-do-i-interact-with-google-to-import-email-via-imapsync
+
+R2. I had the same issue one time (mars 2015) logging to Gmail 
+with imapsync.
+The Gmail imap message error said "Please log in via your web browser"
+so I logged for this account via a web browser. Then,
+it asked me to receive a code via a mobile, I said yes,
+I entered the code and everything went ok on next syncs
+with imapsync. 
+
+
+=======================================================================
+Q. Can not open imap connection on [imap.gmail.com]: 
+   Unable to connect to imap.gmail.com
+
+R0. It looks like this issue is related to ipv6. Both ipv4 and ipv6 
+protocols should work with gmail and imapsync, I test that regularly, 
+imapsync works fine for both ipv4 and ipv6. 
+If you disable ipv6 then disable also ipv6 resolution! 
+
+The default names resolution order is to present ipv6 name resolutions 
+first. If you know how to make ipv4 answers be taken before ipv6 
+then tell me.
+
+R1. First solution, run imapsync with the option --inet4:
+
+   imapsync ... --inet4
+
+R2. A second solution is to use directly gmail ipv4 ip address:
+
+  imapsync ... --host1 64.233.184.108 
+
+In case it changes, get it with any command showing the imap.gmail.com 
+name resolution, try one of those:
+
+  nslookup imap.gmail.com
+  host     imap.gmail.com
+  ping     imap.gmail.com
+
+Or go to http://ping.eu/nslookup/ to get the resolution.
+
+Thanks to Chris Nolan to report, understand and fix this issue!
+
+=======================================================================
+Q. Can I transfer "Chat" messages with imapsync?
+
+R. No. 
+   Even if you think you can because the Chat folder is seen in IMAP,
+   with Chat messages in them, they won't be well transferred.
+   Chat messages are not well presented and not well transferred 
+   using the IMAP protocol.
+
+=======================================================================
+Q. Can I safely use --useuid or --usecache for Gmail transfers?
+
+R. Yes, but I suggest to not use --useuid nor --usecache 
+   for Gmail transfers.
+
+Using UIDs is useless with Gmail in the case of global duplicates
+(duplicates across different folders). Gmail always accept a global
+duplicate message as a new message, giving imapsync a new UID for this
+message, and throw it away because it already has it. Gmail
+will do this at each run so imapsync will always try to copy the
+message, and Gmail will always accept and throw away the new copy. It
+ends up with no duplicates on Gmail but a waste of bandwidth and time,
+which is the opposite goal of --usecache implied by --useuid.
+
+
+======================================================================= 
+Q. Gmail does not really delete messages in folder [Gmail]/All Mail 
+   What happens? What can I do? 
+
+R. It's true and explained in Gmail documentation at
+https://support.google.com/mail/answer/7401?hl=en
+
+To really remove messages in folder "[Gmail]/All Mail", they have to
+be moved to the "Trash" folder and be deleted from "Trash".
+
+Quoting the link above (25 december 2018, happy christmas by the way!)
+...
+Empty your Trash
+If you don't want a message to stay in your Trash for 30 days, 
+you can permanently delete it.
+* On your computer, go to Gmail.
+* On the left side of the page, scroll down, 
+  then click More and then Trash.
+* Check the box next to messages you want to permanently delete, 
+  then click Delete forever.
+
+* Note: The Delete forever option is only available in the Trash. 
+  You won’t be able to delete items forever from the Search result view.
+  To delete all messages in your trash, click Empty Trash now.
+
+
+=======================================================================
+Q. Can I use the Extension of the SEARCH command: X-GM-RAW described at
+   https://support.google.com/mail/answer/7190?hl=en
+   https://developers.google.com/gmail/imap_extensions#extension_of_the_search_command_x-gm-raw
+
+R. Sure. Example, to search only emails with attachment and in unread state:
+
+On Unix:
+
+  imapsync ... --search 'X-GM-RAW "has:attachment in:unread"'
+
+On Windows:
+
+  perl imapsync ... --search "X-GM-RAW ""has:attachment in:unread"""
+
+
+=======================================================================
+Q. How to avoid the [IMAP] prefix on Gmail side?
+How to stop creating folder with this prefix?
+Any switch we can use? e.g. [IMAP]/Archive
+
+R. No switch in imapsync since [IMAP]/ prefix is done by Gmail,
+   it might be configurable within Gmail parameters configuration.
+
+
+=======================================================================
+Q. Does imapsync have the capability to do 2 stage authentication?
+
+R. No, imapsync doesn't support 2 stage authentication. 
+Reading https://support.google.com/mail/answer/1173270?hl=en
+it looks like it can't because imapsync uses imap protocol.
+
+So you have to follow the Google recommendation and generate an 
+application-specific password or normal authentication 
+or use XOAUTH or XOAUTH2.
+
+
+=======================================================================
+Q. How to use XOAUTH2 to globally authenticate gmail users?
+
+R. Yes, but really tested on Unix systems, not sure on Windows. See:
+   http://imapsync.lamiral.info/FAQ.d/FAQ.XOAUTH2.txt
+
+
+=======================================================================
+Q. How to use XOAUTH to globally authenticate gmail users?
+
+R0. XOAUTH is considered obsolete and superseded by XOAUTH2
+    See http://imapsync.lamiral.info/FAQ.d/FAQ.XOAUTH2.txt
+
+
+=======================================================================
+Q. How to use a Gmail account to backup several different imap accounts?
+
+R. For each account named xxx use:
+
+  imapsync ... --subfolder2 xxx/xxx
+
+It syncs the account xxx under a sub-subfolder xxx/xxx. This way there
+is no supplementary label created on the multi-archive Gmail 
+destination account. No labels all over the place and all original
+xxx sub-folders show up nested within xxx/xxx.
+
+
+=======================================================================
+Q. How to migrate email from gmail to google apps?
+
+R. Take a look at:
+
+http://biasecurities.com/2009/02/migrate-email-from-gmail-to-google-apps/
+http://www.thamtech.com/blog/2008/03/29/gmail-to-google-apps-email-migration/
+
+=======================================================================
+=======================================================================

FAQ.d/FAQ.ISP.txt

@@ -0,0 +1,126 @@
+#!/bin/cat
+$Id: FAQ.ISP.txt,v 1.9 2018/05/24 11:34:30 gilles Exp gilles $
+
+This document is also available online at
+https://imapsync.lamiral.info/FAQ.d/
+https://imapsync.lamiral.info/FAQ.d/FAQ.ISP.txt
+
+=======================================================================
+      Imapsync tips for ISP. Specific issues and solutions.
+=======================================================================
+
+* IMAPSync - usage scenario with ISP - by Flávio Zarur Lucarelli.
+
+I thought Id write a quick step by step on my attempts to learn the
+imapsync features that matter the most, so it works as we expected in
+the cenario in which we use it, which is to migrate customers from
+their old ISP to our ISP/email hosting. Thanks to the master Gilles
+Lamiral for all his help and hard work.
+
+First of all, remember to use --dry to test things first always and
+check the log file to see what would actually happen.
+
+Initially, I used a method where I'd do an exact sync of source to
+destination, deleting messages which were in destination, but not
+source. I call this "Method 2", below. In this cenario, customer
+shouldn't be using the destination account yet. Then, after I switch MX,
+I'd do a final sync based on date. The big advantage of this is, you
+get an exact sync.
+
+Easier, however, is method 1, where I sync based on message ID, this
+way, I can use the same syntax before and after MX change, with no
+worries. Only disadvantage, you might not get an exact sync, there
+might be some difference in terms of total emails in folders, due to
+duplicates, emails that had same message ID in source server.
+
+* Method 1 - sync based on message ID, can use same syntax before and
+  after MX change
+
+  imapsync --host1 imap.myisp.com --user1 user@domain.com --password1 pwd \
+           --host2 imap.myisp.com --user2 user@domain.com --password2 pwd \
+		   --addheader
+
+Note: add header adds message ID when it doesn't exist.
+
+This syntax can also be used to sync different source accounts to one
+same destination account, simply execute it as many times as desired,
+switching source user (user1).
+
+* Method 2 - exact sync source do destination, then sync based on date
+  after MX change
+
+My first goal is to have an exact sync of an account from
+current/source host to the new/destination host and be able to sync
+several times. The --useuid parameter is very important for that
+purpose. This is what I use:
+
+  imapsync --host1 imap.gmail.com --user1 user@domain.com --password1 pwd --ssl1 \
+           --host2 imap.myisp.com --user2 user@domain.com --password2 pwd --ssl2 \
+		   --useuid --delete2 --delete2folders 
+
+This makes it so imap.myisp.com (destination) is an exact copy of the
+account at imap.gmail.com (source). This is not a problem, since the
+user is not using the new host yet. ]You can check Imapsync log files
+and surely you will see the final difference should be 0. Check also
+for any possible errors in the log (search for "error").
+
+The second goal is to lower the TTL (ex: 5 min) for the host
+associated with the MX record, in the domain's DNS server. Let's say
+customer has a host mail which his MX points to, with a high TTL
+(usually 1 hour). Lower it to 5 min so that, when you change the MX,
+it propagates faster.
+
+When comes time to switch over to the new host, do a final sync with
+above syntax, before changing the MX. Then, change the MX and tell
+your users to start using exclusively the new host.
+
+A few hours after the MX change, we will run Imapsync again. We have
+to start preserving emails users move or flag in the new host, which
+they started using, so we can't do an exact sync anymore.
+
+The best solution for me was to Sync any new emails (maxage:1) from
+source (that could arrive in source even after MX change, due to
+cache) and delete such emails from source server. This way, customer's
+mailbox is still intact on the source server, except new emails, which
+get synced to new server and deleted from source.
+
+  imapsync --host1 imap.gmail.com --user1 user@domain.com --password1 pwd --ssl1 \
+           --host2 imap.myisp.com --user2 user@domain.com --password2 pwd --ssl2 \
+           --folder INBOX --useuid --noexpungeaftereach --skipemptyfolders --maxage 1 --delete1
+
+I personally prefer to keep a copy of users box intact in source, but
+if that's not an issue for you, you can remove --folder INBOX and even
+--maxage, but then, all emails in source will be deleted. You can use
+--maxage 1 with --delete1, however, for all folder (without specifying
+--folder INBOX), so only any new email that arrives at source is
+copied to destination and deleted from source.
+
+My next goal was to automate the process, so I followed this advice:
+http://imapsync.lamiral.info/examples/sync_loop_unix.sh
+
+I also ended up requiring a regex to translate folder names. On the
+old server (Gmail), Sent items were in a folder called [Gmail]/E-mails
+enviados and on the new server, its simply called SENT. Same with
+lixeira (trash) and rascunhos (drafts).
+
+So this was added:
+
+  --regextrans2 "s,\[Gmail\].,," \
+  --regextrans2 "s,E-mails enviados,Sent," \
+  --regextrans2 "s,Lixeira,Trash," \
+  --regextrans2 "s,Rascunhos,Drafts,"
+
+*** Other cenarios
+
+- Sync entire account into 1 folder of another account
+
+  imapsync --host1 xxx --user1 user1@domain.com --password1 secret1 --ssl1 \
+           --host2 yyy --user2 user2@domain.com --password2 secret2 --ssl2 \
+		   --useuid --subfolder2 otheraccountfolder --delete2 --delete2foldersonly /otheraccountfolder/
+
+Above is based on message UID, advantage of no dupes, however, user
+must not be using such destination folder in destination account until
+you finish syncing.
+
+=======================================================================
+=======================================================================

FAQ.d/FAQ.Kerio.txt

@@ -0,0 +1,46 @@
+#!/bin/cat
+$Id: FAQ.Kerio.txt,v 1.2 2019/11/15 11:33:14 gilles Exp gilles $
+
+This document is also available online at
+https://imapsync.lamiral.info/FAQ.d/
+https://imapsync.lamiral.info/FAQ.d/FAQ.Kerio.txt
+
+=======================================================================
+              Imapsync tips for Kerio accounts.
+=======================================================================
+
+
+
+
+=======================================================================
+Q. How to migrate from Kerio Connect to XXX
+
+R. No special options required. 
+See also:
+http://www.linux-france.org/prj/imapsync_list/msg01756.html
+http://web.archive.org/web/20140224041102/https://www.safetynet-it.com/it-support/mac-kerio-server-to-microsoft-exchange-2010-migration-1/
+http://web.archive.org/web/20121125074756/http://www.safetynet-it.com/it-support/mac-kerio-server-to-microsoft-exchange-2010-migration-2/
+
+=======================================================================
+Q. How to use Kerio master authentication with imapsync?
+
+R. Example:
+
+Kerio at host1
+
+  imapsync ... --user1 USERNAME --password1 MASTERPASSWORD --authmech1 X-MASTERAUTH 
+
+Kerio at host2
+
+  imapsync ... --user2 USERNAME --password2 MASTERPASSWORD --authmech2 X-MASTERAUTH 
+  
+See also:
+https://github.com/imapsync/imapsync/pull/53
+
+If you get the error
+"Host failure: Error login on ... auth [X-MASTERAUTH]: 2 BAD AUTHENTICATE Unknown authentication method"
+
+Then admin authentication may not be activated yet. See:
+https://forums.gfi.com/index.php?t=msg&th=28458&goto=118447&#msg_118447
+
+=======================================================================

FAQ.d/FAQ.Massive.txt

@@ -0,0 +1,338 @@
+#!/bin/cat
+$Id: FAQ.Massive.txt,v 1.30 2019/07/24 12:01:41 gilles Exp gilles $
+
+This document is also available online at
+https://imapsync.lamiral.info/FAQ.d/
+https://imapsync.lamiral.info/FAQ.d/FAQ.Massive.txt
+
+
+=======================================================================
+              Imapsync tips for massive/bulk migrations.
+=======================================================================
+
+Questions answered here are:
+
+Q. How long will take the whole migration?
+
+Q. I need to migrate hundred accounts, how can I do?
+
+Q. I have to migrate 500k users using 400 TB of disk space. 
+   How do I proceed? How about speed?
+
+Q. How to determine where is the bottleneck in an imapsync process?
+
+Q. Can I run several instances of imapsync in parallel on a Windows host?
+
+Q. I run multiple imapsync applications at the same time then get a
+   warning "imapsync.pid already exists, overwriting it".
+   Is this a potential problem when trying to sync multiple 
+   IMAP account in parallel?
+
+=======================================================================
+Q. How long will take the whole migration? 
+
+R1. First you have to consider several periods. There is the global 
+    period, from when the migration process is decided to the final end
+    where all mailboxes are migrated. This global period can be divided
+    into three smaller periods.
+    
+    The first period is the analyse period: you play with the tools 
+    available, you estimate the volume to be transferred, the number of
+    accounts, you measure how long it takes for one account under
+    your context.
+    
+    The second period is the presync period. The users are still using
+    the old accounts but nothing prevents you from starting to sync
+    the old accounts, as they are, to the new accounts.
+    With tons of gigabytes to transfer, this period may be the longest one. 
+    There is nothing more than launching the presyncs and monitoring them 
+    until the round is finished.
+    
+    The last period is the final sync period where only the last 
+    changes of the mailboxes need to be synced in order to switch
+    the users to their new mailboxes.
+
+R2. To estimate the presync period, consider the mean imapsync transfer
+    rate to be around 340 Kbytes/s, ie, 2.8 Mbps, no matter the local 
+    link bandwidth.
+    It's a mean, measured upon various different syncs, coming from 
+    the online service /X where the network card flow rate is 100 Mbps 
+    and the provider bandwidth is also 100 Mbps. Max seen is a transfer 
+    at 21 Mbps.
+   
+    At 340 Kbytes/s,
+    1 TB to transfer and one sync at a time will end in 35 days (1024^3/340/3600/24).
+    At  10 transfers at a time, 1 TB will take 3.5 days.
+    At 100 transfers at a time, 1 TB will take 8 hours.
+    Double the time because the best scenario never happens.
+    Triple the time because, well, real world is like that.
+
+R3. To estimate the last period, just rerun a complete presync,
+    ie, resync all the mailboxes, the final sync should take 
+    the same amount of time.
+    
+=======================================================================
+Q. I need to migrate hundred accounts, how can I do?
+
+R. If you have many mailboxes to migrate, think about a little
+script program. Write a file called file.txt (for example)
+containing hosts, users and passwords on both sides.
+The separator used in this example is ";"
+
+The file.txt file contains for example:
+
+host001_1;user001_1;password001_1;host001_2;user001_2;password001_2;
+host002_1;user002_1;password002_1;host002_2;user002_2;password002_2;
+host003_1;user003_1;password003_1;host003_2;user003_2;password003_2;
+host004_1;user004_1;password004_1;host004_2;user004_2;password004_2;
+etc.
+
+Most of the times, the first column (host001_1, host002_1 ...) will
+contains the same value, the value of --host1 parameter. Same
+thing for the third column (host001_2, host002_2).
+
+On Unix the shell script can be:
+
+#!/bin/sh
+{ while IFS=';' read  h1 u1 p1 h2 u2 p2 fake
+    do 
+        imapsync --host1 "$h1" --user1 "$u1" --password1 "$p1" \
+                 --host2 "$h2" --user2 "$u2" --password2 "$p2" "$@" 
+    done 
+} < file.txt
+
+You can add extra options inside this script, just after the variable "$@".
+You can also pass extra options via the parameters of this script 
+since they will go in "$@"
+
+Here is a complete Unix example ready to use: 
+http://imapsync.lamiral.info/examples/sync_loop_unix.sh
+
+
+On Windows the batch script can be:
+
+CD /D %~dp0
+SET csvfile=file.txt
+FOR /F "tokens=1,2,3,4,5,6,7 delims=; eol=#" %%G IN (%csvfile%) DO (
+imapsync ^
+  --host1 %%G --user1 %%H --password1 %%I ^
+  --host2 %%J --user2 %%K --password2 %%L %%M  ...
+)
+
+You can add extra options inside this script, just after the variable %%M.
+You can add extra options inside the file.txt, in the last column. Add 
+an extra semicolon at the end (optional)
+Example:
+host001_1;user001_1;password001_1;host001_2;user001_2;password001_2;
+host002_1;user002_1;password002_1;host002_2;user002_2;password002_2;
+becomes
+host001_1;user001_1;password001_1;host001_2;user001_2;password001_2; --automap --addheader
+host002_1;user002_1;password002_1;host002_2;user002_2;password002_2; --automap --addheader
+
+With this solution, options can be added, changed or removed per account.
+Technically those options will go in %%M in the loop body 
+
+Here is a complete Windows example ready to use: 
+http://imapsync.lamiral.info/examples/sync_loop_windows.bat
+
+Another solution to add extra arguments is to write another .bat that 
+calls sync_loop_windows.bat with the extra arguments, like this
+for example:
+
+  sync_loop_windows.bat --automap --addheader --maxmessagespersecond 4 
+
+Technically those options will go in %arguments%  in the loop body
+of sync_loop_windows.bat
+
+
+=======================================================================
+Q. I have to migrate 500k users using 400 TB of disk space. 
+   How do I proceed? How about speed?
+
+R. A good solution to this issue is two words: parallelism and measurements.  
+
+Since all mailboxes are functionnaly independent, they can be processed 
+independently, here comes the parallelism, ie, lunching several imapsync 
+processes in parallel.
+
+Meanwhile, mailboxes usually belong to the same server and the syncs
+share the same imapsync host via the same bandwidth, here come 
+some limitations and bottlenecks.
+
+How many syncs can we run in parallel in your context?
+Here comes some measurements.
+
+1) Measure the total transfer rate by adding each one printed in each run.
+   Since adding this way is not so easy, just look at the overall 
+   network rate of the imapsync host.
+
+   On Linux and FreeBSD, nload is a good candidate to measure this overall
+   network rate. For example, to measure the rate every 6 seconds (-t 6000), 
+   on eth0 or em0 interface, with values in Kbytes (-u K), use:
+   
+     nload -t 6000 eth0 -u K  # Linux
+     nload -t 6000 em0  -u K  # FreeBSD
+
+   On Linux only, another very good network tool is dstat:
+   
+     dstat -n -N eth0 6  # Linux only (in 2018)
+
+   Another excellent tool to measure the network trafic is iftop.
+   The following command will monitor imap and imaps connections
+   on interfce eth0, only them, and sum them up:
+   
+     iftop -i eth0 -f 'port imap or port imaps' -B # Linux
+     iftop -i em0  -f 'port imap or port imaps' -B # FreeBSD
+
+   During iftop, press the h to see the display commands available, 
+   every single feature is useful! Press h again and try each one.
+   My preferred display combination is by typing
+   t p >  
+   meaning: one line per connection, show port numbers, sort by destination.
+
+
+   On Windows 8.1 Windows 10 Windows 2012 R2 Windows 2016,
+   get the overall network rate with the classical
+   task manager (Ctrl-Shift-Esc), there is a Performance tab
+   in it where resides a Network grap monitor.
+
+   On Windows 7, get the overall network rate with the classical
+   task manager (Ctrl-Shift-Esc), there is a Network tab in it.
+
+   I'm looking for a free and simple tool on Windows that could 
+   sum up only the imap traffic.
+
+2) Launch new parallel runs, one by one, as long as the total 
+   transfer rate increase.
+
+3) When the total transfer rate starts to diminish, stop new launches. 
+   Note N as the number of parallel runs you got until then.
+
+4) Only keep N-2 parallel runs for the future.
+
+
+=======================================================================
+Q. How to determine where is the bottleneck in an imapsync process?
+
+R1. Divide and conquer.
+
+In order to detect whether host1/link1 is the bottleneck or
+host2/link2, we have several tests to explore:
+
+1) run a sync from host1 to host1, with a host1 test account as destination.
+This way, only host1+link1 are tested, host2 is not directly concerned.
+If performances increase a lot then host2/link2 is the bottleneck.
+
+2) run a sync from host2 to host2, with a host2 test account as destination.
+This way, only host2+link2 are tested, host1 is not concerned.
+If performances increase a lot then host1/link1 is the bottleneck.
+
+If performances increase on both tests 1) and 2), I have no clue to explain that.
+Same thing if they both decrease! 
+
+R2. Isolating and overcoming bottlenecks
+
+On any process involving several mechanisms, among all elements taking
+part on the process, there is always a bottleneck.  No one knows in
+advance what is the first bottleneck. The first bottleneck has to be
+determined, by measurements, not by guesses.  Once this first
+bottleneck is known and overcome then the next bottleneck has to be
+determined and overcome too, if needed. Repeat the process of looking
+for the next bottleneck and its elimination until you estimate the
+transfer rates, money costs, time spent on this, and final dates 
+are good enough to proceed the whole huge migration.
+
+Possible bottlenecks: 
+
+- Throttles. 
+  IMAP servers have artificial limits. 
+  For example Gmail, Office365, Exchange have throttle limits.
+
+- Bandwidth. 
+  Usually available bandwidth is NOT a bottleneck.
+  Meanwhile, it can be a bottleneck on small Internet connections.
+  Imapsync downloads messages from host1 and upload messages to host2,
+  consider this in case the connections are asymmetric.
+  
+- I/O on disks. 
+  I/O are a classical bottleneck, almost always forgotten.
+  Unlike CPU and RAM, Input/Output performances don't improve
+  very much as time goes on so it's often a bottleneck.
+  To measure and overcome an I/O disk bottleneck, you need 
+  usually a direct access to host1 and host2.
+  An I/O bottleneck where imapsync runs is possible if
+  --usecache or --useuid is used or with very big messages.
+
+
+- RAM memory.
+  On all sides, monitor that your systems don't swap its 
+  running processes on disk, because swapping running processes 
+  on disks decreases performance by a factor of 20, at least.
+  It's not because the swap memory is used that your
+  system swaps processes on disk.
+
+- CPU.
+  100% CPU during a whole transfer means the system is busy.
+  Usually CPU is not a problem with imapsync but it can be a problem
+  with one of the imap servers.
+  Most often CPU is not the real bottleneck, I/O are.
+
+Other possible bottlenecks:
+- Number of hosts available to run imapsync processes.
+- Imapsync itself.
+- Management of errors.
+- MX domains, DNS.
+- Incompetence.
+- Money.
+- Time.
+- Bad luck.
+- ...
+
+
+=======================================================================
+Q. Can I run several instances of imapsync in parallel on a Windows host?
+
+R. Yes!
+
+Q. Any performance issue?
+
+You have to try and check the transfer rates, sum them up to
+have a uniq numeric criteria. 
+There is always a limit, depending on remote imap servers 
+and the one running imapsync.
+CPU, memory, Inputs/Outputs are the classical bottlenecks, 
+the worst bottleneck is the winner that sets the limit.
+
+examples/sync_loop_windows.bat says
+...
+REM ==== Parallel executions ====
+REM If you want to do parallel runs of imapsync then this current script is a good start.
+REM Just copy it several times and replace, on each copy, the csvfile variable value.
+REM Instead of SET csvfile=file.txt write for example
+REM SET csvfile=file01.txt in the first copy
+REM then also 
+REM SET csvfile=file02.txt in the second copy etc.
+REM Of course you also have to split the data contained in file.txt
+REM into file01.txt file02.txt etc.
+REM After that, just double-click on each batch file to launch each process
+
+
+=======================================================================
+Q. I run multiple imapsync applications at the same time then get a
+   warning "imapsync.pid already exists, overwriting it".
+   Is this a potential problem when trying to sync multiple 
+   IMAP account in parallel?
+
+R1. No issue with the file imapsync.pid if you don't use its content
+by yourself. 
+
+This file can help you to manage multiple runs by sending signals 
+to the processes (sigterm or sigkill) using their PID.
+Each run can have its own pid file with --pidfile option.
+The file imapsync.pid contains the PID of the current imapsync process.
+This file is removed at the end of a normal run.
+You can safely ignore the warning if you don't use imapsync.pid file
+to manage imapsync processes.
+
+=======================================================================
+=======================================================================

FAQ.d/FAQ.Memory.txt

@@ -0,0 +1,69 @@
+#!/bin/cat
+$Id: FAQ.Memory.txt,v 1.8 2018/08/31 13:29:53 gilles Exp gilles $
+
+This document is also available online at
+https://imapsync.lamiral.info/FAQ.d/
+https://imapsync.lamiral.info/FAQ.d/FAQ.Memory.txt
+
+
+=======================================================================
+             Imapsync tips about memory issues.
+=======================================================================
+
+
+=======================================================================
+Q. I got an "Out of memory" error message then imapsync crashes.
+   How to fix that?
+
+R0. Add option --debugmemory to debug memory issues.
+    On Windows this option uses a DOS command similar to:
+
+        tasklist /NH /FO CSV | findstr imapsync
+
+    On Unix it uses:
+    
+        ps -o vsz -p PID_of_imapsync  # value is in KB
+
+    Similar to:
+    
+        ps -ax -o vsz,comm | grep imapsync
+
+    Use those commands in a DOS window or a Unix shell in order
+    to monitor a imapsync run you know it will crash. 
+    The goal is to detect the memory limit, when and how it happens.
+    
+    * Is the "final" amount near the total RAM available or 
+      just a small part of it?
+    * Does the rise of memory consumption happens suddenly 
+      or along the sync?
+
+R1. It's probably a very big message on the host1 account.
+   Before imapsync release 1.688 memory usage is at least 5 times 
+   the biggest message size. then 2 times with release 1.688.
+   So a 700 MB message will crunch 3.5 GB of memory.
+   Starting with 1.688 it  will crunch 1.4 GB of memory.
+
+R2. To check if the problem is a big message crunching to much 
+   memory, add --maxsize 50_000_000, this will limit the message
+   size treated to 50 MB. If the sync succeed while limiting 
+   messages sizes it's probably is a big message crunching to much
+   memory issue. Possible solutions:
+   * Try on another host
+   * Buy memory
+   * Build imapsync.exe binary 64bits
+
+R3. If R2 shows that the memory issue is not a big message crunching 
+    too much memory, then it can be imapsync using too much memory
+    to identify messages (a very big folder served by a
+    very talkative imap server). A possible solution is to use
+    the option --useuid. If it still fails, I have no clue.
+    If you have time, drop me a note.
+
+R4. Usually "Out of memory" errors are related to old days,
+   to old Mail::IMAPClient module releases, before 3.26.
+   At that time memory usage was around 17 times the biggest message.
+   Look at imapsync output first lines to get the Mail::IMAPClient 
+   release used. Then upgrade Mail::IMAPClient Perl module if needed.
+
+=======================================================================
+=======================================================================

FAQ.d/FAQ.Messages_Selection.txt

@@ -0,0 +1,418 @@
+#!/bin/cat
+$Id: FAQ.Messages_Selection.txt,v 1.15 2019/07/24 12:02:11 gilles Exp gilles $
+
+This document is also available online at
+https://imapsync.lamiral.info/FAQ.d/
+https://imapsync.lamiral.info/FAQ.d/FAQ.Messages_Selection.txt
+
+
+=======================================================================
+                Imapsync tips to select messages.
+=======================================================================
+
+Questions answered in this FAQ are:
+
+Q. What messages imapsync syncs by default?
+
+Q. Is there a way we can specify a date range to sync emails? 
+   If yes, can you please share an example?
+
+Q. Is there a way we can specify an age to sync emails? 
+   If yes, can you please share some examples?
+
+Q. I want to sync messages based on their UID.
+
+Q. Can I migrate only mails with attachments?
+
+Q. How can I move messages marked \Deleted from all folders to
+   a dedicated folder?
+
+Q. What are the selection criteria available with --search option?
+
+
+=======================================================================
+Q. What messages imapsync syncs by default?
+
+R. By default, Imapsync syncs all messages, except duplicates.
+
+=======================================================================
+Q. Is there a way we can specify a date range to sync emails? 
+   If yes, can you please share an example?
+
+R. Yes, a date range is possible with the --search option.
+
+  imapsync ... --search "SENTSINCE 1-Jan-2010" 
+  
+or 
+  
+  imapsync ... --search "SENTBEFORE 31-Dec-2010"
+
+or
+  
+  imapsync ... --search "SENTSINCE 1-Jan-2010 SENTBEFORE 31-Dec-2010"
+
+  Months are specified like this:
+  
+   Jan
+   Feb
+   Mar
+   Apr
+   May 
+   Jun
+   Jul 
+   Aug
+   Sep
+   Oct 
+   Nov
+   Dec
+
+=======================================================================
+Q. Is there a way we can specify an age to sync emails? 
+   If yes, can you please share some examples?
+
+R. Yes, with the --maxage or the --minage option.
+
+E.1 Sync only messages less than 2 days old:
+
+  imapsync ... --maxage 2
+
+E.2 Sync only messages more than 2 days old:
+
+  imapsync ... --minage 2
+
+E.3 Sync only messages more than 30 days old and less than 365 days old:
+
+  imapsync ... --minage 30 --maxage 365
+
+E.4 Sync only messages less than 30 days old or more than 365 days old:
+
+  imapsync ... --maxage 30 --minage 365
+
+Full explanation:
+
+--maxage      <int>    : Skip messages older than <int> days.
+                         final stats (skipped) don't count older messages
+                         see also --minage
+--minage      <int>    : Skip messages newer than <int> days.
+                         final stats (skipped) don't count newer messages
+                         You can do (+ are the messages selected):
+                         past|----maxage+++++++++++++++>now
+                         past|+++++++++++++++minage---->now
+                         past|----maxage+++++minage---->now (intersection)
+                         past|++++minage-----maxage++++>now (union)
+
+C.1 By default,
+
+  option --maxage is implemented as a --search SENTSINCE 
+RFC 3501 says: SENTSINCE <date>
+Messages whose [RFC-2822] Date: header (disregarding time and
+timezone) is within or later than the specified date.
+
+  Option --minage is implemented as a --search SENTBEFORE
+RFC 3501 says: SENTBEFORE <date>
+Messages whose [RFC-2822] Date: header (disregarding time and
+timezone) is earlier than the specified date.
+
+If --noabletosearch is on then --minage and --maxage deal
+with the internal dates given by a FETCH imap command but 
+not the Date: header. Internal date is the arrival date 
+in the mailbox. Same remark for --noabletosearch1 and
+--noabletosearch2 but only for one side then.
+
+=======================================================================
+Q. I want to sync messages based on their UID.
+
+R. First have in mind that UIDs are unique only per folder, so work this
+   way only with one folder at a time, with --folder option.
+
+To show UIDs, there is the --debugLIST parameter.
+
+  imapsync ...  --debugLIST
+
+To sync only a part of all messages, selected by UIDs 
+from 10000 to 11000:
+
+  imapsync ... --search1 "UID 10000:11000" 
+
+To sync from INBOX only 3 messages UIDs 20000 20002 20004:
+
+  imapsync ... --search1 'OR OR UID 20000 UID 20002 UID 20004' --folder INBOX
+
+To sync all messages from INBOX except 3 messages 
+UIDs 20000 20002 20004:
+
+  imapsync ... --search1 'NOT OR OR UID 20000 UID 20002 UID 20004' --folder INBOX
+
+If you search n UIDs then you have to put n-1 OR in the search line,
+that's IMAP.
+
+=======================================================================
+Q. Can I migrate only mails with attachments?
+
+R. Use:
+
+  imapsync ... --search "HEADER Content-Type multipart/mixed" 
+
+or more generally:
+
+  imapsync ... --search "OR HEADER Content-Disposition attachment HEADER Content-Type multipart/mixed" 
+
+
+=======================================================================
+Q. How can I move messages marked \Deleted from all folders to
+   a dedicated folder?
+
+R. To move \Deleted messages from all folders to a specific folder, 
+   let's call it Trash, use:
+
+  imapsync ... --search DELETED --regextrans2 "s/.*/Trash/" 
+
+=======================================================================
+Q. What are the selection criteria available with --search option?
+
+R. The list of search criteria are listed below, an excerpt from RFC3501.
+
+
+https://tools.ietf.org/html/rfc3501#section-6.4.4
+...
+      The SEARCH command searches the mailbox for messages that match
+      the given searching criteria.  Searching criteria consist of one
+      or more search keys.  The untagged SEARCH response from the server
+      contains a listing of message sequence numbers corresponding to
+      those messages that match the searching criteria.
+      When multiple keys are specified, the result is the intersection
+      (AND function) of all the messages that match those keys.  For
+      example, the criteria DELETED FROM "SMITH" SINCE 1-Feb-1994 refers
+      to all deleted messages from Smith that were placed in the mailbox
+      since February 1, 1994.  A search key can also be a parenthesized
+      list of one or more search keys (e.g., for use with the OR and NOT
+      keys).
+
+      In all search keys that use strings, a message matches the key if
+      the string is a substring of the field.  The matching is
+      case-insensitive.
+
+      The defined search keys are as follows.  Refer to the Formal
+      Syntax section for the precise syntactic definitions of the
+      arguments.
+
+      <sequence set>
+         Messages with message sequence numbers corresponding to the
+         specified message sequence number set.
+
+      ALL
+         All messages in the mailbox; the default initial key for
+         ANDing.
+
+      ANSWERED
+         Messages with the \Answered flag set.
+
+      BCC <string>
+         Messages that contain the specified string in the envelope
+         structure's BCC field.
+
+      BEFORE <date>
+         Messages whose internal date (disregarding time and timezone)
+         is earlier than the specified date.
+
+      BODY <string>
+         Messages that contain the specified string in the body of the
+         message.
+
+      CC <string>
+         Messages that contain the specified string in the envelope
+         structure's CC field.
+
+      DELETED
+         Messages with the \Deleted flag set.
+
+      DRAFT
+         Messages with the \Draft flag set.
+
+      FLAGGED
+         Messages with the \Flagged flag set.
+
+      FROM <string>
+         Messages that contain the specified string in the envelope
+         structure's FROM field.
+
+      HEADER <field-name> <string>
+         Messages that have a header with the specified field-name (as
+         defined in [RFC-2822]) and that contains the specified string
+         in the text of the header (what comes after the colon).  If the
+         string to search is zero-length, this matches all messages that
+         have a header line with the specified field-name regardless of
+         the contents.
+
+      KEYWORD <flag>
+         Messages with the specified keyword flag set.
+
+      LARGER <n>
+         Messages with an [RFC-2822] size larger than the specified
+         number of octets.
+
+      NEW
+         Messages that have the \Recent flag set but not the \Seen flag.
+         This is functionally equivalent to "(RECENT UNSEEN)".
+
+      NOT <search-key>
+         Messages that do not match the specified search key.
+
+      OLD
+         Messages that do not have the \Recent flag set.  This is
+         functionally equivalent to "NOT RECENT" (as opposed to "NOT
+         NEW").
+
+      ON <date>
+         Messages whose internal date (disregarding time and timezone)
+         is within the specified date.
+
+      OR <search-key1> <search-key2>
+         Messages that match either search key.
+
+      RECENT
+         Messages that have the \Recent flag set.
+
+      SEEN
+         Messages that have the \Seen flag set.
+
+      SENTBEFORE <date>
+         Messages whose [RFC-2822] Date: header (disregarding time and
+         timezone) is earlier than the specified date.
+
+      SENTON <date>
+         Messages whose [RFC-2822] Date: header (disregarding time and
+         timezone) is within the specified date.
+
+      SENTSINCE <date>
+         Messages whose [RFC-2822] Date: header (disregarding time and
+         timezone) is within or later than the specified date.
+
+      SINCE <date>
+         Messages whose internal date (disregarding time and timezone)
+         is within or later than the specified date.
+
+      SMALLER <n>
+         Messages with an [RFC-2822] size smaller than the specified
+         number of octets.
+
+      SUBJECT <string>
+         Messages that contain the specified string in the envelope
+         structure's SUBJECT field.
+
+      TEXT <string>
+         Messages that contain the specified string in the header or
+         body of the message.
+
+      TO <string>
+         Messages that contain the specified string in the envelope
+         structure's TO field.
+
+      UID <sequence set>
+         Messages with unique identifiers corresponding to the specified
+         unique identifier set.  Sequence set ranges are permitted.
+
+      UNANSWERED
+         Messages that do not have the \Answered flag set.
+
+      UNDELETED
+         Messages that do not have the \Deleted flag set.
+
+      UNDRAFT
+         Messages that do not have the \Draft flag set.
+
+      UNFLAGGED
+         Messages that do not have the \Flagged flag set.
+
+      UNKEYWORD <flag>
+         Messages that do not have the specified keyword flag set.
+
+      UNSEEN
+         Messages that do not have the \Seen flag set. 
+
+...
+
+search          = "SEARCH" [SP "CHARSET" SP astring] 1*(SP search-key)
+                    ; CHARSET argument to MUST be registered with IANA
+...
+
+search-key      = "ALL" / "ANSWERED" / "BCC" SP astring /
+                  "BEFORE" SP date / "BODY" SP astring /
+                  "CC" SP astring / "DELETED" / "FLAGGED" /
+                  "FROM" SP astring / "KEYWORD" SP flag-keyword /
+                  "NEW" / "OLD" / "ON" SP date / "RECENT" / "SEEN" /
+                  "SINCE" SP date / "SUBJECT" SP astring /
+                  "TEXT" SP astring / "TO" SP astring /
+                  "UNANSWERED" / "UNDELETED" / "UNFLAGGED" /
+                  "UNKEYWORD" SP flag-keyword / "UNSEEN" /
+                    ; Above this line were in [IMAP2]
+                  "DRAFT" / "HEADER" SP header-fld-name SP astring /
+                  "LARGER" SP number / "NOT" SP search-key /
+                  "OR" SP search-key SP search-key /
+                  "SENTBEFORE" SP date / "SENTON" SP date /
+                  "SENTSINCE" SP date / "SMALLER" SP number /
+                  "UID" SP sequence-set / "UNDRAFT" / sequence-set /
+                  "(" search-key *(SP search-key) ")"
+
+seq-number      = nz-number / "*"
+                    ; message sequence number (COPY, FETCH, STORE
+                    ; commands) or unique identifier (UID COPY,
+                    ; UID FETCH, UID STORE commands).
+                    ; * represents the largest number in use.  In
+                    ; the case of message sequence numbers, it is
+                    ; the number of messages in a non-empty mailbox.
+                    ; In the case of unique identifiers, it is the
+                    ; unique identifier of the last message in the
+                    ; mailbox or, if the mailbox is empty, the
+                    ; mailbox's current UIDNEXT value.
+                    ; The server should respond with a tagged BAD
+                    ; response to a command that uses a message
+                    ; sequence number greater than the number of
+                    ; messages in the selected mailbox.  This
+                    ; includes "*" if the selected mailbox is empty.
+
+seq-range       = seq-number ":" seq-number
+                    ; two seq-number values and all values between
+                    ; these two regardless of order.
+                    ; Example: 2:4 and 4:2 are equivalent and indicate
+                    ; values 2, 3, and 4.
+                    ; Example: a unique identifier sequence range of
+                    ; 3291:* includes the UID of the last message in
+                    ; the mailbox, even if that value is less than 3291.
+
+sequence-set    = (seq-number / seq-range) *("," sequence-set)
+                    ; set of seq-number values, regardless of order.
+                    ; Servers MAY coalesce overlaps and/or execute the
+                    ; sequence in any order.
+                    ; Example: a message sequence number set of
+                    ; 2,4:7,9,12:* for a mailbox with 15 messages is
+                    ; equivalent to 2,4,5,6,7,9,12,13,14,15
+                    ; Example: a message sequence number set of *:4,5:7
+                    ; for a mailbox with 10 messages is equivalent to
+                    ; 10,9,8,7,6,5,4,5,6,7 and MAY be reordered and
+                    ; overlap coalesced to be 4,5,6,7,8,9,10.
+
+
+See also the excellent "Introduction to IMAP" by Nick Babcock
+https://nbsoftsolutions.com/blog/introduction-to-imap
+
+
+
+See also "WITHIN Search Extension to the IMAP Protocol"
+https://tools.ietf.org/html/rfc5032
+
+...
+   search-key =/ ( "OLDER" / "YOUNGER" ) SP nz-number
+                  ; search-key defined in RFC 3501
+
+4.  Example
+
+   C: a1 SEARCH UNSEEN YOUNGER 259200
+   S: a1 * SEARCH 4 8 15 16 23 42
+
+   Search for all unseen messages within the past 3 days, or 259200
+   seconds, according to the server's current time.
+   
+=======================================================================
+=======================================================================
+

FAQ.d/FAQ.Messages_Too_Big.txt

@@ -0,0 +1,51 @@
+#!/bin/cat
+$Id: FAQ.Messages_Too_Big.txt,v 1.3 2019/06/18 16:37:39 gilles Exp gilles $
+
+This document is also available online at
+https://imapsync.lamiral.info/FAQ.d/
+https://imapsync.lamiral.info/FAQ.d/FAQ.Messages_Too_Big.txt
+
+=======================================================================
+              Dealing with too big messages with Imapsync.
+=======================================================================
+
+Questions answered in this FAQ are:
+
+Q. What can I do to transfer messages bigger than what allows the 
+   imap destination server?
+
+R1. A solution is to truncate the message to the maximum size allowed 
+    before copying it to host2. That's a little dirty but it's ok
+    if you prefer having a truncated message than no message 
+    at all. The attachments after the truncation won't be available 
+    but everything before should be ok. It may also depends
+    on the software tool reading the email message.
+
+For example, 
+Gmail currently limits messages to 35651584 bytes (May 2019),
+
+Starting with imapsync release 1.938 option --truncmess xxxx truncates
+messages bigger than the  given size xxxx.
+
+  imapsync --truncmess 35651584 --appendlimit 1000000000000
+
+Prior to imapsync release 1.938, instead of --truncmess:
+
+On Linux, use:
+
+   imapsync ... --pipemess  'perl -0ne "print substr \$_,0,35651584" '
+   
+On windows, use:
+
+   I'm not sure of (not tested yet):
+   
+   imapsync ... --pipemess  "perl -0ne 'print substr $_,0,35651584' "
+
+   
+R2. A not so dirty solution would be to transform the message and 
+    include links to the big attachments, instead of the attachments. 
+    Well, not done yet and too much complicted compared to the simple 
+    solution which is to allow big messages on the destination account.
+
+=======================================================================
+=======================================================================

FAQ.d/FAQ.Migration_Plan.txt

@@ -0,0 +1,140 @@
+#!/bin/cat
+$Id: FAQ.Migration_Plan.txt,v 1.6 2019/04/10 12:05:31 gilles Exp gilles $
+
+This document is also available online at
+https://imapsync.lamiral.info/FAQ.d/
+https://imapsync.lamiral.info/FAQ.d/FAQ.Migration_Plan.txt
+
+
+=====================================================================
+   Imapsync. Suggestions for a good, low impact on users, 
+   well executed email migration plan.
+=====================================================================
+
+There is two main different scenarios depending on the response to the
+following question:
+
+Will the imap software tools used by the users use the exact same
+credentials triplet for both imap servers, the old server host1 and
+the new server host2?
+
+The credentials triplet is hostname/username/password.
+
+If the answer is yes, ie, clients email tools use the exact same
+triplet credentials, then it is possible to perform a migration
+without changing anything on the users side. This may be a very time
+saving option. But it's a rare condition so I'll describe this
+scenario later in this document.
+
+
+=====================================================================
+Classical scenario, credentials triplets are different on both sides
+=====================================================================
+
+ * Decrease the TTL of the MX, to 5 minutes (or even less).  See
+   FAQ.TTL.txt to understand why it's an advantage.  If you can't
+   decrease the TTL, the migration will span a little more but that's
+   ok, the situation is not that bad.
+
+ * Create the new mailboxes on the destination server host2.  If the
+   users are already playing with the new mailboxes on host2, don't
+   follow this scenario.
+
+ * Presync all the mailboxes from the old server host1 to the new
+   server host2.  Presyncs can usefully be done with --delete2 in
+   order to get an exact sync. But never use the option --delete2 once
+   users have started to play with their new account on host2, their
+   play will be lost on the next presync, or when the MX is changed,
+   since INBOX will start to receive new messages that are not on
+   host1.
+
+ * Decide a migration day/hour.
+
+ * Repeat the presyncs (with the --delete2 options) daily until the
+   migration hour. This repeated process will show how long should
+   take the last sync.
+
+ * At the migration hour, cut access to the users to the old server
+   host1, if you can. Or tell them to not use it anymore.
+
+ * Do a last presync exactly like previous ones.
+
+ * Change the MX, the new messages should start to arrive in the new
+   imap server host2.
+
+ * Wait the TTL value, aka 5 minutes. Now, new messages should 
+   not arrive to the old server host1.
+
+ * Tell the users that the old imap server host1 is down and no 
+   longer available.
+
+ * Do a postsync. A postsync is a sync with the following options 
+   --maxage 1 --delete1 --folder INBOX
+
+   This postsync will move the last new messages arrived on host1 to
+   host2 during the TTL interval and delete them on host1. Do not use
+   the option --delete2 in a postsync.
+
+ * Give access to new accounts to the users with their new credential
+   triplet hostname/username/password.  If the way to contact users is
+   email then you should give this long before shutting down the old
+   server.
+
+ * Migration done.
+
+ * In case there are still messages arriving at the old imap server
+   host1, you can perform more postsyncs, ie, syncs every day 
+   with the options:
+   --maxage 1 --delete1 --folder INBOX
+
+
+=====================================================================
+Lucky scenario, credentials triplets are the same on both sides
+=====================================================================
+ 
+ * Decrease the TTL of the MX, as well as the imap hostname resolution,
+   to 5 minutes (or even less). See FAQ.TTL.txt to understand why.
+
+ * Create the new mailboxes on the destination server host2.
+ 
+ * Presync all the mailboxes from the old host1 to the new server host2, 
+   using different names that the ones used by the imap software 
+   clients (use their IP for example).
+   Presyncs have to be done with --delete2 but never use --delete2 
+   once users have started playing with their new account on host2.
+ 
+ * Decide a migration day/hour.
+
+ * repeat the presyncs (with the --delete2 options) daily until the 
+   migration hour. This repeated process will show how long should 
+   take the last sync.
+
+ * At the migration hour, cut access to the users to the old server.
+   You can do this by changing the imap host1 hostname to a non-imap 
+   server for example, or by changing their password on host1.
+
+ * Do a last sync exactly like the presyncs, not using the imap hostname.
+
+ * Change also the MX resolution, the new messages should start 
+   to arrive in the new imap server very soon.
+ 
+ * Wait the TTL value, aka 5 minutes. Now, new messages should 
+   not arrive to the old server host1.
+ 
+ * Do a postsync. A postsync is a sync with the following options 
+   --maxage 1 --delete1 --folder INBOX
+
+   This postsync will move the last new messages arrived on host1 to
+   host2 during the TTL interval and delete them on host1. Do not use
+   the option --delete2 in a postsync.
+
+ * Shutdown the old imap server.
+
+ * Change the user imap hostname resolution from the old IP of host1
+   to the IP of the new imap server host2.
+
+ * Migration done.
+
+ =======================================================================
+ =======================================================================
+ 

FAQ.d/FAQ.Old_Style_Web_Design.txt

@@ -0,0 +1,56 @@
+#!/bin/cat
+$Id: FAQ.Old_Style_Web_Design.txt,v 1.4 2019/11/25 13:08:31 gilles Exp gilles $
+
+This document is also available online at
+https://imapsync.lamiral.info/FAQ.d/
+https://imapsync.lamiral.info/FAQ.d/FAQ.Old_Style_Web_Design.txt
+
+=======================================================================
+              Imapsync tips for Gmail accounts.
+=======================================================================
+
+Questions answered in this FAQ are:
+
+Q. Why the imapsync website looks so old fashion?
+
+Now the questions again with their answers.
+
+=======================================================================
+Q. Why the imapsync website looks so old fashion?
+
+R. Once in a while I receive messages from people complaining about 
+the website style, not that much about the content by the way,
+as people don't read.
+
+I know the imapsync website has a grandmother style,
+I'm not offended by complaints about it.
+
+Here are several reasons it stays like that for now:
+
+* I like to do things myself
+
+* I like static web
+
+* I'm proud to be w3c compliant
+  https://validator.w3.org/check?uri=https%3A%2F%2Fimapsync.lamiral.info
+  Very very few sites are w3c compliant, it's because all CMS frameworks aren't.
+
+* I prefer to spend more time on the product itself than the showcase
+
+* The product is a command line, a fancy website to sell a command line
+  makes more disappointed buyers
+
+
+I agree I could do some sort of A/B experiment and see whether during
+a month I sell more imapsync on a brand new style B site than
+the current A one.
+
+
+Besides, don't misunderstand buyers. The surprising thing about complainers
+is that all are web designers, none is a user not in the webdesign branch. 
+I even received some phone call from a buyer saying: "I saw your website 
+and I told to myself: this can't be a fake one, the product must be a good one".
+
+Another folk like me:
+http://keyhut.com/pos.htm
+(well, not w3c compliant, since only mad people try to be w3c compliant)

FAQ.d/FAQ.OnlineUI.txt

@@ -0,0 +1,136 @@
+#!/bin/cat
+$Id: FAQ.OnlineUI.txt,v 1.20 2019/12/06 14:51:03 gilles Exp gilles $
+
+This document is also available online at
+https://imapsync.lamiral.info/FAQ.d/
+https://imapsync.lamiral.info/FAQ.d/FAQ.OnlineUI.txt
+
+=====================================================================
+   Imapsync tips about the online visual user interfaces
+   https://i005.lamiral.info/X/
+   https://imapsync.lamiral.info/X/
+=====================================================================
+
+Questions answered in this FAQ are:
+
+Q. How secure is the online visual user interface /X?
+
+Q. Will I have any issues with browser timing out? What happens
+   if the browser connection is closed for whatever reason?
+
+
+Now the questions again with their answers.
+
+=====================================================================
+Q. How secure is the online visual user interface /X?
+
+R0. Well, I don't know if asking the provider whether his online 
+   service is secure or not would be of any interest. 
+   Let's do it anyway, you'll be the judge.
+
+R1. Some figures
+
+Date of this report: 6 December 2019.
+
+The online imapsync service /X started 9 January 2017 
+(1061 days of service).
+
+In average, /X has 50 users per day lunching in mean 6 
+different migrations, from just one launch to many (hundreds).
+
+The total volume /X transferred is around 101 TiB in more 
+than 219 thousands email imap migrations, 
+340 millions email messages.
+
+R2. Pros & Cons
+
+The online imapsync service /X runs on https only, with a 
+letsencrypt certificate, a certificate overall rated "A+" at
+https://www.ssllabs.com/ssltest/analyze.html?d=i005.lamiral.info
+
+Because of the https usage, what the users enter in their browser,
+the imap logins and passwords, can't be eavesdropped on the network.
+
+Imapsync itself takes care about encryption for the imap sessions, 
+if possible: It tries SSL first on port 993, then TLS on port 143 
+if the servers announces TLS, then no encryption at all. 
+Concerning encryption, what is done with the source imap server host1 
+is independent of what is done with the destination imap server host2.
+
+At the date of 6 December 2019, there is no security problem 
+detected or reported to me (Gilles LAMIRAL), so far.
+Feel free to attack the service and feel free to report any 
+hole encountered. Have in mind I can watch what you try 
+from the server side and take measure if the service suffers from
+your acts.
+
+As the owner of the service, it could have been 219 000 pairs of 
+credentials collected and nearly 101 terabytes of email messages. 
+I haven't kept them but I can't prove I haven't. It's just trust, 
+like nearly every online service in the universe.
+
+The imap server certificates are not checked for authenticity 
+(by default) because too many  imap servers are crappy configured 
+regarding certified certificates.
+
+This default behavior is chosen like this because users of /X 
+want their emails transferred, instead of being not transferred 
+because of an incompetent imap server sysadmin.
+
+I admint that this part, checking imap ssl/tls certificates, 
+could be improved from my side by including well known 
+certificates directly in imapsync. 
+
+If the imap servers don't honor ssl nor tls, then logins, passwords 
+and everything will go clear text during the imap transfers. 
+That's not good at all but what "comforts" me is that if the 
+imap servers do only clear text transfers, then it's also true 
+for all imap sessions the accounts' owner encounters, 
+imapsync is just one of them.
+
+Last point, who could be sure that no cracker cracked the online 
+hosts and that he isn't currently sniffing the credentials?
+
+No one, I'm not sure myself, even if I do take care of that 
+possibility. So changing the imap accounts passwords after 
+a sync is a safe and recommended practice!
+
+=====================================================================
+Q. Will I have any issues with browser timing out? What happens
+   if the browser connection is closed for whatever reason?
+
+R. It stops the imapsync process, ie, the sync is ended right away.
+
+Further comments on this behavior.
+
+When using the /X interface there are three connections. 
+One connection is the Browser/WebServer connection, 
+the two others connections are the WebServer/ImapServers 
+connections (imapsync stuff).
+
+If the Browser/WebServer connection is timeout or ended, 
+the imapsync sync is also ended immediately by the remote 
+Apache https server. Technically, Apache sends a TERM signal
+to the imapsync process, then wait some seconds before 
+sending a KILL signal if it is still alive.
+
+You can relaunch a sync again with "Sync!" button, at any time.
+If the "Sync!" button is gray/inactive then just reload 
+the page (F5 or similar), and reenter the credentials.
+
+If the interface tells you that a sync is already going on,
+it may be that a sync is running from another browser or place.
+You can stop this sync with the "Abort!" button from any /X
+tab/window, even from another browser or place. To be able
+to abort with success, you have to give the same account 
+parameters, same credentials, or imapsync will ignore the demand.
+
+In other words, you can try safely to launch several parallel 
+runs between the same mailboxes. Open a new tab/windows with /X, 
+and start the exact same sync. It's safe, the /X will say, if any, that 
+there is already a current sync running on them and it will present
+the logfile running the sync like a "tail -f" command (isn't that magic?).
+
+
+=====================================================================
+=====================================================================

FAQ.d/FAQ.Oracle-UCS.txt

@@ -0,0 +1,23 @@
+#!/bin/cat
+$Id: FAQ.Oracle-UCS.txt,v 1.5 2018/05/24 11:34:30 gilles Exp gilles $
+
+This document is also available online at
+https://imapsync.lamiral.info/FAQ.d/
+https://imapsync.lamiral.info/FAQ.d/FAQ.Oracle-UCS.txt
+
+
+=======================================================================
+       Imapsync tips for Oracle-UCS. Specific issues.
+=======================================================================
+
+Oracle-UCS was previously Sun JES, IPlanet, etc.
+
+"NO Message contains NUL characters"
+--skipmess 'm/(\x00)+\Z/'
+
+"Message contains invalid header"
+--skipmess 'm/[\x80-\xff]/' 
+
+
+=======================================================================
+=======================================================================

FAQ.d/FAQ.POP3.txt

@@ -0,0 +1,118 @@
+#!/bin/cat
+$Id: FAQ.POP3.txt,v 1.5 2019/07/27 20:18:37 gilles Exp gilles $
+
+This document is also available online at
+https://imapsync.lamiral.info/FAQ.d/
+https://imapsync.lamiral.info/FAQ.d/FAQ.POP3.txt
+
+
+=======================================================================
+               Imapsync tips about POP3.
+=======================================================================
+
+Questions answered here are:
+
+Q. Can I use imapsync to migrate emails from pop3 server to imap server?
+
+Q. How can I handle those terrible POP-leaving-a-copy users?
+   POP-leaving-a-copy clients will download a new copy of all 
+   their emails after a migration, which is a big pain and 
+   causes hundreds of support calls. 
+
+=======================================================================
+Q. Can I use imapsync to migrate emails from pop3 server to imap server?
+
+R1. No, but you can migrate emails from a pop3 server to an imap server 
+with the command line tool pop2imap:
+http://www.linux-france.org/prj/pop2imap/
+http://www.linux-france.org/prj/pop2imap/README
+
+R2. Yes, sometimes, because many pop3 servers runs in parallel
+with an imap server on exactly the same mailboxes. They serve 
+the same INBOX, ie, imap serves INBOX and several other folders, 
+pop3 serves only INBOX.
+So have a try with imapsync on the same host1.
+
+=======================================================================
+Q. How can I handle those terrible POP-leaving-a-copy users?
+   POP-leaving-a-copy clients will download a new copy of all 
+   their emails after a migration, which is a big pain and 
+   causes hundreds of support calls. 
+
+R1. Context and condition: you have access to the POP email client tool
+and the user WILL STAY using POP.
+
+POP email client tools can leave or delete the messages after pulling 
+them. It's very often a configurable behavior. Configure the email client
+tool to delete the messages already pulled and then they won't never 
+be pulled again from the server to the client. 
+
+If you can't access to the POP email client tool, see R2 below.
+
+Problem in the future: INBOX will be seen as empty when the email client
+go to IMAP (unless the email client tool allows then an upload
+synchronization, but don't count on that...)
+
+
+R2. Context and condition: you know which users use POP.
+
+If the pop mailboxes are known then all the INBOX messages can be moved 
+in an subfolder called INBOX_backup for example. Ti help you do this,
+the tool pop2imap transfers messages from POP to IMAP, without duplicates, 
+without deleting the messages transferred, by default, and can put them 
+in any subfolder you want to. It can also delete them and, that way,
+do what the email client tool don't or can't do, for any reason. 
+We're here to do a good job with what we have, do we?
+
+In case of Dovecot for example, the magic can be there since already 
+fetched messages via POP are seen as \Seen in IMAP but the new messages are 
+seen as new messages, thanks to the Dovecot developper Timo's cleverness!. 
+So it is possible to sync back only the new messages to INBOX, 
+with "imapsync ... --search UNSEEN ...", and then  POP users won't see the old 
+messages come back but they will see the new messages and fetch them via POP.
+
+
+R3. Context and condition: you know nothing
+
+Do R2 without the sync back of UNSEEN messages. It can't hurt to have a backup
+of INBOX in a subfolder for IMAP or POP users.
+
+R4. Here are some points, an analyse that made me purpose the not 
+to bad but not very good R2 answer.
+
+There was a discussion about this issue on the imapsync mailing-list:
+http://www.linux-france.org/prj/imapsync_list/msg02622.html
+http://www.linux-france.org/prj/imapsync_list/msg02623.html
+My reply was not very good
+http://www.linux-france.org/prj/imapsync_list/msg02624.html
+It's because I wrote pop2imap and it uses a stateless
+mechanism to avoid duplicates, I wasn't aware of UIDL when I wrote pop2imap,
+and later when I entered the discussion.
+
+See also Rick Sanders discussion about this issue:
+https://www.emailquestions.com/threads/how-to-prevent-duplicate-emails-after-server-migration-for-pop3-users-with-leave-mail-on-server.8109/
+
+Quoting Timo Sirainen on
+https://wiki2.dovecot.org/Migration
+
+"If a client already saw changed UIDLs and decided to start
+re-downloading mails, it's unlikely there is anything you can do to
+stop it. Even going back to your old server is unlikely to help at
+that point."
+
+"Some (many?) POP3 clients also require that the message ordering is
+preserved."
+
+"Some clients re-download all mails if you change the hostname in the
+client configuration. Be aware of this when testing."
+
+Quoting 
+https://wiki.dovecot.org/POP3Server
+
+"Flag changes
+By default when a message is RETRed, \Seen flag is added to it. 
+POP3 itself doesn't support flags, but if the mailbox is opened 
+with IMAP (eg. from webmail) it's shown as seen."
+
+=======================================================================
+=======================================================================

FAQ.d/FAQ.Passwords_on_Unix.txt

@@ -0,0 +1,40 @@
+#!/bin/cat
+$Id: FAQ.Passwords_on_Unix.txt,v 1.6 2019/04/02 17:19:21 gilles Exp gilles $
+
+This document is also available online at
+https://imapsync.lamiral.info/FAQ.d/
+https://imapsync.lamiral.info/FAQ.d/FAQ.Passwords_on_Unix.txt
+
+
+=======================================================================
+              Imapsync issues with passwords on Unix.
+=======================================================================
+
+
+=======================================================================
+Q. On Unix, some passwords contain some weird *(),;&~ characters. 
+   Login fails.
+
+R1. Enclose the password within single-quotes in the imapsync
+    command line:
+
+    imapsync ... --password1 'passw*(),;&rd~'
+
+R2. If R1 fails, with very old imapsync or old Mail::IMAPClient Perl module,
+    try also using double-quotes within single-quotes. It will enclose
+    the password within double-quotes in the imap LOGIN command:
+
+    imapsync ... --password1 '"passw*(),;&rd~"'
+
+Old Mail::IMAPClient 3.37 is a bad horse having this issue solved
+by this double-quotes trick.
+fixed in 3.38 https://metacpan.org/changes/distribution/Mail-IMAPClient
+version 3.38: Tue Feb  9 02:48:21 UTC 2016
+        - rt.cpan.org#110273: failure to quote password values
+          (regression introduced in 3.36 via fix for rt.cpan.org#100601)
+
+R3. Change the password to keep only f...ing normal characters.
+    Make it long and random if strong security is your concern
+
+=======================================================================
+=======================================================================

FAQ.d/FAQ.Passwords_on_Windows.txt

@@ -0,0 +1,65 @@
+#!/bin/cat
+$Id: FAQ.Passwords_on_Windows.txt,v 1.5 2018/06/11 22:35:10 gilles Exp gilles $
+
+This document is also available online at
+https://imapsync.lamiral.info/FAQ.d/
+https://imapsync.lamiral.info/FAQ.d/FAQ.Passwords_on_Windows.txt
+
+
+=======================================================================
+             Imapsync issues with passwords on Windows.
+=======================================================================
+
+Related documentation:
+
+http://www.robvanderwoude.com/escapechars.php
+http://stackoverflow.com/questions/3288552/how-can-i-escape-an-exclamation-mark-in-cmd-scripts
+
+In case you're brave and relentless, understand and try this:
+http://www.dostips.com/forum/viewtopic.php?f=3&t=1733
+
+=======================================================================
+Q. On Windows, some passwords contain $ or other special characters
+   like one more more of the nine characters $%&<>|^"! 
+   Login fails. 
+
+   
+R0. Change the password so that only normal characters remain.
+    It's often a quick and good solution. If you care about
+    strong password policy, just make it longer.
+    If you can't avoid special characters use no problematic
+    characters such as underscore _ or minus - or comma , or dot.
+    If you can't change passwords then read on and good luck!
+
+R1. Enclose passwords between ""
+
+    imapsync ... --password1 "zzz$zz$$z"
+
+R2. Prefix each $ character with a ^ since ^ is the escape character
+    on Windows
+
+    imapsync ... --password1 zzz^$zz^$^$z
+
+For a password that is exactly the 8 characters string $%&<>|^"
+you have to enter
+
+    imapsync ... --password1 "$%%&<>|^"^"
+
+The exclamation mark ! does not have to be escaped sometimes,
+so have a try.
+
+=======================================================================
+Q. On Windows, some passwords begin with an equal = character. 
+   Login fails. What can I do?
+
+R. Use twice equals == characters instead; For example, if =secret 
+   is the password then use:
+
+    imapsync ... --password1 ==secret
+
+or even
+
+    imapsync ... --password1 "==secret"
+
+=======================================================================
+=======================================================================

FAQ.d/FAQ.Principles.txt

@@ -0,0 +1,41 @@
+
+$Id: FAQ.Principles.txt,v 1.5 2019/09/05 13:33:46 gilles Exp gilles $
+
+This documentation is also available online at
+https://imapsync.lamiral.info/FAQ.d/
+https://imapsync.lamiral.info/FAQ.d/FAQ.Principles.txt
+
+
+=======================================================================
+             Imapsync principles and design ideas  
+=======================================================================
+
+
+Questions answered in this FAQ are:
+
+Q. What is the bandwidth used by imapsync?
+
+
+Now the questions again with their answers.
+
+=======================================================================
+Q. What is the bandwidth used by imapsync?
+
+R. From the host where imapsync runs, it opens two imap connections, 
+   one with the source account at host1, one with the destination 
+   account at host2.
+   
+   So, the global bandwidth used is twice the volume of the source 
+   account, one volume to download the messages from host1, 
+   one volume to upload those messages to host2.
+   
+   If the host2 is already filled with the messages, imapsync doesn't
+   transfer them and then the volume transferred is small, just the IMAP
+   commands to identify the messages on both sides.
+   
+   There is no local cache of the email messages, except when a 
+   message is very big, it is temporarly saved locally. 
+   
+
+=======================================================================
+=======================================================================

FAQ.d/FAQ.Release_Checklist.txt

@@ -0,0 +1,46 @@
+#!/bin/cat
+$Id: FAQ.Release_Checklist.txt,v 1.16 2020/01/04 09:35:36 gilles Exp gilles $
+
+This documentation is also available online at
+https://imapsync.lamiral.info/FAQ.d/
+https://imapsync.lamiral.info/FAQ.d/FAQ.Release_Checklist.txt
+
+=======================================================================
+               Imapsync developer notes
+=======================================================================
+
+
+Checklist before release a new release:
+
+- Add a new section in S/news.shtml reading "rlog imapsync"
+- In case of a new dependency, add it to all the INSTALL/* files.
+- Generate the README
+- Run a spell checker on the README
+- Read the README again slowly. Fix all issues, all.
+- Read the OPTIONS section of README and read it very slowly
+- Read slowly README_Windows.txt
+- Read slowly the TUTORIAL_Unix file in html
+- Review the newsletter by running:
+    m4 -P W/ml_announce.in.txt
+
+- Review the TODO file and mark done what is done.
+- Review the general FAQ.d/FAQ.General.txt
+- Report values of --gmail1 --gmail2 to FAQ.Gmail.txt
+- Report values of --exchange* --office* to FAQ.Exchange.txt
+
+- /X verify direct cgi
+- /X verify under noscript with firefox
+- /X verify under private with chrome
+
+- Check the binaries imapsync.exe imapsync_64bit.exe with
+  https://www.virustotal.com/
+  https://www.metadefender.com/
+
+
+- make dist
+- verify on Windows the zip extraction and simple execution of imapsync_example.bat
+- make publish
+- verify VERSION is uploaded
+
+=======================================================================
+=======================================================================

FAQ.d/FAQ.Reporting_Bugs.txt

@@ -0,0 +1,33 @@
+#!/bin/cat
+$Id: FAQ.Reporting_Bugs.txt,v 1.4 2018/05/24 11:34:30 gilles Exp gilles $
+
+This document is also available online at
+https://imapsync.lamiral.info/FAQ.d/
+https://imapsync.lamiral.info/FAQ.d/FAQ.Reporting_Bugs.txt
+
+
+=======================================================================
+               Imapsync bugs reports
+=======================================================================
+
+=======================================================================
+Q. How can I report bugs or problems I encountered with Imapsync?
+
+R. Help me to help you: follow the following guidelines.
+
+Report any bug or feature request directly to the author by
+email at <gilles@lamiral.info>
+
+Put a useful title with word "imapsync" in it: my spam filters 
+won't filter it.
+
+Provide me any useful information. The simplest way is to attach 
+the complete log file, in case it is not too big, let say less 
+than 1MB. Don't zip it, it will slow my response.
+
+Thanks!
+
+=======================================================================
+=======================================================================
+
+

FAQ.d/FAQ.SSL_errors.txt

@@ -0,0 +1,133 @@
+#!/bin/cat
+$Id: FAQ.SSL_errors.txt,v 1.9 2019/12/11 15:38:37 gilles Exp gilles $
+
+This document is also available online at
+https://imapsync.lamiral.info/FAQ.d/
+https://imapsync.lamiral.info/FAQ.d/FAQ.SSL_errors.txt
+
+
+=======================================================================
+               Imapsync SSL errors
+=======================================================================
+
+Questions answered in this FAQ are:
+
+Q. What are the errors
+  DEBUG: .../IO/Socket/SSL.pm:1165: local error: SSL write error
+  or
+  DEBUG: .../IO/Socket/SSL.pm:1088: local error: SSL read error
+
+Q. What can I do to avoid those "SSL read/write errors"?
+
+Q. SSL connect attempt failed SSL 
+   routines:SSL23_GET_SERVER_HELLO:sslv3 alert handshake failure
+
+
+Now the questions again with their answers.
+
+=======================================================================
+Q. What are the errors
+  DEBUG: .../IO/Socket/SSL.pm:1165: local error: SSL write error
+  or
+  DEBUG: .../IO/Socket/SSL.pm:1088: local error: SSL read error
+
+
+R1.Like they claim, those errors are SSL errors. SSL is not directly
+   done by imapsync but by an underlying Perl module called
+   IO::Socket::SSL. Those errors arise sometimes and sometimes
+   they form a serie that ends with imapsync auto-abortion.
+   Those errors happen with some hosts but not with others,
+   it's often Exchange or Office365. I don't know what exactly happens.
+   Those errors happen more often on Windows than on Linux.
+
+
+=======================================================================
+Q. What can I do to avoid those "SSL read/write errors"?
+
+R0. Windows users: upgrade to imapsync.exe release 1.836 (or next ones)
+    Those errors don't appear with recent releases, post 1.836
+
+R1. Remove all ssl/tls encryption
+
+  imapsync ...   --nossl1 --notls1 --nossl2 --notls2
+
+R2. If you don't want to quit encryption, rerun imapsync until the 
+    complete sync is over. Those errors are not at the same place 
+    each time, so imapsync will sync remaining messages at each run
+    until none remains.
+
+R3. Run imapsync on a Linux machine, a VM is ok, there are less
+    SSL errors on Unix.
+    
+R4. Use https://imapsync.lamiral.info/X/
+    It's a Linux host so response R3 applies there.
+
+R5. Set up a ssltunnel proxy to the host.
+    Read the file FAQ.Security.txt for an example to set up
+    a ssltunnel proxy.
+
+=======================================================================
+Q. SSL connect attempt failed SSL 
+   routines:SSL23_GET_SERVER_HELLO:sslv3 alert handshake failure
+
+R1. Use: 
+
+   imapsync ... --sslargs1 'SSL_cipher_list=DEFAULT' 
+   or    
+   imapsync ... --sslargs2 'SSL_cipher_list=DEFAULT' 
+
+   depending on where the error occurs, host1 or host2 or both.
+
+R2. If it doesn't work, I let you try other things, 
+    I quote the "SSL_version" section of
+    https://metacpan.org/pod/IO::Socket::SSL (Module version: 2.066)
+
+    imapsync ...  --sslargs1 SSL_version=SSLv2
+    imapsync ...  --sslargs1 SSL_version=TLSv1_2
+    
+    SSLv2 and TLSv12 are just examples depending on your context
+    (--ssl1 or --tls1, and also the imap server encryption scheme)
+    
+Feedback on what worked for you (and possibly hy) is welcome!
+
+https://metacpan.org/pod/IO::Socket::SSL
+...
+SSL_version
+
+Sets the version of the SSL protocol used to transmit data.
+'SSLv23' uses a handshake compatible with SSL2.0, SSL3.0 and TLS1.x, 
+while 'SSLv2', 'SSLv3', 'TLSv1', 'TLSv1_1', 'TLSv1_2', or 'TLSv1_3' 
+restrict handshake and protocol to the specified version. 
+All values are case-insensitive. Instead of 'TLSv1_1', 'TLSv1_2', and 'TLSv1_3' 
+one can also use 'TLSv11', 'TLSv12', and 'TLSv13'.
+
+Support for 'TLSv1_1', 'TLSv1_2', and 'TLSv1_3' 
+requires recent versions of Net::SSLeay and openssl.
+
+Independent from the handshake format you can limit to set of 
+accepted SSL versions by adding !version separated by ':'.
+The default SSL_version is 'SSLv23:!SSLv3:!SSLv2' which means, 
+that the handshake format is compatible to SSL2.0 and higher, 
+but that the successful handshake is limited to TLS1.0 and higher, 
+that is no SSL2.0 or SSL3.0 because both of these versions have
+serious security issues and should not be used anymore.
+
+You can also use !TLSv1_1 and !TLSv1_2 to 
+disable TLS versions 1.1 and 1.2 while still allowing TLS version 1.0.
+
+Setting the version instead to 'TLSv1' might break interaction 
+with older clients, which need and SSL2.0 compatible handshake.
+
+On the other side some clients just close the connection 
+when they receive a TLS version 1.1 request. 
+In this case setting the version 
+to 'SSLv23:!SSLv2:!SSLv3:!TLSv1_1:!TLSv1_2' might help.
+
+
+=======================================================================
+=======================================================================
+
+
+
+
+

FAQ.d/FAQ.Security.txt

@@ -0,0 +1,217 @@
+#!/bin/cat
+# $Id: FAQ.Security.txt,v 1.19 2018/09/13 17:53:45 gilles Exp gilles $
+
+This document is also available online at
+https://imapsync.lamiral.info/FAQ.d/
+https://imapsync.lamiral.info/FAQ.d/FAQ.Security.txt
+
+
+=======================================================================
+      Imapsync tips about security. Issues and solutions.
+=======================================================================
+
+SSL: going to encryption before the imap session start. 
+     It is on port 993.
+
+TLS: going to encryption after the imap session start but before
+     the credential are sent. It is on port 143.
+
+=======================================================================
+Q. Is running this program a secure method of transferring emails?  
+   Are there any security concerns?
+
+R. Well, it depends. Use encryption, secure the access to the host running
+   imapsync and everything shall be safe.
+
+=======================================================================
+Q. I noticed that the online UI has no option for TLS/SSL 
+   Is this secure? Is this more secure that using the .bat file 
+   on my computer?
+
+R1. The online UI does TLS/SSL imap connections if the imap
+    servers support TLS/SSL. If you are concerned by security then 
+    using the .bat file or .sh on your computer should be more secure 
+    since you can examine and secure it by yourself, no matter high is
+    your paranoïd spirit. The online UI security is mine, I am
+    concerned by security, not to the upmost high level possible 
+    but I won't give you direct access to the host to discover my level.
+    With a good guy spirit, feel free to try to break the online UI 
+    security and report me any security issue you encounter, I'll do my
+    best to fix them as soon as possible. Drop me a note before
+    starting because I may detect a sort of abuse and ban 
+    definitively your IPs.
+
+=======================================================================
+Q. Are transferred emails/attachments stored on any other 
+   server/location aside from my originating/destination server(s)?
+
+R. No!
+
+=======================================================================
+Q. Other than changing passwords on the originating/destination email 
+   accounts once the relevant emails have been moved, 
+   are there any other security tips I should know?
+
+R. Secure the host where imapsync is running since credentials are
+   on it.
+
+=======================================================================
+Q. I need to transfer mail from an imap server to an other imap server. 
+   Which ports need to be open on the firewall to make this possible?
+
+R. It depends. Open either:
+    * port 143 in basic (no special option) or tls mode (--tls1 or --tls2)
+    * port 993 in ssl mode (--ssl1 or --ssl2)
+
+=======================================================================
+Q. Does imapsync support IMAP TLS?
+
+R1. Yes. 
+   Use --tls1 and/or --tls2 options:
+
+  --tls1 tells imapsync to use tls on host1.
+  --tls2 tells imapsync to use tls on host2.
+
+R2. Since imapsync release 1.755 TLS mode is activated automatically
+    if the server announce it supports it, STARTTLS inside the response 
+    to CAPABILITY, and if neither --notls nor --ssl is explicitely
+    mentioned on the command line options.
+
+=======================================================================
+Q. Does imapsync support IMAP over SSL (IMAPS)?
+
+R. Yes natively since release 1.161. 
+   Still, there are 2 ways, at least, to use ssl:
+
+a) Use native --ssl1 and/or --ssl2 options
+
+  --ssl1 tells imapsync to use ssl on host1.
+  --ssl2 tells imapsync to use ssl on host2.
+
+
+b) Use stunnel
+   http://www.stunnel.org/
+   Use stunnel3 command since stunnel now usually calls
+   stunnel4 or stunnel5 and the command line options syntax 
+   has changed (option "-c" not recognized for example).
+   
+   Assuming there is an imaps (993) server on imap.foo.org,
+   on your localhost machine (or bar machine), run:
+
+     stunnel3 -c -d imap -r imap.foo.org:imaps -f 
+
+   or using numbers instead of names:
+
+     stunnel3 -c -d 143 -r imap.foo.org:993  -f
+
+   then use imapsync on localhost (or bar machine) imap (143) port.
+   If the local port 143 is already taken then use a free one, 
+   like 10143 for example.
+
+c) Other example for accessing gmail with no local root access 
+   to open port 143
+
+   stunnel3 -P '' -c -d 9993 -r imap.gmail.com:993 -f 
+
+Then, to access gmail as host2 use:
+
+  imapsync ... --host2 localhost --port2 9993 --nossl2 
+
+
+=======================================================================
+Q.How can I test an ssl imap connection without imapsync?
+
+R1. Use either ncat or telnet-ssl or openssl commands like in the 
+    following examples with imap.gmail.com server:
+
+  ncat --ssl -C imap.gmail.com 993
+
+  telnet-ssl -z ssl  imap.gmail.com 993
+
+  openssl s_client -crlf -connect imap.gmail.com:993
+
+The previous commands are interactive, hit ctrl-c
+to finish them. If you want to finish automatically, then use: 
+
+  { sleep 2; echo "a logout"; sleep 1; } | ncat --ssl -C  imap.gmail.com 993
+
+
+=======================================================================
+Q. How can I manually test a login via ssl?
+
+R. Use either ncat or telnet-ssl or openssl commands like in the 
+    following examples with imap.gmail.com server:
+
+  ncat --ssl -C imap.gmail.com 993
+  telnet-ssl -z ssl  imap.gmail.com 993
+  openssl s_client -crlf  -connect imap.gmail.com:993
+
+Tipical dialog for an imap LOGIN command:
+  
+* OK Gimap ready for requests from 78.196.254.58 q1mb175739668wix
+a LOGIN "gilles.lamiral@gmail.com" "secret" 
+* CAPABILITY IMAP4rev1 UNSELECT IDLE NAMESPACE ... ESEARCH
+a OK gilles.lamiral@gmail.com Gilles Lamiral authenticated (Success)
+b LOGOUT
+* BYE LOGOUT Requested
+b OK 73 good day (Success)
+
+The client part you have to type is 
+a LOGIN ... 
+b LOGOUT
+while replacing ... by your credentials values.
+
+
+=======================================================================
+Q.How can I test an tls imap connection without imapsync?
+
+R1. Use openssl command like the following example with 
+    an outlook.office365.com server:
+
+  openssl s_client -crlf -starttls imap -connect outlook.office365.com:143
+
+The previous commands are interactive, hit ctrl-c
+to finish them. If you want to finish automatically, then use: 
+
+  { sleep 2; echo "a logout"; sleep 1; } | openssl s_client -crlf -starttls imap -connect outlook.office365.com:143
+
+Replace outlook.office365.com with your imap server name.
+
+
+======================================================================
+Q. Imapsync used to use SSL_VERIFY_PEER now it uses SSL_VERIFY_NONE.
+   How can I change this back to the more secure SSL_VERIFY_PEER?
+
+
+R2. After imapsync 1.673, 
+    to set SSL_verify_mode to SSL_VERIFY_PEER on host1
+    and    SSL_verify_mode to SSL_VERIFY_NONE on host2
+
+  imapsync ...  --ssl1 --ssl2  \
+                --sslargs1 SSL_verify_mode=1 \
+                --sslargs2 SSL_verify_mode=0 
+
+See perldoc IO::Socket::SSL for all possibilities, also at
+http://search.cpan.org/perldoc?IO%3A%3ASocket%3A%3ASSL
+
+It might be possible you need an extra:
+                --sslargs1 SSL_ca_file=/etc/ssl/certs/ca-certificates.crt 
+to help the ssl software verifying the server certificate.
+The file ca-certificates.crt may be elsewhere on your system, even 
+named differently.
+
+=======================================================================
+Q: How to have an imaps server?
+
+R. 
+a) Install one 
+
+b) or use stunnel :
+   Assuming there is an imap (143) server on localhost
+        stunnel  -d 993 -r 143 -f
+
+c) or use stunnel on inetd
+   imaps stream  tcp nowait cyrus /usr/sbin/stunnel -s cyrus -p /etc/ssl/certs/imapd.pem -r localhost:imap2
+
+=======================================================================
+=======================================================================

FAQ.d/FAQ.SmarterMail.txt

@@ -0,0 +1,44 @@
+#!/bin/cat
+$Id: FAQ.SmarterMail.txt,v 1.14 2019/10/15 14:57:19 gilles Exp gilles $
+
+This document is also available online at
+https://imapsync.lamiral.info/FAQ.d/
+https://imapsync.lamiral.info/FAQ.d/FAQ.SmarterMail.txt
+
+
+=======================================================================
+    Imapsync tips for SmarterMail. Specific issues and solutions.
+=======================================================================
+
+
+=======================================================================
+Q. Synchronizing from SmarterMail to XXX
+
+On Unix:
+imapsync --host1 imap.d1.org --user1 joe --password1 secret1 \
+         --host2 imap.d2.org --user2 joe --password2 secret2 \
+         --sep1 "/" --prefix1 "" --useheader Message-Id --noabletosearch
+
+On Windows:
+imapsync.exe --host1 imap.d1.org --user1 joe --password1 secret1 ^
+         --host2 imap.d2.org --user2 joe --password2 secret2  ^
+         --sep1 "/" --prefix1 "" --useheader Message-Id --noabletosearch
+
+
+=======================================================================
+Q. Synchronizing from XXX to SmarterMail
+
+On Unix:
+imapsync --host1 imap.d1.org --user1 joe --password1 secret1  \
+         --host2 imap.d2.org --user2 joe --password2 secret2  \
+         --sep2 "/" --prefix2 "" --useheader Message-Id --noabletosearch
+
+On Windows:
+imapsync.exe --host1 imap.d1.org --user1 joe --password1 secret1 ^
+             --host2 imap.d2.org --user2 joe --password2 secret2 ^
+             --sep2 "/" --prefix2 "" --useheader Message-Id --noabletosearch
+
+
+=======================================================================
+=======================================================================
+

FAQ.d/FAQ.TTL.txt

@@ -0,0 +1,37 @@
+#!/bin/cat
+$Id: FAQ.TTL.txt,v 1.2 2018/05/24 11:34:30 gilles Exp gilles $
+
+This document is also available online at
+https://imapsync.lamiral.info/FAQ.d/
+https://imapsync.lamiral.info/FAQ.d/FAQ.TTL.txt
+
+
+=====================================================================
+   Imapsync tips about TTL when changing name resolution of hosts
+=====================================================================
+
+Why decrease the TTL (Time To Live) delay in DNS configuration, down
+to 5 minutes?
+
+A small TTL is not mandatory, it's safer and more easy to work with when
+migrating.
+
+It's about how long it takes to be sure the users are using the new
+imap host, and how long it takes to be sure all new incoming messages
+are going right now at the right place. Will you shut down the old
+server just after the resolution change? I guess you won't and you'll
+be right.
+
+The TTL is just a value, very well supported by machines, with a
+little name resolution supplementary work for them when it is set to a
+small value like 5 minutes, but it's a tremendous comfort for migrator
+people like us.
+
+Be sure to wait 24h after this TTL change before changing any
+resolution since the TTL change has to be propagated as well. After
+the migration done, no problem to set back the TTL to 24h or more. If
+you can't decrease TTL under 4h or even 24h, it's ok anyway, imapsync
+can sync the new messages dropped in the old server.
+
+=======================================================================
+=======================================================================

FAQ.d/FAQ.Use_addheader.txt

@@ -0,0 +1,39 @@
+#!/bin/cat
+$Id: FAQ.Use_addheader.txt,v 1.6 2018/12/10 20:12:05 gilles Exp gilles $
+
+This document is also available online at
+https://imapsync.lamiral.info/FAQ.d/
+https://imapsync.lamiral.info/FAQ.d/FAQ.Use_addheader.txt
+
+
+=======================================================================
+               Imapsync --addheader suggestion.
+=======================================================================
+
+=======================================================================
+Q. What means this log message:
+   "Host1 Sent/1234 ignored (no wanted headers so we ignore this message. 
+   To solve this: use --addheader)"
+
+R. In order to sync messages from one account to another, Imapsync has
+   to identify messages on both sides, and compare them.
+   
+   Imapsync can use two completely different methods to identify 
+   messages on each account.
+   
+   The first one, the default one, uses some headers of messages.
+   Real world syncs with various imap servers have bring me to use
+   two headers "Message-Id:" and "Received:". It works for most
+   messages except for special folders like Sent or Draft where
+   messages in those folders don't have "Message-Id:" nor 
+   "Received:" headers.
+   
+   Here comes --addheader option. When a message has no "Message-Id:" 
+   nor "Received:" headers, option --addheader adds a "Message-Id" header 
+   consisting of the imap UID of the message on the host1 folder, 
+   like "Message-Id: 12345@imapsync".
+   This way, messages are well identified on both sides,
+   transferred, and only once.
+
+=======================================================================
+=======================================================================

FAQ.d/FAQ.Use_cache.txt

@@ -0,0 +1,139 @@
+
+$Id: FAQ.Use_cache.txt,v 1.9 2019/09/13 10:43:06 gilles Exp gilles $
+
+This document is also available online at
+https://imapsync.lamiral.info/FAQ.d/
+https://imapsync.lamiral.info/FAQ.d/FAQ.Use_cache.txt
+
+
+=======================================================================
+               Imapsync  --usecache option
+=======================================================================
+
+Questions answered in this FAQ are:
+
+Q. What is --usecache good for?
+
+Q. What is the technical principle of --usecache?
+
+Q. On Windows, with --useuid or --usecache a problem occurs with long
+   nested folder names. The error message is:
+   "No such file or directory; The filename or extension is too long"
+
+Q. Inode problem with --usecache or --useuid on Linux
+
+
+Now the questions again and their answers
+
+=======================================================================
+Q. What is --usecache good for?
+
+R. The option --usecache is useful to speed up next syncs with --usecache.
+   The first sync with --usecache between two imap accounts is as low 
+   as the first sync without --usecache.
+
+=======================================================================
+Q. What is the technical principle of --usecache?
+
+R. Option --usecache creates a empty file per email message
+   in order to keep the UIDs mapping between account1 and account2.
+   
+   The cache is maintened at each run. Messages UIDs enregistred 
+   in the cache are not fetched again to be identified. It really
+   speeds up the process of syncing.
+   
+   The cache directory is 
+   
+       <tmpdir>/imapsync_cache/
+       
+   where <tmpdir> is the temporary directory given by the --tmpdir option
+   or the one by default, /tmp on Unix, variable on Windows.
+   
+   
+=======================================================================
+Q. On Windows, with --useuid or --usecache a problem occurs with long
+   nested folder names. The error message is:
+   "No such file or directory; The filename or extension is too long"
+
+R. This comes from a Windows limitation on pathnames.
+No more than 260 characters are allowed for pathnames.
+See more details on page
+http://msdn.microsoft.com/en-us/library/windows/desktop/aa365247.aspx#maxpath
+The workaround solution given at the previous link, 
+ie using \\?\D:", does not work for imapsync. 
+So this imapsync Windows bug is still pending and needs a fix using 
+a different technique to cache, like a database file for example.
+
+A solution to fix the issue is to use a Linux virtual host on a 
+Windows box, with VirtualBox or VmWare etc. There is no bug this way,
+pathnames can be several thousands characters long.
+Better said that done but not so difficult nor expensive these days,
+VirtualBox is free and VmWare Player is free for personal or test use.
+
+If you have to stick on Windows, there are two good workarounds 
+to reduce the cache directory name:
+
+1) Use --tmpdir "D:\\temp" or simply --tmpdir "D:" and imapsync
+will build and use the cache in the sub directory 
+D:\imapsync_cache\
+
+2) add two equivalent entries in the etc/hosts for host1 imap.truc.org 
+and host2 imap.trac.org. 
+If you map the ip of imap.truc.org just with the letter a 
+and same thing for imap.trac.org then you gain characters
+
+etc/hosts
+
+192.168.12.1 a
+192.168.55.3 b
+
+Then use:
+
+  imapsync --host1 a --host2 b ...
+
+You can get the ip of a host with the ping command line
+C:\> ping imap.truc.org
+
+3) A third solution is to not use options --useuid nor --usecache
+
+Fixing this long path problem directly in imapsync is in the TODO file
+for a very long time.
+
+=======================================================================
+Q. Inode problem with --usecache or --useuid on Linux
+
+R. You may run out of inodes using --usecache, especially with large
+migration. Option --usecache creates a empty file per email message
+in order to keep the UIDs mapping between account1 and account2.
+
+So, if you plan to sync regularly 10 millions messages over a period 
+of migration then the filesystem of --tmpdir needs 10 millions of free 
+inodes. If it hasn't those free inodes then create a new special
+filesystem devoted to the imapsync cache. 
+
+# Create a file of 10 GB (10 millions*1024):
+
+  dd if=/dev/zero of=/var/tmp/fscache bs=1M count=10000
+
+# Create a filesystem where each file is only 1024 bytes per inode:
+
+  mkfs.ext2 -F -i 1024  /var/tmp/fscache
+
+# Mount this brand new filesystem
+
+  mkdir -p /var/tmp/cachedir
+  mount -o loop /var/tmp/fscache /var/tmp/cachedir
+  df -i /var/tmp/cachedir # count inodes available
+
+# Tell imapsync to use it
+
+  imapsync ... --tmpdir /var/tmp/cachedir/
+
+# When the migration is over and the cache becomes really useless
+
+    umount /var/tmp/cachedir/
+    rm /var/tmp/fscache
+
+
+=======================================================================
+=======================================================================

FAQ.d/FAQ.User_Concurrent_Access.txt

@@ -0,0 +1,46 @@
+#!/bin/cat
+$Id: FAQ.User_Concurrent_Access.txt,v 1.5 2018/05/24 11:34:30 gilles Exp gilles $
+
+This document is also available online at
+https://imapsync.lamiral.info/FAQ.d/
+https://imapsync.lamiral.info/FAQ.d/FAQ.User_Concurrent_Access.txt
+
+
+=======================================================================
+              Imapsync and user concurrent access.
+=======================================================================
+
+=======================================================================
+Q. What happens if a user access the mailbox during the transfer process?
+
+R. Think all potential problems with a sync between
+   a master/source/host1 and a slave/destination/host2
+
+What happens when a user access syncing accounts depends
+on what he does, where he does and when. 
+
+As a summary, reading is safe, writing/deleting is not.
+
+Details:
+
+* Reading: no problem anywhere, at source/host1 or at destination/host2,
+           anytime. Reading is safe.
+
+* Writing at source/host1:
+  * adding folder       => will need a resync after
+  * deleting folder     => folders deletions are not synced unless --delete2folders
+  * deleting message    => messages deletions are not synced unless --delete2
+  * adding message      => will need a resync
+  * moving message      => will need a resync. Moving is like adding + deleting 
+                           so --delete2 is needed to sync the deletion.
+  * message flag change => will need a resync
+
+* Writing at destination/host2:
+  * adding folder       => no problem, unless --delete2folders is used
+  * deleting folder     => will reappear by a new sync
+  * adding message      => no problem, unless --delete2 is used on next sync.
+  * deleting message    => might reappear by a new sync.
+  * message flag change => will be reseted by a new sync.
+
+=======================================================================
+=======================================================================

FAQ.d/FAQ.Various_Software_Servers.txt

@@ -0,0 +1,236 @@
+#!/bin/cat
+$Id: FAQ.Various_Software_Servers.txt,v 1.13 2019/07/04 09:26:28 gilles Exp gilles $
+
+This document is also available online at
+https://imapsync.lamiral.info/FAQ.d/
+https://imapsync.lamiral.info/FAQ.d/FAQ.Various_Server_Softwares.txt
+
+
+=======================================================================
+         Imapsync tips for various imap server softwares.
+=======================================================================
+
+
+
+=======================================================================
+Q. From or to Zimbra
+
+R. Read the FAQ.Zimbra.txt 
+   https://imapsync.lamiral.info/FAQ.d/FAQ.Zimbra.txt
+
+=======================================================================
+Q. From or to HMailServer version 4.4.1.
+
+R. You have to add prefix and separator manually because  4.4.1 doesn't
+honor the NAMESPACE imap command.
+
+Example for host1:
+
+imapsync ... \
+         --prefix1 "" --sep1 .
+
+No specific option for HMailServer 5.3.3 since NAMESPACE is supported.
+
+Maybe --subscribe_all will help you to see all migrated folders.
+
+
+=======================================================================
+Q. from Microsoft's Exchange 2007 to Google Apps for your Domain 
+   (GAFYD)
+
+R. Take a look at:
+http://mark.ossdl.de/2009/02/migrating-from-exchange-2007-to-google-apps-mail/
+
+
+=======================================================================
+Q. Migrating from or to Parallels Plex Server
+
+R. It depends on the OS
+
+Parallells Plesk Panel for Windows requires --sep2 / --prefix2 ""
+Parallells Plesk Panel for Linux works with default parameters.
+
+=======================================================================
+Q. I'm migrating from WU to Cyrus, and the mail folders are under
+   /home/user/mail but the tool copies everything in /home/user, how
+   can i avoid that?
+
+Two solutions:
+
+R. Use
+   imapsync ... --include '^mail'
+
+R. or (better)
+   imapsync ... --subscribed --subscribe
+
+
+=======================================================================
+Q. I'm migrating from WU to Cyrus, and the mail folders are under
+   /home/user/mail directory.  When imapsync creates the folders in
+   the new cyrus imap server, it makes a folder "mail" and below that
+   folder puts all the mail folders the user have in /home/user/mail,
+   i would like to have all those folders directly under INBOX.
+
+R. Use 
+   imapsync ... --regextrans2 's/^mail/INBOX/' --dry
+   look at the simulation and if all transformations seem
+   good then remove the --dry option.
+
+
+=======================================================================
+Q. Migrating from Groupwise to Cyrus
+
+R. By Jamie Neil:
+
+I eventually managed to get the mail to migrate without errors using the 
+following options:
+
+--maxage 3650
+  - some messages just don't seem to want to transfer and produce the 
+    perl errors I mentioned before. This prevents the errors, but the
+    bad messages don't transfer.
+
+Even though the mail migrated OK, there are a couple of gotchas with 
+Groupwise IMAP:
+
+1) Some of the GW folders are not real folders and are not available
+to IMAP, the main problem one being "Sent Items". I could find no way
+of coping the contents of these folders. The nearest I got was to
+create a "real" folder and copy/move the sent items into it, but
+imapsync still didn't see the messages (I think because there is
+something funny about the reported dates/sizes).
+
+It think this problem has been rectified in GW6.5.
+
+2) Version 6.0.1 of the Groupwise Internet Connector sucks. I was 
+getting server aborts when I pushed it a bit hard! I eventually had to
+upgrade to 6.0.4 which seems to be a lot more stable.
+
+=======================================================================
+Q. Migrating from iPlanet Messaging Server
+5.2 Patch 2 (built Jul 14 2004)) to Groupwise 7.0
+I encounter many errors like this:
+"Error trying to append string: 17847 BAD APPEND"
+
+R. GroupWise 7 seems buggy. Apply GroupWise 7 support pack 1
+
+
+=======================================================================
+Q. Migrating from or to David Tobit
+
+R. See FAQ.David_Tobit.txt
+   https://imapsync.lamiral.info/FAQ.d/FAQ.David_Tobit.txt
+
+=======================================================================
+
+Q. I need to migrate 1250 mailboxes, passwords are in a MySQL Database.
+Can you tell me if your script suits my needs?
+
+R. Mailboxes must exist before running imapsync.
+You have to extract users logins and passwords in a csv file.
+See the "HUGE MIGRATION" section in the README file.
+
+
+======================================================================
+Q: From MailEnable 1.75
+R: --sep1 "/" --prefix1 ""
+
+Q: From MailEnable 2.2
+R: --sep1 "." --prefix1 ""
+
+Q: To MailEnable
+R: --sep2 / --prefix2 "" --addheader --messageidnodomain --syncflagsaftercopy
+
+======================================================================
+Q. From GMX IMAP4 StreamProxy
+R. Use:
+   --prefix1 INBOX and --sep1 .
+
+======================================================================
+Q. From Courier to Archiveopteryx
+R. You can read http://www.archiveopteryx.org/migration/imapsync
+   Default values might be fine now with latest imapsync.
+
+======================================================================
+Q. To Sun Java(tm) System Messaging Server 6.2-7.05
+Q. To Communigate Pro - Solaris version
+
+R. See and run patches/imapsync_1.267_jari
+
+
+======================================================================
+Q. From Softalk Workgroup Mail 7.6.4 
+
+R. Old Softalk releases don't support the IMAP SEARCH command.
+   Here are the options to get it working.
+
+imapsync ... --sep1 '.' --prefix1 '' \
+             --noabletosearch1  --nocheckmessageexists --addheader
+
+(Thanks to Andrew Tucker)
+
+======================================================================
+Q. From or to QQMail IMAP4Server
+
+R. imapsync ... --noabletosearch1
+
+======================================================================
+Q. From FirstClass to XXX
+   http://www.firstclass.com/
+
+R. Migrating from FirstClass is not easy because FirstClass, strangely, 
+   does not show all messages via IMAP. To make it show all messages,
+   a trick, painful to follow by hand, is moving emails 
+   out and back in, for each folder. May be it can be done by a script.
+
+  FirstClass releases prior to release 12 do not shows the "Sent" 
+  folder in IMAP but FirstClass release 12 shows it.
+  I advice you to upgrade to FirstClass release 12 before leaving it
+  with imapsync or another imap tool.
+
+Here is a command line used to migrate from FirtClass release 12:
+
+  imapsync ... \
+    --tmpdir /var/tmp --usecache \
+    --useheader Message-ID \
+    --idatefromheader \
+    --addheader \
+    --regextrans2 "s,(/|^) +,\$1,g" --regextrans2 "s, +(/|$),\$1,g" \
+    --regextrans2 "s/[\^]/_/g"       \
+    --regextrans2 "s/['\"\\\\]/_/g"  \
+    --regextrans2 "s,&AC8-,-,g" \
+    --regextrans2 "s,&APg-,oe,g" 
+
+On Windows:
+  imapsync.exe ... ^
+    --automap ^
+    --usecache ^
+    --useheader Message-ID ^
+    --idatefromheader ^
+    --addheader ^
+    --regextrans2 "s,(/|^) +,$1,g" ^
+    --regextrans2 "s, +(/|$),$1,g" ^
+    --regextrans2 "s/[\^]/_/g" ^
+    --regextrans2 "s/['\\]/_/g" ^
+    --regextrans2 "s,^&AC8-,-,g"  ^
+    --regextrans2 "s,^&APg-,oe,g"
+
+
+Special thanks to Kristian Wind and Joey Alexander for helping me
+writing this FAQ item. 
+See also this worth reading discussion in a Zimbra forum:
+http://www.zimbra.com/forums/migration/20349-help-needed-migrating-firstclass.html
+
+======================================================================
+Q. From XXX to FTGate
+
+R. Do NOT use --usecache since new UIDs are not given by FTGate and also
+   badly guessed by imapsync. UIDEXPUNGE does not work so use also
+   --expunge2 when using --delete2
+  
+  imapsync ... \
+     --sep2 / --prefix2 "" \
+     --useheader Message-Id \
+
+=======================================================================
+=======================================================================

FAQ.d/FAQ.Virus.txt

@@ -0,0 +1,59 @@
+
+$Id: FAQ.Virus.txt,v 1.6 2019/12/06 09:43:52 gilles Exp gilles $
+
+This document is also available online at
+https://imapsync.lamiral.info/FAQ.d/
+https://imapsync.lamiral.info/FAQ.d/FAQ.Virus.txt
+
+
+=======================================================================
+              Imapsync and virus scanners
+=======================================================================
+
+=======================================================================
+Q. My virus scanner claims imapsync.exe is a virus/malware/trojan etc.
+   What the hell?
+
+R1. Yes, I find the same sometimes with few antivirus, some report that 
+   imapsync might have a trojan in it.
+   Most virus scanners say imapsync.exe and  is ok.
+   I've done this test on imapsync.exe release 1.727 on the two following
+   meta-virus-scanners:
+   https://www.virustotal.com/
+   https://www.metadefender.com/
+
+R2. Explanation: 
+    It may come from the fact that imapsync checks whether there is a
+    new realease available at http://imapsync.lamiral.info/VERSION
+    It's explained here:
+    https://imapsync.lamiral.info/#NUMBERS
+
+    Any other explanation is welcome!
+
+
+R3. There is no virus alerts reported for the Perl script imapsync
+    itself. The binary imapsync.exe is just a compiled version of
+    the script imapsync, with perl interpreter itself and all modules 
+    needed by imapsync in order to make imapsync.exe a standalone software.
+
+R4. Using online meta-virus-scanners
+    https://www.virustotal.com/
+    https://www.metadefender.com/
+
+    Release 1.945
+    
+    imapsync.exe release 1.945 is reported as totally clean:
+    * https://www.virustotal.com/gui/file/c122fd3bc82c9c784e8b27504e1843f95b1dfd9beba05f50a2893853ad4a6c59/details
+    * https://metadefender.opswat.com/results#!/file/bzE5MTIwNVN5ZXNDa2NMVEhCeWJpQTFjVVRT/regular/overview
+
+    imapsync_64bit.exe release 1.945 is reported as totally clean:
+    * https://www.virustotal.com/gui/file/f561c6e457c3173f7b0379ee8cc267347feff1bc1991cf47fea7c513c81ccb0a/detection
+    * https://metadefender.opswat.com/results#!/file/bzE5MDkzMHJ5dk9qb2gxZEhIMXVkaWloeV9C/regular/multiscan
+
+
+    Release 1.836
+    
+    imapsync.exe release 1.836 is reported as totally clean:
+    https://www.virustotal.com/#/file/2a33eb93198da77677a4013a5dfb4868cb6aa8f4513e2102a55884b258d19043/detection
+    https://metadefender.opswat.com/results#!/file/ZTE4MDMxN1MxZTk4aGhxdEdCSlpxVTJoOVlN/regular/information
+

FAQ.d/FAQ.XOAUTH2.txt

@@ -0,0 +1,219 @@
+#!/bin/cat
+$Id: FAQ.XOAUTH2.txt,v 1.16 2019/07/31 22:58:36 gilles Exp gilles $
+
+This document is also available online at
+https://imapsync.lamiral.info/FAQ.d/
+https://imapsync.lamiral.info/FAQ.d/FAQ.XOAUTH2.txt
+
+
+=======================================================================
+  Imapsync tips to use XOAUTH2 authentication (Gmail) and old XOAUTH 
+=======================================================================
+
+
+=======================================================================
+Q. Is XOAUTH2 authentication available with imapsync?
+
+R. Yes, but XOAUTH2 has been really tested on Unix systems, 
+   less profund on Windows but it should work.
+
+   Two file formats are available from Gmail: json and pk12.
+   json is easier to manage than pk12.
+
+=======================================================================
+Q. Imapsync XOAUTH2 fails with the following message, how to fix that?
+{
+ "error": "unauthorized_client",
+ "error_description": "Unauthorized client or scope in request."
+}
+
+R. In order to work you also have to allow the service https://mail.google.com/ 
+   in the Google client API manager for OAUTH2.
+   "Select OAuth 2.0 scopes:"
+
+=======================================================================
+Q. How to use XOAUTH2 via a json file to globally authenticate gmail users? 
+
+R. Unless you use an imapsync binary like imapsync.exe or imapsync_bin_Darwin,
+   Perl modules needed for xoauth2 are:
+
+  Crypt::OpenSSL::RSA
+  JSON
+  JSON::WebToken
+  LWP
+  HTML::Entities
+  Encode::Byte
+
+A easy way to install or upgrade Perl modules is to use cpanm command,
+also called cpanminus. On Linux it is something like
+
+  sudo cpanm  JSON::WebToken JSON Crypt::OpenSSL::RSA LWP HTML::Entities Encode::Byte
+
+The json file patch code and explanation comes from Secretion at
+https://github.com/imapsync/imapsync/pull/68
+
+Here is a complete example for Gmail. It is a little stupid
+since it is the same account as source and destination but
+it's just to get the picture for xoauth2 authentication.
+
+All xoauth2 config is given via the --password1 parameter. 
+It has the form:
+
+  --password1 secret.xoauth2.json
+
+where secret.xoauth2.json is the json file given by Gmail.
+
+
+imapsync \
+        --host1 imap.gmail.com --ssl1 --user1 gilles.lamiral@gmail.com \
+        --password1 secret.xoauth2.json --authmech1 XOAUTH2 \
+        --host2 imap.gmail.com --ssl2 --user2 gilles.lamiral@gmail.com \
+        --password2 secret.xoauth2.json --authmech2 XOAUTH2 \
+        --justlogin --debug
+
+Use your own xoauth2 values.
+
+The secret.xoauth2.json looks like:
+
+{
+  "type": "service_account",
+  "project_id": "your-project-name",
+  "private_key_id": "1cfb..............................bd7fbe",
+  "private_key": "-----BEGIN PRIVATE KEY-----\nMIIEvQIBADANBgkqhkiGziM...ZV5ACKPHuOfp8A46I=\n-----END PRIVATE KEY-----\n",
+  "client_email": "jsonfile@your-project-name.iam.gserviceaccount.com",
+  "client_id": "105................689",
+  "auth_uri": "https://accounts.google.com/o/oauth2/auth",
+  "token_uri": "https://accounts.google.com/o/oauth2/token",
+  "auth_provider_x509_cert_url": "https://www.googleapis.com/oauth2/v1/certs",
+  "client_x509_cert_url": "https://www.googleapis.com/robot/v1/metadata/x509/jsonfile%40your-project-name.iam.gserviceaccount.com"
+}
+
+You get this json file by a link like:
+https://console.developers.google.com/apis/credentials?project=your-project-name
+
+See also:
+https://developers.google.com/gmail/imap/xoauth2-protocol
+https://developers.google.com/identity/protocols/OAuth2
+
+
+=======================================================================
+Q. How to use XOAUTH2 via pk12 file to globally authenticate gmail users? 
+
+R. First, consider the XOAUTH2 feature at a prototype level.
+
+Perl modules needed for xoauth2 are:
+  Crypt::OpenSSL::RSA
+  JSON
+  JSON::WebToken
+  LWP
+  HTML::Entities
+  Encode::Byte
+
+A easy way to install or upgrade Perl modules is to use cpanm command,
+also called cpanminus.
+
+  sudo cpanm  JSON::WebToken JSON Crypt::OpenSSL::RSA LWP HTML::Entities Encode::Byte
+
+The code and first explanation comes from Joaquin Lopez at
+https://github.com/imapsync/imapsync/pull/25
+http://www.linux-france.org/prj/imapsync_list/msg02129.html
+
+Also, the binary command "openssl" is needed since it is used to 
+convert the pk12 file.
+On Windows I've tried xoauth2 with openssl from
+https://slproweb.com/download/Win32OpenSSL-1_0_2d.exe at
+https://slproweb.com/products/Win32OpenSSL.html
+It works.
+
+Here is a complete example for Gmail. It is a little stupid
+since it is the same account as source and destination but
+it's just to get the picture for xoauth2 authentication.
+
+All xoauth2 config is given via the --password1 parameter. 
+It has the form:
+
+  --password1 "A;B;C"
+
+where A = 108687549524-gj68fg5ho5icoicv3v79dq2rcuf5c85e@developer.gserviceaccount.com
+is the name of the Google Developer API service account.
+
+where B = /g/var/pass/imapsync-xoauth2-15f8456ad5b7_notasecret.p12
+is the location of the keyfile associated with it.
+
+where C = notasecret
+is the password to access the keyfile.
+
+
+imapsync \
+        --host1 imap.gmail.com --ssl1 --user1 gilles.lamiral@gmail.com \
+        --password1 "108687549524-gj68fg5ho5icoicv3v79dq2rcuf5c85e@developer.gserviceaccount.com;/g/var/pass/imapsync-xoauth2-15f8456ad5b7_notasecret.p12;notasecret" \
+        --host2 imap.gmail.com --ssl2 --user2 gilles.lamiral@gmail.com \
+        --password2 "108687549524-gj68fg5ho5icoicv3v79dq2rcuf5c85e@developer.gserviceaccount.com;/g/var/pass/imapsync-xoauth2-15f8456ad5b7_notasecret.p12" \
+        --justfoldersizes --nofoldersizes \
+        --authmech1 XOAUTH2 --authmech2 XOAUTH2 --debug
+
+Use your own xoauth2 values.
+
+See also
+http://www.notearthday.org/nedtech/2016/05/creating-creating-oauth2-credentials-with-google-apps/
+
+=======================================================================
+Q. How to use a proxy with XOAUTH2 authentication?
+
+With imapsync 1.670, you have to set two environment variables
+PERL_LWP_ENV_PROXY and https_proxy. Example:
+
+  PERL_LWP_ENV_PROXY=1 https_proxy=http://myproxy:8080/ imapsync --host1 ...
+
+With later release than 1.670, you have to set only the https_proxy
+environment variable, if it isn't already set. Example:
+
+  https_proxy=http://myproxy:8080/ imapsync --host1 ...
+
+
+=======================================================================
+Q. How to use XOAUTH to globally authenticate gmail users?
+
+R0. XOAUTH is considered obsolete and superseded by XOAUTH2
+    Anyway the manage part might be the same (I don't know).
+
+R1. The XOAUTH code and this FAQ item come from Eduardo Bortoluzzi
+    Thanks Eduardo!
+
+R2. In case you still have to use XOAUTH, here is the method:
+
+   The goal of OAUTH is to migrate all users from/to Google Apps 
+   Premier Edition without knowing their passwords.
+
+   The global password is available at the Google Apps control panel, 
+   at Advanced Tools -> Manage OAuth domain key.
+
+./imapsync \
+    --host1 imap.gmail.com --ssl1 \
+    --user1 foo@lab3.dedal.br \
+    --password1 secret1 \
+    --authmech1 XOAUTH \
+    --host2 imap.gmail.com --ssl2 \
+    --user2 bar@lab3.dedal.br \
+    --password2 secret2 \
+    --authmech2 XOAUTH
+
+Google Apps is a paid service, but you can try it for 30 days without any cost,
+or you could try, time goes on on free trial offers.
+
+Some notes about configuring the Google Apps XOAUTH:
+
+ On "Advanced Tools > Manage OAuth domain key > Two-legged OAuth access control" 
+    the "Allow access to all APIs" must be checked 
+    (https://support.google.com/a/bin/answer.py?answer=162105)
+
+ OR
+
+ On "Advanced Tools > Manage third party OAuth client access", 
+    the configured costumer key must have the scope 
+    "https://mail.google.com/" configured 
+    (https://support.google.com/a/bin/answer.py?answer=162106).
+
+=======================================================================
+=======================================================================
+

FAQ.d/FAQ.Yahoo.txt

@@ -0,0 +1,75 @@
+
+$Id: FAQ.Yahoo.txt,v 1.8 2018/05/24 11:34:30 gilles Exp gilles $
+
+This document is also available online at
+https://imapsync.lamiral.info/FAQ.d/
+https://imapsync.lamiral.info/FAQ.d/FAQ.Yahoo.txt
+
+
+=======================================================================
+                     Imapsync tips for Yahoo.
+=======================================================================
+
+
+=======================================================================
+Q. Synchronizing from Yahoo to XXX
+
+R. Use --host1 imap.mail.yahoo.com --ssl1
+
+./imapsync \
+    --host1 imap.mail.yahoo.com \
+    --user1 billy \
+    --password1 secret \
+    --ssl1 \
+    --host2 XXX \
+    --user2 billy \
+    --password2 secret \
+    --noabletosearch --errorsmax 10000 
+
+SSL is mandatory for yahoo since November 2011.
+
+Why increasing --errorsmax to 10000?
+Because during the sync you may encounter several lines like this one:
+- msg Inbox/12600 {0} S[36012] F[] I[27-Nov-2015 07:08:35 +0000] could not be fetched: 190 NO [UNAVAILABLE] UID FETCH Server error while fetching messages
+- msg Inbox/12600 skipped.
+I don't know why it happens, why Yahoo server says 
+"NO [UNAVAILABLE] UID FETCH Server error while fetching messages"
+Usually another run syncs the message successfully.
+
+Why --noabletosearch option?
+Yahoo IMAP does not honor well the SEARCH imap command (Dec 2017).
+So don't use the --search option.
+You can use --minage or/and --maxage but then add also --noabletosearch
+
+Yahoo bandwidth per connection is relatively low, 50 KiB/s to 500 KiB/s max, usually 100 KiB/s.
+Consider using --useuid to speed up large accounts.
+
+
+You also need to go to Yahoo, security and enable 
+"Allow less secure apps to login", 
+otherwise the login will not work. 
+
+To enable less secure apps to login:
+  * Login to the Yahoo mail account,
+  * click on the account name or the avatar and select "Account Info",
+  * click on "Account security",
+  * turn off "Two steps verification"
+  * turn on "Allow apps that use less secure authentication".​
+
+Thanks to Eugen Mayer for this last point.
+
+Another solution:
+
+  * Login to the Yahoo mail account,
+  * click on the account name or the avatar and select "Account Info",
+  * click on "Account security",
+  * Turn on "Two-step verification"
+  * Click on "Manage app passwords" and 
+    generate a specific password for imapsync, 
+	choose "Other app" at the bottom and type imapsync
+    since it is not in the predefined apps.
+  * Use this password with imapsync.
+
+
+=======================================================================
+=======================================================================

FAQ.d/FAQ.Yandex.txt

@@ -0,0 +1,26 @@
+#!/bin/cat
+$Id: FAQ.Yandex.txt,v 1.1 2019/09/12 10:08:05 gilles Exp gilles $
+
+This document is also available online at
+https://imapsync.lamiral.info/FAQ.d/
+https://imapsync.lamiral.info/FAQ.d/FAQ.Kerio.txt
+
+=======================================================================
+              Imapsync tips for Yandex accounts.
+=======================================================================
+
+
+
+
+=======================================================================
+Q. How to migrate from or to Yandex
+
+
+R. Use:
+
+  imapsync ... --useheader Message-Id --noabletosearch
+
+The option --noabletosearch is needed only if options --maxage or --minage
+are used. I don't know which --search commands could work, maybe none.
+
+The imap server for --host1 or --host2 is usually imap.yandex.ru

FAQ.d/FAQ.Zimbra.txt

@@ -0,0 +1,53 @@
+#!/bin/cat
+$Id: FAQ.Zimbra.txt,v 1.6 2019/06/25 00:15:16 gilles Exp gilles $
+
+This documentation is also available online at
+https://imapsync.lamiral.info/FAQ.d/
+https://imapsync.lamiral.info/FAQ.d/FAQ.Zimbra.txt
+
+
+=======================================================================
+      Imapsync tips for Zimbra. Specific issues and solutions.
+=======================================================================
+
+Please, don't follow
+https://wiki.zimbra.com/wiki/Guide_to_imapsync
+It's obsolete and it will give you, and me, more difficulties than 
+doing a standard sync without additional options.
+
+
+=======================================================================
+Q. From Zimbra to XXX
+
+  imapsync ... \
+        --exclude "Conversation Action Settings" \
+        --exclude "Quick Step Settings" \
+        --exclude "News Feed"
+
+=======================================================================
+Q. Zimbra disconnects without reason
+   Could not select: * BYE ... Zimbra IMAP4rev1 server closing connection
+
+R. The cause of this problem may be that some users have a subscription 
+   of a shared folder from a mailbox locked and so the shared folder.
+   The access problems may happen in a lot of folders, 
+   not only the shared/locked one.
+
+   It should work after removing the locked/shared folder.
+
+   Thanks to Danny Herrlitz for this input!
+
+=======================================================================
+Q. How to migrate from Zimbra with an admin account?
+
+R. Use:
+
+  imapsync ... --user1 "normal_user" --authuser1 "admin_user"  --password1 "admin_user_password"
+
+To setup or use a Zimbra admin user see:
+https://zimbra.github.io/adminguide/8.8.9/index.html#_administrator_accounts
+
+Thanks to Richard Street from thinkround for this tip.
+
+=======================================================================
+=======================================================================

FAQ.d/htaccess.txt

@@ -0,0 +1,62 @@
+
+# $Id: htaccess.txt,v 1.27 2019/12/08 16:05:27 gilles Exp gilles $
+
+
+AddDescription "<b>Back</b> to Imapsync main page."                     ..
+AddDescription "<b>Where this Description column comes from</b>."       htaccess.txt
+
+AddDescription "<b>APPEND errors</b>."                                  FAQ.Admin_Authentication.txt
+AddDescription "<b>Authenticate via an admin account</b>."              FAQ.APPEND_errors.txt
+AddDescription "<b>Archiving</b> tips."                                 FAQ.Archiving.txt
+AddDescription "<b>Authentication failures</b>."                        FAQ.Authentication_failure.txt
+AddDescription "<b>Big mailboxes</b> tips."                             FAQ.Big_Mailbox.txt
+AddDescription "<b>Changing folders names</b>."                         FAQ.Folders_Mapping.txt
+AddDescription "<b>Connection issues</b>."                              FAQ.Connection.txt
+AddDescription "<b>Contacts & Calendars & Chat issues</b>."             FAQ.Contacts_Calendars.txt
+AddDescription "<b>Dates issues</b>."                                   FAQ.Dates.txt
+AddDescription "<b>David Tobit</b> accounts."                           FAQ.David_Tobit.txt
+AddDescription "<b>Domino</b> accounts."                                FAQ.Domino.txt
+AddDescription "<b>Dovecot</b> accounts."                               FAQ.Dovecot.txt
+AddDescription "<b>Duplicated</b> messages issues."                     FAQ.Duplicates.txt
+AddDescription "<b>Emptying</b> an account."                            FAQ.Emptying.txt
+AddDescription "<b>Exchange 20xx</b> and <b>Office365</b> accounts."    FAQ.Exchange.txt
+AddDescription "<b>Selecting folders</b>."                              FAQ.Folders_Selection.txt
+AddDescription "<b>Folders sizes with Imapsync</b>."                    FAQ.Folders_Sizes.txt
+
+
+AddDescription "<b>Flags tips and issues</b>."                          FAQ.Flags.txt
+AddDescription "<b>General Data Protection Regulation</b> (GDPR)."      FAQ.GDPR.txt
+AddDescription "<b>General</b> and <b>pot-pourri</b> issues"            FAQ.General.txt
+AddDescription "<b>Gmail</b> accounts."                                 FAQ.Gmail.txt
+AddDescription "<b>ISP tips</b>."                                       FAQ.ISP.txt
+AddDescription "<b>Kerio</b> accounts."                                 FAQ.Kerio.txt
+AddDescription "<b>Massive/bulk migrations</b>."                        FAQ.Massive.txt
+AddDescription "<b>Memory issues</b>."                                  FAQ.Memory.txt
+AddDescription "<b>Migration Plan</b>."                                 FAQ.Migration_Plan.txt
+AddDescription "<b>The Online UI service Q&R</b>."                      FAQ.OnlineUI.txt
+AddDescription "<b>Password & special characters on Windows</b>."       FAQ.Passwords_on_Windows.txt
+AddDescription "<b>Password & special characters on Unix</b>."          FAQ.Passwords_on_Unix.txt
+AddDescription "<b>POP3 issues</b>."                                    FAQ.POP3.txt
+AddDescription "<b>Principles & design decisions</b>."                  FAQ.Principles.txt
+AddDescription "<b>Selecting messages</b>."                             FAQ.Messages_Selection.txt
+AddDescription "<b>How to transfer too big messages</b>."               FAQ.Messages_Too_Big.txt
+AddDescription "<b>Why the imapsync web site looks so old?</b>"         FAQ.Old_Style_Web_Design.txt
+AddDescription "<b>Oracle-UCS</b> accounts."                            FAQ.Oracle-UCS.txt
+
+AddDescription "<b>Checklist before release a new release</b>."         FAQ.Release_Checklist.txt
+AddDescription "<b>Guidelines to report bugs</b>."                      FAQ.Reporting_Bugs.txt
+AddDescription "<b>Security</b>."                                       FAQ.Security.txt
+AddDescription "<b>SSL errors</b>."                                     FAQ.SSL_errors.txt
+AddDescription "<b>SmarterMail</b> accounts."                           FAQ.SmarterMail.txt
+
+AddDescription "<b>TTL (Time To Live) delay in DNS configuration</b>."  FAQ.TTL.txt
+AddDescription "<b>Option --usecache and inodes</b>."                   FAQ.Use_cache.txt
+AddDescription "<b>User concurrent access</b>."                         FAQ.User_Concurrent_Access.txt
+AddDescription "<b>Virus scanners on Imapsync</b>."                     FAQ.Virus.txt
+AddDescription "<b>Why use --addheader?</b>."                           FAQ.Use_addheader.txt
+AddDescription "<b>Various imap software servers</b>."                  FAQ.Various_Software_Servers.txt
+AddDescription "<b>XOAUTH2</b> (<b>Gmail</b>)."                         FAQ.XOAUTH2.txt
+AddDescription "<b>Yahoo</b> accounts."                                 FAQ.Yahoo.txt
+AddDescription "<b>Yandex</b> accounts."                                FAQ.Yandex.txt
+AddDescription "<b>Zimbra</b> accounts."                                FAQ.Zimbra.txt
+

FAQ.d/memo

@@ -0,0 +1,4 @@
+
+
+( cd .. && make upload_FAQ )
+

INSTALL

@@ -0,0 +1 @@
+INSTALL.d/INSTALL.ANY.txt

INSTALL.d/.dockerignore

@@ -0,0 +1,4 @@
+
+#
+memo
+RCS

INSTALL.d/Dockerfile

@@ -0,0 +1,92 @@
+## Dockerfile for building a docker imapsync image
+
+# $Id: Dockerfile,v 1.28 2019/12/02 13:19:41 gilles Exp gilles $
+# I use the following command to build the image:
+#
+#  docker build -t gilleslamiral/imapsync . 
+#
+# where this Dockerfile is in the current directory
+# 
+# I like thanks
+# I like stars
+# I also like (and need) money
+# I thank you very much
+
+# Number of imapsync images pulled so far (2019_12_02): 32732
+# Command used:
+# curl -s https://hub.docker.com/v2/repositories/gilleslamiral/imapsync/ | jq '.pull_count'
+
+
+FROM debian:buster 
+
+LABEL   maintainer="Gilles LAMIRAL <gilles@lamiral.info>" \
+        description="Imapsync" \
+        documentation="https://imapsync.lamiral.info/#doc"
+
+# Put a copy of the Dockerfile in the image itself
+# It can help future maintenance, isn't it?
+
+COPY Dockerfile /
+
+# Also put my local imapsync on /usr/bin/ for testing purpose
+# renamed imapsync_local since would be erased by the wget
+
+COPY imapsync /usr/bin/imapsync_local
+COPY prerequisites_imapsync /usr/bin/prerequisites_imapsync_local
+
+RUN set -xe && \
+  apt-get update \
+  && apt-get install -y \
+  libauthen-ntlm-perl \
+  libcgi-pm-perl \
+  libcrypt-openssl-rsa-perl \
+  libdata-uniqid-perl \
+  libencode-imaputf7-perl \
+  libfile-copy-recursive-perl \
+  libfile-tail-perl        \
+  libio-socket-ssl-perl \
+  libio-socket-inet6-perl \
+  libio-tee-perl \
+  libhtml-parser-perl \
+  libjson-webtoken-perl \
+  libmail-imapclient-perl \
+  libparse-recdescent-perl \
+  libmodule-scandeps-perl \
+  libpar-packer-perl \
+  libreadonly-perl \
+  libregexp-common-perl \
+  libsys-meminfo-perl \
+  libterm-readkey-perl \
+  libtest-mockobject-perl \
+  libtest-pod-perl \
+  libunicode-string-perl \
+  liburi-perl  \
+  libwww-perl \
+  procps \
+  wget \
+  make \
+  cpanminus \
+  lsof \
+  && rm -rf /var/lib/apt/lists/*
+
+RUN set -xe \
+  && pwd \
+  && wget -N https://imapsync.lamiral.info/imapsync \
+     https://imapsync.lamiral.info/prerequisites_imapsync \
+  && mv imapsync /usr/bin/imapsync \
+  && chmod +x /usr/bin/imapsync /usr/bin/imapsync_local # just_a_comment_to_force_update 2019_11_26_12_58_34
+
+
+USER nobody:nogroup
+
+ENV HOME /var/tmp/
+
+WORKDIR /var/tmp/
+
+STOPSIGNAL SIGINT
+
+CMD ["/usr/bin/imapsync"]
+
+# 
+# End of imapsync Dockerfile 
+

INSTALL.d/INSTALL.ANY.txt

@@ -0,0 +1,194 @@
+# $Id: INSTALL.ANY.txt,v 1.60 2019/11/28 14:37:40 gilles Exp gilles $
+# 
+# This is the main INSTALL file for imapsync.
+# imapsync : IMAP sync and migrate tool.
+
+This documentation is also located online at 
+https://imapsync.lamiral.info/INSTALL.d/
+https://imapsync.lamiral.info/INSTALL.d/INSTALL.ANY.txt
+
+=======================================================================
+                        INTRODUCTION
+=======================================================================
+
+ imapsync works fine under any operating system with Perl and Perl modules (listed below).
+ imapsync.exe works fine standalone under Windows XP, Vista, Seven, 20XX, either 32 or 64bit.
+ imapsync_64bit.exe works fine standalone under Seven, 20XX, but only 64bit.
+ 
+=======================================================================
+               Installing imapsync on WINDOWS 
+=======================================================================
+
+Read the file README_Windows.txt
+Also available at
+https://imapsync.lamiral.info/README_Windows.txt
+
+
+=======================================================================
+               Installing imapsync on Unix 
+=======================================================================
+
+There are specific INSTALL files in the imapsync directory INSTALL.d/ 
+Those documents are also available at https://imapsync.lamiral.info/INSTALL.d/
+
+- Mac OS X
+- FreeBSD
+- CentOS
+- CPanel
+- Debian
+- Ubuntu
+- AWS EC2
+- Arch Linux
+- Docker
+- Online UI like /X
+
+If you are not on one of these systems then read the last section
+below called "Installing imapsync on other Unixes".
+
+=======================================================================
+               Installing imapsync on Mac OS X 
+=======================================================================
+
+Easy.
+Read the file INSTALL.d/INSTALL.Darwin.txt
+This document is also available at
+https://imapsync.lamiral.info/INSTALL.d/INSTALL.Darwin.txt
+
+=======================================================================
+               Installing imapsync on FreeBSD 
+=======================================================================
+
+Easy.
+Read the file INSTALL.d/INSTALL.FreeBSD.txt
+This document is also available at
+https://imapsync.lamiral.info/INSTALL.d/INSTALL.FreeBSD.txt
+
+
+=======================================================================
+               Installing imapsync on CentOS 
+=======================================================================
+
+Easy.
+Read the file INSTALL.d/INSTALL.Centos.txt
+This document is also available at
+https://imapsync.lamiral.info/INSTALL.d/INSTALL.Centos.txt
+
+
+=======================================================================
+               Installing imapsync on CPanel 
+=======================================================================
+
+Easy.
+Read the file INSTALL.d/INSTALL.CPanel.txt
+This document is also available at
+https://imapsync.lamiral.info/INSTALL.d/INSTALL.CPanel.txt
+
+
+=======================================================================
+               Installing imapsync on Debian 6 or 7 
+=======================================================================
+
+Not so easy.
+See the file INSTALL.d/INSTALL.Debian.txt
+This document is also available at
+https://imapsync.lamiral.info/INSTALL.d/INSTALL.Debian.txt
+
+=======================================================================
+               Installing imapsync on Ubuntu 12 or 14 
+=======================================================================
+
+Not so easy.
+See the file INSTALL.d/INSTALL.Ubuntu.txt
+This document is also available at
+https://imapsync.lamiral.info/INSTALL.d/INSTALL.Ubuntu.txt
+
+=======================================================================
+               Installing imapsync on AWS EC2 
+=======================================================================
+
+Not so easy.
+See the file INSTALL.d/INSTALL.AWS_EC2.txt
+This document is also available at
+https://imapsync.lamiral.info/INSTALL.d/INSTALL.AWS_EC2.txt
+
+=======================================================================
+               Installing imapsync on ArchLinux
+=======================================================================
+
+Not so easy.
+See the file INSTALL.d/INSTALL.ArchLinux.txt
+This document is also available at
+https://imapsync.lamiral.info/INSTALL.d/INSTALL.ArchLinux.txt
+
+=======================================================================
+               Installing imapsync online like /X 
+=======================================================================
+
+Follow the document INSTALL.d/INSTALL.OnlineUI.txt
+This document is also available at
+https://imapsync.lamiral.info/INSTALL.d/INSTALL.OnlineUI.txt
+
+
+=======================================================================
+               Installing imapsync on other Unixes
+=======================================================================
+
+
+Purchase imapsync at
+https://imapsync.lamiral.info/
+or get it anywhere.
+
+You have access to a compressed tarball called imapsync-1.xxx.tgz
+where 1.xxx is the version number. Untar the tarball where
+you want:
+
+  cd 
+  tar xzvf  imapsync-1.xxx.tgz
+
+Go into the directory imapsync-1.xxx
+
+  cd imapsync-1.xxx
+
+You can easily detect any missing Perl modules via the 
+script prerequisites_imapsync located in the INSTALL.d directory:
+
+  sh INSTALL.d/prerequisites_imapsync
+
+or 
+
+  cd INSTALL.d/
+  sh prerequisites_imapsync
+
+You don't need to be root to run the previous command. You have
+to be root if you want the Perl modules to be available for the 
+whole system, for all users.
+
+You may be in one of following cases: 
+- you are not root.
+- you are in a environment where modifying system Perl 
+  modules can break other things or where you're not allowed to
+  change the whole system.
+
+The "make" command is a prerequisite to build some Perl modules.
+Install make in case it is not already installed.
+
+Run the "cpanm" command with the missing Perl modules as arguments.
+For example it can be:
+
+  cpanm Authen::NTLM Data::Uniqid File::Copy::Recursive IO::Tee \
+        Mail::IMAPClient Unicode::String Encode::IMAPUTF7
+
+Once you've run the "cpanm" command, you can rerun "sh prerequisites_imapsync" 
+to verify everything is ok:
+
+  sh prerequisites_imapsync 
+
+When everything is ok the script execution ends with this sentence
+"All needed modules are already installed"
+
+Now imapsync should work on your system. To check it run:
+
+  ./imapsync --testslive
+
+=======================================================================
+=======================================================================

INSTALL.d/INSTALL.AWS_EC2.txt

@@ -0,0 +1,68 @@
+#!/bin/cat 
+# $Id: INSTALL.AWS_EC2.txt,v 1.7 2019/11/28 14:37:23 gilles Exp gilles $
+
+This documentation is also located online at 
+https://imapsync.lamiral.info/INSTALL.d/
+https://imapsync.lamiral.info/INSTALL.d/INSTALL.AWS_EC2.txt
+
+=======================================================================
+               Installing imapsync on AWS EC2
+=======================================================================
+
+AWS: Amazon Web Service
+
+cat /etc/system-release
+Amazon Linux AMI release 2017.03
+
+
+sudo yum install  \
+perl-Class-Load   \
+perl-IO-Compress  \
+perl-Crypt-OpenSSL-RSA   \
+perl-Data-Dumper         \
+perl-Dist-CheckConflicts \
+perl-ExtUtils-Embed      \
+perl-File-Copy-Recursive \
+perl-File-Tail       \
+perl-IO-Socket-INET6 \
+perl-IO-Socket-SSL   \
+perl-JSON            \
+perl-HTML-Parser     \
+perl-libwww-perl     \
+perl-Mail-IMAPClient \
+perl-Module-Implementation \
+perl-Module-Runtime   \
+perl-Module-ScanDeps  \
+perl-Net-SSLeay       \
+perl-Package-Stash    \
+perl-Package-Stash-XS \
+perl-Parse-RecDescent \
+perl-Readonly         \
+perl-Regexp-Common    \
+perl-Sys-MemInfo      \
+perl-TermReadKey      \
+perl-Test-Fatal       \
+perl-Test-MockObject  \
+perl-Test-Simple      \
+perl-Test-Pod         \
+perl-Test-Requires    \ 
+perl-Try-Tiny         \
+perl-Unicode-String   \
+perl-URI              \
+cpanminus
+
+sudo cpanm Authen::NTLM Data::Uniqid IO::Tee \
+     JSON::WebToken JSON::WebToken::Crypt::RSA \
+     Test::Mock::Guard \
+     Encode::IMAPUTF7
+
+wget -N https://imapsync.lamiral.info/imapsync
+
+chmod +x imapsync
+
+./imapsync
+
+./imapsync --testslive
+
+=======================================================================
+=======================================================================

INSTALL.d/INSTALL.ArchLinux.txt

@@ -0,0 +1,94 @@
+#!/bin/cat 
+# $Id: INSTALL.ArchLinux.txt,v 1.5 2019/11/28 14:37:59 gilles Exp gilles $
+
+This documentation is also located online at 
+https://imapsync.lamiral.info/INSTALL.d/
+https://imapsync.lamiral.info/INSTALL.d/INSTALL.ArchLinux.txt
+
+==========================================
+===  Installing imapsync on ArchLinux  ===
+==========================================
+
+Thanks to Aldo Villagra!
+
+---------------------------------
+With yaourt and AUR repositories
+---------------------------------
+
+  pacman -S --needed  base-devel git
+
+  git clone https://aur.archlinux.org/package-query.git
+  cd package-query
+  makepkg -si
+  cd ..
+  git clone https://aur.archlinux.org/yaourt.git
+  cd yaourt
+  makepkg -si
+  cd ..
+
+After you have installed Yaourt, you can install imapsync:
+
+  yaourt -S --needed imapsync
+
+That's all folks!
+
+-----------------------------------------------
+With the "pacman" and the standard repositories
+community/
+extra/
+-----------------------------------------------
+
+Commands to run:
+
+  pacman -S --needed make lsb-release cpanminus wget
+  
+  pacman -S --needed community/perl-cgi \
+   extra/perl-crypt-openssl-rsa \
+   extra/perl-data-uniqid \
+   extra/perl-digest-hmac \
+   community/perl-dist-checkconflicts \
+   extra/perl-file-copy-recursive \
+   extra/perl-io-socket-inet6 \
+   extra/perl-io-socket-ssl \
+   community/perl-io-tee \
+   community/perl-json \
+   extra/perl-html-parser \
+   extra/perl-libwww \
+   community/perl-module-implementation \
+   community/perl-module-runtime \
+   community/perl-module-scandeps \
+   extra/perl-net-ssleay \
+   community/perl-package-stash \
+   community/perl-package-stash-xs \
+   community/perl-parse-recdescent \
+   community/perl-readonly \
+   community/perl-regexp-common \
+   extra/perl-term-readkey \
+   community/perl-test-fatal \
+   community/perl-test-mockobject \
+   extra/perl-test-pod \
+   community/perl-test-requires \
+   community/perl-test-nowarnings \
+   community/perl-test-deep \
+   extra/perl-try-tiny \
+   extra/perl-uri \
+   community/perl-file-tail
+
+Mandatory Perl modules via cpanm:
+
+  cpanm Mail::IMAPClient \
+   Unicode::String \
+   Sys::MemInfo \
+   Encode::IMAPUTF7
+
+Other Perl modules, needed sometimes:
+
+  cpanm Authen::NTLM  \
+   JSON::WebToken \
+   JSON::WebToken::Crypt::RSA \
+   Test::Mock::Guard \
+   Test::Warn \
+   PAR::Packer
+
+  
+  

INSTALL.d/INSTALL.CPanel.txt

@@ -0,0 +1,37 @@
+#!/bin/cat 
+# $Id: INSTALL.CPanel.txt,v 1.7 2019/11/28 14:38:18 gilles Exp gilles $
+
+This documentation is also located online at 
+https://imapsync.lamiral.info/INSTALL.d/ 
+https://imapsync.lamiral.info/INSTALL.d/INSTALL.CPanel.txt
+
+=======================================================================
+               Installing imapsync on CPanel
+=======================================================================
+
+This procedure has been tested on cPanel 11.36 (64 bits).
+It should be the same for any Cpanel distribution based on Centos.
+
+First install access to the Epel repository via yum:
+
+  yum install epel-release
+
+Then install imapsync and its dependencies:
+
+  yum install imapsync
+
+  
+After installing imapsync, it should be able to work on your system.
+A good test that shows also the basic example:
+
+  imapsync
+
+
+If you want to update to the latest imapsync, then look at
+the Centos installation document called INSTALL.Centos.txt
+and also INSTALL.ANY.txt 
+
+You're on your own, I don't have access to a CPanel system.
+
+=======================================================================
+=======================================================================

INSTALL.d/INSTALL.Centos.txt

@@ -0,0 +1,163 @@
+#!/bin/cat 
+# $Id: INSTALL.Centos.txt,v 1.14 2019/11/28 14:37:02 gilles Exp gilles $
+
+This documentation is also located online at 
+https://imapsync.lamiral.info/INSTALL.d/
+https://imapsync.lamiral.info/INSTALL.d/INSTALL.Centos.txt
+
+=======================================================================
+               Installing imapsync on CentOS
+=======================================================================
+
+There is one section for Centos 7 and one for Centos 6.
+
+=======================================================================
+               Centos 7
+=======================================================================
+
+First install access to the Epel repository via yum:
+
+  yum install epel-release
+
+Then install imapsync and its dependencies:
+
+  yum install imapsync
+
+After installing imapsync, it should be able to work on your system.
+A good test that shows also the basic example:
+
+  imapsync
+
+A live test:
+
+  imapsync --testslive
+  
+Unit tests:
+
+  imapsync --tests
+
+=======================================================================
+               Centos 7 and latest imapsync
+=======================================================================
+
+At the time of this writing (April 2018), the epel repository contains 
+imapsync release 1.727, which is not the latest available release.
+
+In order to install the latest imapsync I suggest the following process:
+
+Install the epel imapsync 1.727 release via yum like mentioned above.
+It will install many needed packages, Perl itself and Perl modules 
+for release 1.727. The latest imapsync needs more Perl modules.
+
+Then:
+
+  yum install perl-App-cpanminus \
+ perl-Dist-CheckConflicts \
+ perl-HTML-Parser \
+ perl-libwww-perl \
+ perl-Module-Implementation \
+ perl-Module-ScanDeps \
+ perl-Package-Stash \
+ perl-Package-Stash-XS \
+ perl-PAR-Packer \
+ perl-Regexp-Common \
+ perl-Sys-MemInfo \
+ perl-Test-Fatal \
+ perl-Test-Mock-Guard \
+ perl-Test-Requires \
+ perl-Test-Deep \
+ perl-File-Tail \
+ perl-Unicode-String
+
+  cpanm Encode::IMAPUTF7 # this module is not available as a rpm package
+  
+  wget -N https://imapsync.lamiral.info/imapsync
+  chmod +x imapsync
+  ./imapsync --testslive
+
+Now you should shave the latest imapsync locally working on Centos 7.
+
+If you want to install it and replace the old one:
+
+  mv /usr/bin/imapsync  /usr/bin/imapsync_old
+  cp ./imapsync /usr/bin/imapsync
+
+  imapsync --version
+
+should give the latest release number instead of 1.727
+(It is 1.964 at the time of this writing)
+
+If you want to install an online imapsync service
+like /X then you also need a recent decent CGI.pm,
+add it with cpanm:
+
+  cpanm CGI 
+
+
+=======================================================================
+               Centos 6
+=======================================================================
+
+This section has been tested with imapsync release 1.670
+
+First, install access to the Epel repository
+ 
+  wget http://dl.fedoraproject.org/pub/epel/6/i386/epel-release-6-8.noarch.rpm
+  rpm -Uvh epel-release-6-8.noarch.rpm
+
+Then install imapsync and its dependencies:
+
+ yum install imapsync
+
+After installing imapsync, it should be able to work on your system.
+A good test that shows also the basic example:
+
+  imapsync
+
+A live test:
+
+  imapsync --testslive
+  
+Unit tests:
+
+  imapsync --tests
+
+=======================================================================
+               Centos 6 and latest imapsync
+=======================================================================
+
+Install the epel imapsync 1.670 release via yum like mentioned above.
+
+It will install many needed packages, Perl itself and Perl modules 
+for release 1.670. The latest imapsync needs more Perl modules.
+
+Then:
+
+  yum install perl-App-cpanminus \
+ perl-Dist-CheckConflicts \
+ perl-HTML-Parser \
+ perl-libwww-perl \
+ perl-Module-Implementation \
+ perl-Module-ScanDeps \
+ perl-Package-Stash \
+ perl-Package-Stash-XS \
+ perl-PAR-Packer \
+ perl-Regexp-Common \
+ perl-Sys-MemInfo \
+ perl-Test-Fatal \
+ perl-Test-Mock-Guard \
+ perl-Test-Requires \
+ perl-Test-Deep \
+ perl-File-Tail \
+ perl-Unicode-String
+
+  wget https://imapsync.lamiral.info/imapsync
+
+  chmod +x imapsync
+  ./imapsync --testslive
+
+Now you have the latest imapsync on Centos 6, 
+do you?
+
+=======================================================================
+=======================================================================

INSTALL.d/INSTALL.Darwin.txt

@@ -0,0 +1,198 @@
+#!/bin/cat
+# $Id: INSTALL.Darwin.txt,v 1.24 2019/11/28 14:42:52 gilles Exp gilles $
+
+This documentation is also located online at 
+https://imapsync.lamiral.info/INSTALL.d/
+https://imapsync.lamiral.info/INSTALL.d/INSTALL.Darwin.txt
+
+=======================================================================
+               Installing imapsync binary on Darwin / Mac OS X
+=======================================================================
+
+Caveat Catalina: The binary imapsync_bin_Darwin is detected as a malware
+or similar on the latest Mac OS X named Catalina.
+It's Catalina new security policy. I'm working on it.
+All other Mac OS X releases are ok.
+So far I found 
+https://www.quora.com/What-does-Can-t-be-opened-because-it-s-integrity-cannot-be-verified-mean-on-OSX-Catalina
+https://github.com/fastlane/fastlane/issues/15186#issuecomment-532047545
+https://github.com/neovim/neovim/issues/11011#issuecomment-531369505
+Other way, on the binary: Control + Right Click -> Open 
+(I don't know if it adds imapsync in the ok apps)
+See also the last section of https://support.apple.com/en-us/HT202491
+"How to open an app that hasn’t been notarized or is from an unidentified developer"
+
+Now, let's forget Catalina for the rest of this document 
+
+There is a standalone imapsync binary for Mac OS X 
+called "imapsync_bin_Darwin" (without the quotes),
+available in the compressed tarball called imapsync-1.xxx.tgz
+where 1.xxx is the version number. I suppose this tarball is put
+under your $HOME directory, let say /Users/gilles/, but you can
+put it anywhere.
+
+Open a terminal: /Applications/Utilities/Terminal double-click on Terminal.
+
+Untar the tarball where you want:
+
+  cd
+  tar xzvf  /Users/gilles/imapsync-1.xxx.tgz
+
+Go into the directory imapsync-1.xxx
+
+  cd imapsync-1.xxx
+
+
+First let's have a simple run to see if imapsync_bin_Darwin works. 
+You should see some help about options and an example at the end 
+of this run:
+
+  ./imapsync_bin_Darwin
+
+To go further, perform a complete test with two
+real IMAP server accounts:  
+  
+  ./imapsync_bin_Darwin --testslive
+
+If this sync works fine then imapsync_bin_Darwin is ready for any 
+imap account synchronization. 
+
+When reading the documentation with imapsync command lines examples, 
+you have to replace the command "imapsync" by "imapsync_bin_Darwin"
+For example, instead of the command:
+
+  ./imapsync \
+    --host1 test1.lamiral.info --user1 test1 --password1 secret1 \
+    --host2 test2.lamiral.info --user2 test2 --password2 secret2
+
+you have to use:
+
+  ./imapsync_bin_Darwin \
+    --host1 test1.lamiral.info --user1 test1 --password1 secret1 \
+    --host2 test2.lamiral.info --user2 test2 --password2 secret2
+
+You also may have to edit the examples you use, like
+examples/imapsync_example.sh
+and replace in there the command ./imapsync by ./imapsync_bin_Darwin
+in case it is not already done.
+
+Be careful the way you edit the files, use a text editor. 
+Do not use a word processor because word processors add 
+or use special formating characters that will break the shell
+scripts. If you use TextEdit, use the text mode.
+
+
+The script examples/imapsync_example_darwin.sh is ready to use,
+it is a copy of examples/imapsync_example.sh adapted to Mac users.
+
+The script examples/sync_loop_darwin.sh is also ready to use.
+Try:
+
+  sh examples/sync_loop_darwin.sh
+
+or
+
+  cp examples/sync_loop_darwin.sh mysync.sh
+  sh mysync.sh
+
+Now read on the tutorial
+https://imapsync.lamiral.info/doc/TUTORIAL_Unix.html
+
+=======================================================================
+    Installing imapsync script on Darwin / Mac OS X with brew
+=======================================================================
+
+In case you have brew installed on your system ( see https://brew.sh/ ),
+install imapsync with the command:
+
+  brew install imapsync
+  
+Do a real test with imap server test.lamiral.info:
+
+  imapsync --testslive
+  
+
+=======================================================================
+    Installing imapsync script on Darwin / Mac OS X the way I do
+=======================================================================
+
+This part is only for advanced Unix users, or brave users.
+
+The "make" command is a prerequisite to build some Perl modules.
+Install make in case it is not already installed.
+
+First let us install cpanminus locally in ~/perl5
+
+  wget --no-check-certificate -O- http://cpanmin.us | perl - -l ~/perl5 App::cpanminus local::lib
+
+Then take this install into account in the current environment
+
+  eval `perl -I ~/perl5/lib/perl5 -Mlocal::lib`
+  perl -I ~/perl5/lib/perl5 -Mlocal::lib
+
+If you want to have always this setting in your environment then run the commands
+  
+  echo 'eval `perl -I ~/perl5/lib/perl5 -Mlocal::lib`' >> ~/.profile
+  echo 'export MANPATH=$HOME/perl5/man:$MANPATH' >> ~/.profile
+  cat ~/.profile 
+
+Now let's update the standard CPAN Perl module
+
+  cpanm CPAN
+
+The specific install part for imapsync begins, the script "prerequisites_imapsync"
+helps to verify what is needed to install on your system
+
+  curl -L http://imapsync.lamiral.info/INSTALL.d/prerequisites_imapsync > prerequisites_imapsync 
+  sh prerequisites_imapsync
+
+  cpanm Authen::NTLM
+  cpanm File::Copy::Recursive IO::Tee
+  cpanm Mail::IMAPClient
+  cpanm Readonly
+  cpanm Unicode::String
+  cpanm Data::Uniqid
+  cpanm JSON::WebToken
+
+We're ready to install and test the latest imapsync
+
+  wget -c http://imapsync.lamiral.info/imapsync
+  ./imapsync
+  ./imapsync --modules
+
+You can rerun "sh prerequisites_imapsync" 
+to verify everything is ok:
+
+  sh prerequisites_imapsync 
+
+When everything is ok the script execution ends with this sentence
+"All needed modules are already installed"
+
+Now imapsync should work on your system.
+
+  ./imapsync --testslive
+
+=======================================================================
+               Building imapsync binary on Darwin / Mac OS X
+=======================================================================
+
+cpanm Module::ScanDeps
+cpanm PAR::Packer
+
+pp -o imapsync.bin imapsync 
+
+./imapsync.bin 
+./imapsync.bin  --testslive
+./imapsync.bin  --tests
+./imapsync.bin  --module
+
+
+=======================================================================
+               Installing imapsync Mac OS X Leopard
+=======================================================================
+
+Mac OS X Leopard has perl 5.8.8 and an old openssl version.
+
+
+=======================================================================
+=======================================================================

INSTALL.d/INSTALL.Debian.txt

@@ -0,0 +1,254 @@
+#!/bin/cat 
+# $Id: INSTALL.Debian.txt,v 1.30 2019/11/28 14:36:18 gilles Exp gilles $
+
+This documentation is also located online at 
+https://imapsync.lamiral.info/INSTALL.d/
+https://imapsync.lamiral.info/INSTALL.d/INSTALL.Debian.txt
+
+
+There is three install sections in this document,
+one for Debian 9 Stretch and Debian 10 Buster
+one for Debian 8 Jessie
+one for Debian 7 Wheezy
+
+First a call to Debian packagers
+Why imapsync is not in Debian as a package?
+Imapsync used to be in Debian from 2005-04-25 (release 1.125) to 2011-01-25 (release 1.315).
+It could be in Debian nowadays, as always, my last words on this discussion were 
+"Do what you want, I promise I won't complain anymore about the fact imapsync is on Debian or not."
+https://lists.debian.org/debian-legal/2011/01/msg00058.html
+The license is now "No limits to do anything with this work and this license".
+Feel free.
+See also a more detailed story at
+https://lists.debian.org/debian-user/2016/11/msg00849.html
+
+
+=======================================================================
+     Installing imapsync on Debian 9 Stretch or Debian 10 Buster
+=======================================================================
+
+How to install imapsync dependencies on a Debian system?
+
+The repositories are the classical ones, ie, a
+/etc/apt/sources.list file with:
+
+# Debian 9 Stretch
+deb http://deb.debian.org/debian stretch main contrib
+
+or
+
+# Debian 10 Buster
+deb http://deb.debian.org/debian buster main contrib
+
+
+You need root privilege to run it, be root or use sudo.
+
+apt install -y            \
+  libauthen-ntlm-perl     \
+  libcgi-pm-perl          \
+  libcrypt-openssl-rsa-perl   \
+  libdata-uniqid-perl         \
+  libencode-imaputf7-perl     \
+  libfile-copy-recursive-perl \
+  libfile-tail-perl        \
+  libio-socket-inet6-perl  \
+  libio-socket-ssl-perl    \
+  libio-tee-perl           \
+  libhtml-parser-perl      \
+  libjson-webtoken-perl    \
+  libmail-imapclient-perl  \
+  libparse-recdescent-perl \
+  libmodule-scandeps-perl  \
+  libreadonly-perl         \
+  libregexp-common-perl    \
+  libsys-meminfo-perl      \
+  libterm-readkey-perl     \
+  libtest-mockobject-perl  \
+  libtest-pod-perl         \
+  libunicode-string-perl   \
+  liburi-perl              \
+  libwww-perl              \
+  libtest-nowarnings-perl  \
+  libtest-deep-perl        \
+  libtest-warn-perl        \
+  make                     \
+  cpanminus
+
+
+After installing the dependencies, imapsync should be working,
+go to the section "After installing the dependencies" below.
+
+
+=======================================================================
+             Installing imapsync on Debian 8 Jessie 
+=======================================================================
+
+How to install imapsync dependencies on a Debian system?
+
+You need root priviledge.
+
+The first command installs standard Debian packages:
+apt install           \
+  libauthen-ntlm-perl \
+  libcgi-pm-perl      \
+  libcrypt-openssl-rsa-perl   \
+  libdata-uniqid-perl         \
+  libencode-imaputf7-perl     \
+  libfile-copy-recursive-perl \
+  libfile-tail-perl        \
+  libio-socket-inet6-perl  \
+  libio-socket-ssl-perl    \
+  libio-tee-perl           \
+  libhtml-parser-perl      \
+  libmail-imapclient-perl  \
+  libparse-recdescent-perl \
+  libmodule-scandeps-perl  \
+  libreadonly-perl         \
+  libterm-readkey-perl     \
+  libtest-mockobject-perl  \
+  libtest-pod-perl         \
+  libunicode-string-perl   \
+  liburi-perl              \
+  libwww-perl              \
+  libregexp-common-perl    \
+  libtest-nowarnings-perl  \
+  libtest-deep-perl        \
+  libtest-warn-perl        \
+  make                     \
+  cpanminus
+
+The package libdata-uniqid-perl is in the jessie-backports repository
+https://packages.debian.org/fr/jessie-backports/libdata-uniqid-perl
+
+Here is how to add jessie-backports repository in /etc/apt/sources.list
+
+https://backports.debian.org/Instructions/
+
+If you can't add the jessie-backports repository in /etc/apt/sources.list you
+have to install Perl module Data::Uniqid with cpanm:
+
+  cpanm  Data::Uniqid
+
+The following second command installs "manually" the Perl module Sys::MemInfo
+because Debian 8 Jessie doesn't have this Perl module available via a package 
+(but Debian 9 Stretch does):
+
+  cpanm Sys::MemInfo 
+
+The following optional cpanm command updates Perl module Mail::IMAPClient
+because it is good to be up to date with that imapsync dependency,
+but it is not mandatory since Mail::IMAPClient is installed by
+the Debian package libmail-imapclient-perl:
+
+  cpanm Mail::IMAPClient
+
+Last, in case you need to use XOAUTH2 authentication you have to install   
+the module JSON::WebToken with the command:
+
+  cpanm JSON::WebToken
+
+After installing the dependencies, imapsync should be working,
+go to the section "After installing the dependencies" below.
+
+
+=======================================================================
+               Installing imapsync on Debian 7 Wheezy 
+=======================================================================
+
+How to install imapsync dependencies on a Debian system?
+
+You need root priviledge to run the commands.
+
+The first command installs standard Debian packages:
+
+apt-get install    \
+  libauthen-ntlm-perl  \
+  libclass-load-perl   \
+  libcrypt-openssl-rsa-perl \
+  libdigest-hmac-perl  \
+  libencode-imaputf7-perl     \
+  libfile-copy-recursive-perl \
+  libfile-tail-perl        \
+  libio-compress-perl     \
+  libio-socket-inet6-perl \
+  libio-socket-ssl-perl   \
+  libio-tee-perl          \
+  libmail-imapclient-perl \
+  libmodule-implementation-perl \
+  libmodule-runtime-perl  \
+  libmodule-scandeps-perl \
+  libpackage-stash-perl   \
+  libpackage-stash-xs-perl \
+  libpar-packer-perl      \
+  libreadonly-perl        \
+  libterm-readkey-perl    \
+  libtest-fatal-perl      \
+  libtest-pod-perl        \
+  libtest-requires-perl   \
+  libtest-simple-perl     \
+  libunicode-string-perl  \
+  liburi-perl             \
+  make                    \
+  cpanminus
+
+
+The following second command installs "manually" the Perl modules 
+Data::Uniqid
+Sys::MemInfo
+because Debian hasn't made them available via a package yet.
+This cpanm command  also installs manually Perl module Mail::IMAPClient
+because it is good to be up to date with that imapsync dependency,
+but it is not mandatory since Mail::IMAPClient is installed by
+the Debian package libmail-imapclient-perl:
+
+  cpanm Data::Uniqid  Sys::MemInfo
+  
+In case you want to update the Perl module Mail::IMAPClient,
+a major module for imapsync, but an old March 2012 release 3.31 in Wheezy, 
+the following command updates it "manually":
+
+  cpanm Mail::IMAPClient
+
+Last, in case you need to use XOAUTH2 authentication you have to install   
+the module JSON::WebToken with the command:
+
+  cpanm JSON::WebToken
+
+
+After installing the dependencies, imapsync should be working.
+
+=======================================================================
+                 After installing the dependencies
+=======================================================================
+
+You don't have to be root to test and use imapsync.
+
+Take imapsync either on github or at the upstream site.
+
+Add execution permission to the downloaded script:
+
+  chmod +x imapsync
+  
+Check the dependencies and print also the basic example:
+
+  ./imapsync
+
+Perform a live test showing imapsync job:
+
+  ./imapsync --testslive
+
+Now install imapsync on the system (need root priviledges again):
+
+  cp imapsync /usr/bin/
+
+That's finished for the installation part.
+You can now use imapsync without knowing where it is located
+on the system:
+
+  imapsync 
+
+Now go to read http://imapsync.lamiral.info/#doc
+start with the tutorial.
+
+=======================================================================
+=======================================================================

INSTALL.d/INSTALL.Docker_build.txt

@@ -0,0 +1,107 @@
+#!/bin/cat 
+# $Id: INSTALL.Docker_build.txt,v 1.12 2019/11/28 14:43:48 gilles Exp gilles $
+
+This documentation is also located online at 
+https://imapsync.lamiral.info/INSTALL.d/
+https://imapsync.lamiral.info/INSTALL.d/INSTALL.Docker_build.txt
+
+=======================================================================
+               Building an imapsync docker image from Debian
+=======================================================================
+
+Nearly verbatim copy from https://imapsync.lamiral.info/INSTALL.d/Dockerfile 
+(nearly but the Dockerfile rcs tag Id: removed, that would conflict)
+
+## Dockerfile for building a docker imapsync image
+
+# Dockerfile,v 1.26 2019/11/27 15:49:13 gilles Exp gilles $
+# I use the following command to build the image:
+#
+#  docker build -t gilleslamiral/imapsync . 
+#
+# where this Dockerfile is in the current directory
+# 
+# I like thanks
+# I like stars
+# I also like (and need) money
+# I thank you very much in advance
+
+
+FROM debian:buster 
+
+LABEL   maintainer="Gilles LAMIRAL <gilles@lamiral.info>" \
+        description="Imapsync" \
+        documentation="https://imapsync.lamiral.info/#doc"
+
+# Put a copy of the Dockerfile in the image itself
+# It can help future maintenance, isn't it?
+
+COPY Dockerfile /
+
+# Also put my local imapsync on /usr/bin/ for testing purpose
+# renamed imapsync_local since would be erased by the wget
+
+COPY imapsync /usr/bin/imapsync_local
+COPY prerequisites_imapsync /usr/bin/prerequisites_imapsync_local
+
+RUN set -xe && \
+  apt-get update \
+  && apt-get install -y \
+  libauthen-ntlm-perl \
+  libcgi-pm-perl \
+  libcrypt-openssl-rsa-perl \
+  libdata-uniqid-perl \
+  libencode-imaputf7-perl \
+  libfile-copy-recursive-perl \
+  libfile-tail-perl        \
+  libio-socket-ssl-perl \
+  libio-socket-inet6-perl \
+  libio-tee-perl \
+  libhtml-parser-perl \
+  libjson-webtoken-perl \
+  libmail-imapclient-perl \
+  libparse-recdescent-perl \
+  libmodule-scandeps-perl \
+  libpar-packer-perl \
+  libreadonly-perl \
+  libregexp-common-perl \
+  libsys-meminfo-perl \
+  libterm-readkey-perl \
+  libtest-mockobject-perl \
+  libtest-pod-perl \
+  libunicode-string-perl \
+  liburi-perl  \
+  libwww-perl \
+  procps \
+  wget \
+  make \
+  cpanminus \
+  lsof \
+  && rm -rf /var/lib/apt/lists/*
+
+RUN set -xe \
+  && pwd \
+  && wget -N https://imapsync.lamiral.info/imapsync \
+     https://imapsync.lamiral.info/prerequisites_imapsync \
+  && mv imapsync /usr/bin/imapsync \
+  && chmod +x /usr/bin/imapsync /usr/bin/imapsync_local # just_a_comment_to_force_update 2019_11_26_12_58_34
+
+
+USER nobody:nogroup
+
+ENV HOME /var/tmp/
+
+WORKDIR /var/tmp/
+
+STOPSIGNAL SIGINT
+
+CMD ["/usr/bin/imapsync"]
+
+# 
+# End of imapsync Dockerfile 
+
+
+
+
+=======================================================================
+=======================================================================

INSTALL.d/INSTALL.FreeBSD.txt

@@ -0,0 +1,36 @@
+#!/bin/cat 
+# $Id: INSTALL.FreeBSD.txt,v 1.11 2019/11/28 14:38:42 gilles Exp gilles $
+
+This documentation is also located online at 
+https://imapsync.lamiral.info/INSTALL.d/
+https://imapsync.lamiral.info/INSTALL.d/INSTALL.FreeBSD.txt
+
+=======================================================================
+               Installing imapsync on FreeBSD
+=======================================================================
+
+Thanks to Kurt Jaeger pi@FreeBSD.org a imapsync package is available in FreeBSD  
+http://portsmon.freebsd.org/portoverview.py?category=mail&portname=imapsync
+So, to install imapsync you just have to type one command in a terminal:
+
+  sudo pkg install imapsync
+
+or if you're already root on the console:
+
+  pkg install imapsync
+ 
+Tested 7 March 2015 on FreeBSD 10.1-RELEASE
+Tested 2 July  2018 on FreeBSD 11.2-RELEASE
+
+=======================================================================
+=======================================================================
+
+In order to install and be able to run latest imapsync online /X, 
+install also:
+p5-Regexp-Common
+p5-Test-MockObject
+p5-CGI
+p5-Encode-IMAPUTF7
+
+Call to FreeBSD developer: It's also the new dependencies to add 
+for next the imapsync  package 1.882 

INSTALL.d/INSTALL.OnlineUI.txt

@@ -0,0 +1,291 @@
+#!/bin/cat 
+# $Id: INSTALL.OnlineUI.txt,v 1.32 2019/11/28 14:42:17 gilles Exp gilles $
+
+This documentation is also located online at 
+https://imapsync.lamiral.info/INSTALL.d/
+https://imapsync.lamiral.info/INSTALL.d/INSTALL.OnlineUI.txt
+
+=======================================================================
+               Installing imapsync online
+=======================================================================
+
+Please consider this as relatively experimental.
+However, to a certain extent, I'm now confident with /X 
+since the /X service is up and running quite well since January 2017.
+
+=======================================================================
+                    Hardware consideration
+
+RAM used per imapsync process, mean value: 230 MB.
+Average_bandwidth_rate: 345 KiB/s ~ 2.8 Mbps.
+Load mean: 0.8 on a CPU 4 cores "Intel(R) i5-2320 3.00GHz K8-class"
+
+
+
+
+=======================================================================
+                    Installation
+                    
+You have to be a little familiar with what a CGI script is
+and how to activate a CGI script on the Apache 
+HTTP server, or any other HTTP server. Linux is also a 
+preferred platform (I run /X service on Linux and FreeBSD).
+
+I have tested yet this visual interface on Mac. It works
+but for now it demands some skills few Mac users have.
+
+I have tested this visual interface on Windows,
+it fails on Windows because of some hard coded Unix paths.
+I'm working on it to be Windows ok but it's not done yet (october 2019).
+
+Some users have successfully installed a /X visual interface 
+on Windows using a Linux VM machine.
+
+The web visual user interface frontend /X is compounded in four
+files: a html5 file, a css file, a javascript file and
+a logo image:
+
+* https://i005.lamiral.info/X/imapsync_form_extra.html
+* https://i005.lamiral.info/X/imapsync_form.css
+* https://i005.lamiral.info/X/imapsync_form.js
+* https://i005.lamiral.info/X/logo_imapsync_Xn.png
+
+
+You can do a "view source" to see the html file as 
+it is written, and a "save" to get it locally.
+The three other files can be saved the same way or
+with wget.
+
+Those four files can be put anywhere on a web server,
+as long as they stand in the same directory. If you
+want to put them in different directories, just change
+the content of imapsync_form_extra.html to reflect the change,
+ie, change the two lines referencing imapsync_form.css and imapsync_form.js 
+  href="imapsync_form.css" (near the beginning of imapsync_form_extra.html)
+  src="imapsync_form.js"   (near the end of imapsync_form_extra.html)
+I let you changing the image logo as an exercise, it's safe if you fail.
+
+The actual imap syncing work is done by imapsync acting as a CGI,
+the visual interface is only there to give imapsync the parameters
+needed for the sync.
+
+Use at least Perl module CGI.pm release 4.08 (2014-10-18)
+to avoid the bug "Undefined subroutine CGI::multi_param".
+You can use the command cpanm to upgrade CGI.pm to its last version,
+it's the easiest way.
+
+Print the CGI.pm release with:
+
+  perl -MCGI -e 'print "$CGI::VERSION\n"'
+
+If it is under release 4.08 (2014-10-18) then upgrade it with
+
+  cpanm CGI
+
+It is a good thing to remove the old one if it was installed
+by a distribution package, I let you this part as an exercise too.
+
+To check and fix the Perl modules dependencies, run:
+
+  cd
+  wget -N https://imapsync.lamiral.info/prerequisites_imapsync
+  sh prerequisites_imapsync
+
+In order to make imapsync work as a cgi, there is two conditions.
+First, imapsync has to work by itself on the web host.
+
+If imapsync doesn't work by itself, as a command line, 
+then it won't work as a cgi.
+
+Second, imapsync has to work by itself on the web host using
+the Unix user running the web server. Detailed examples to 
+verify that will be provided further in this document.
+
+The imapsync_form_extra.html file in action calls the CGI location
+/cgi-bin/imapsync
+which has to be imapsync itself, the file script (not the directory).
+
+The very latest and relatively stable imapsync is at
+https://imapsync.lamiral.info/imapsync
+This file is the program file used verbatim for the service given at
+https://i005.lamiral.info/X/
+
+Copy the three files imapsync_form.* on a directory that is exported 
+by your HTTP server.
+Copy the imapsync script on the cgi-bin/ directory
+allowing CGIs and you'll have your own imapsync visual interface
+and service. The cgi-bin/ directory is usually outside the 
+hierarchy exported to anybody by the HTTP server.
+
+Now that I have explained the general context for any system,
+I'll describe concrete examples on several systems, 
+Debian/Ubuntu and Centos. Feedbacks show that the Centos
+process is easier in case you know just a little of the
+linux distributions.
+
+=============================================================================
+A) Concrete example on a Debian server with Apache:
+
+Imapsync script place on the server disk:
+/usr/lib/cgi-bin/imapsync
+
+Get and install latest imapsync:
+
+  cd
+  wget -N -O /usr/lib/cgi-bin/imapsync  https://imapsync.lamiral.info/imapsync
+  chmod +x /usr/lib/cgi-bin/imapsync
+
+ Check it like this:
+
+  cd
+  /usr/lib/cgi-bin/imapsync --testslive
+
+Assuming that the Unix account running Apache is www-data, 
+check that it will work under Apache with this command:
+
+  su -s /bin/sh -c 'SERVER_SOFTWARE=foo /usr/lib/cgi-bin/imapsync' www-data
+
+  wget -nv -S -O-  http://localhost/cgi-bin/imapsync?testslive=1
+
+It should print something like:
+Status: 200 OK to sync IMAP boxes. Load on bar is ...
+...
+
+
+This classical /cgi-bin directory is already configured 
+in the Apache configuration file
+/etc/apache2/sites-available/default-ssl
+or
+/etc/apache2/sites-available/default
+
+The configuration file contains the following section
+somewhere, maybe in comments for now, ie, with 
+some # characters 
+at the beginning to make them ignored:
+
+ScriptAlias /cgi-bin/ /usr/lib/cgi-bin/
+<Directory "/usr/lib/cgi-bin">
+    AllowOverride None
+    # Next line "no-gzip 1" is to avoid output buffering, 
+    # clients can then see the log along the sync
+    SetEnv no-gzip 1
+    Options +ExecCGI -MultiViews
+    Order allow,deny
+    Allow from all
+</Directory>
+
+The UI front-end file place on the server disk in
+this example is
+/var/www/html/X/imapsync_form_extra.html
+but it can be placed it anywhere on disk, the important
+thing is that it has to be served by the web server. 
+
+  mkdir /var/www/html/X/
+  cd /var/www/html/X/
+  wget -N \
+  https://i005.lamiral.info/X/imapsync_form_extra.html \
+  https://i005.lamiral.info/X/imapsync_form.css \
+  https://i005.lamiral.info/X/imapsync_form.js \
+  https://i005.lamiral.info/X/logo_imapsync_Xn.png
+  ln -s imapsync_form_extra.html index.html
+
+The imapsync process working directory in cgi mode is
+/var/tmp/imapsync_cgi/
+it is not configurable unless changing it in
+imapsync directly, it is hard-coded in imapsync. 
+In this directory will go the log files and
+the pid files.
+
+Check 
+   http://yourhost/X/imapsync_form_extra.html
+or the safer
+  https://yourhost/X/imapsync_form_extra.html
+
+That's all for installing a /X service on Debian.
+
+=============================================================================
+B) Concrete example on a Centos 7 server with httpd Apache:
+
+  mkdir /var/www/html/X/
+  cd /var/www/html/X/
+  wget -N \
+  https://i005.lamiral.info/X/imapsync_form_extra.html \
+  https://i005.lamiral.info/X/imapsync_form.css \
+  https://i005.lamiral.info/X/imapsync_form.js \
+  https://i005.lamiral.info/X/logo_imapsync_Xn.png
+  ln -s imapsync_form_extra.html index.html
+  
+  cd
+  wget -N https://imapsync.lamiral.info/imapsync
+  chmod +x imapsync
+  # some basic tests
+  ./imapsync 
+  ./imapsync --testslive
+
+  cp imapsync /var/www/cgi-bin/
+  su -s /bin/sh -c 'SERVER_SOFTWARE=foo /var/www/cgi-bin/imapsync' apache
+  wget -nv -S -O-  http://localhost/cgi-bin/imapsync?testslive=1
+
+
+Check 
+   http://yourhost/X/imapsync_form_extra.html
+or the safer
+  https://yourhost/X/imapsync_form_extra.html
+
+That's all for installing a /X service on Centos 7.
+
+=======================================================================
+=======================================================================
+
+
+====== mod_perl failure ======
+
+This part is for mod_perl experts only.
+The script imapsync doesn't work under Modperl::Registry
+nor under ModPerl::PerlRun. So read on if you think you
+are better than me. 
+
+I've try the standard way, telling how any cgi perl script
+can be run under mod_perl perlrun, but it fails with imapsync.
+Any hint welcome!
+
+# This is a Debian example
+
+# install mod-perl with
+
+  apt-get install libapache2-mod-perl2
+
+# edit the file /etc/apache2/mods-available/perl.conf
+# with the following lines
+  more /etc/apache2/mods-available/perl.conf
+
+<IfModule mod_perl.c>
+  PerlModule ModPerl::PerlRun
+  Alias /perl-run/ /usr/lib/cgi-bin/
+  <Location /perl-run>
+      SetHandler perl-script
+      PerlResponseHandler ModPerl::PerlRun
+      PerlOptions +ParseHeaders
+      Options +ExecCGI
+  </Location>
+</IfModule>
+
+# Enable the Apache perl module
+
+  a2enmod perl
+
+# Verify perl.conf and perl.load are in directory mods-enabled/
+
+  ls mods-enabled/perl.*
+
+# Reload Apache
+
+  apachectl graceful
+
+# Verify imapsync works under perl-run
+
+  curl http://localhost/perl-run/imapsync
+
+
+=======================================================================
+=======================================================================

INSTALL.d/INSTALL.Ubuntu.txt

@@ -0,0 +1,98 @@
+#!/bin/cat 
+# $Id: INSTALL.Ubuntu.txt,v 1.17 2019/11/28 14:35:43 gilles Exp gilles $
+
+This documentation is also located online at 
+https://imapsync.lamiral.info/INSTALL.d/
+https://imapsync.lamiral.info/INSTALL.d/INSTALL.Ubuntu.txt
+
+=======================================================================
+         Installing imapsync on Ubuntu 16.04 or higher
+=======================================================================
+
+Here is  the command to install imapsync dependencies,
+you need root privilege to run them.
+
+This command installs standard Ubuntu packages:
+
+  sudo apt-get install  \
+libauthen-ntlm-perl     \
+libclass-load-perl      \
+libcrypt-ssleay-perl    \
+libdata-uniqid-perl     \
+libdigest-hmac-perl     \
+libdist-checkconflicts-perl \
+libencode-imaputf7-perl     \
+libfile-copy-recursive-perl \
+libfile-tail-perl       \
+libio-compress-perl     \
+libio-socket-inet6-perl \
+libio-socket-ssl-perl   \
+libio-tee-perl          \
+libmail-imapclient-perl \
+libmodule-scandeps-perl \
+libnet-dbus-perl        \
+libnet-ssleay-perl      \
+libpar-packer-perl      \
+libreadonly-perl        \
+libregexp-common-perl   \
+libsys-meminfo-perl     \
+libterm-readkey-perl    \
+libtest-fatal-perl      \
+libtest-mock-guard-perl \
+libtest-mockobject-perl \
+libtest-pod-perl        \
+libtest-requires-perl   \
+libtest-simple-perl     \
+libunicode-string-perl  \
+liburi-perl             \
+libtest-nowarnings-perl \
+libtest-deep-perl       \
+libtest-warn-perl       \
+make                    \
+cpanminus
+
+In case you want to update the Perl module 
+Mail::IMAPClient, a major module for imapsync,
+the following command installs it "manually":
+
+  sudo cpanm Mail::IMAPClient
+
+In case you need to use XOAUTH2 authentication you have to install   
+the module JSON::WebToken with the command:
+
+  sudo cpanm JSON::WebToken
+
+After installing the dependencies, imapsync should be working.
+
+You don't have to be root to test and use imapsync.
+Take the compressed tarball called imapsync-1.xxx.tgz
+where 1.xxx is the version number. 
+Untar the tarball where you want:
+
+  cd 
+  tar xzvf  imapsync-1.xxx.tgz
+
+Go into the directory imapsync-1.xxx
+
+  cd imapsync-1.xxx
+
+A dependencies test that shows also the basic example:
+
+  ./imapsync
+
+A live test showing imapsync job:
+
+  ./imapsync --testslive
+
+Now the install command (need root priviledges again):
+
+  cp imapsync /usr/bin/
+
+That's finished for the installation part.
+You can use imapsync.
+
+Now go to read http://imapsync.lamiral.info/#doc
+start with the tutorial.
+
+=======================================================================
+=======================================================================

INSTALL.d/memo_docker

@@ -0,0 +1,95 @@
+#!/bin/sh
+
+echo imapsync_docker_timestamp_dockerfile
+imapsync_docker_timestamp_dockerfile() {
+	DATE_CURRENT=`date +%Y_%m_%d_%H_%M_%S`
+	echo $DATE_CURRENT
+	sed -i -e "/just_a_comment_to_force_update/s/comment_to_force_update.*/comment_to_force_update $DATE_CURRENT/" Dockerfile
+	ci -l -f -m"Changing timestamp to $DATE_CURRENT with imapsync_docker_timestamp_dockerfile" Dockerfile
+}
+
+echo imapsync_docker_build
+imapsync_docker_build() {
+    docker build -t gilleslamiral/imapsync . \
+        && imapsync_docker_add_tag_version && echo Build SUCCEEDED || echo Build FAILED
+
+    echo
+    #docker run gilleslamiral/imapsync imapsync --testslive
+    #docker run gilleslamiral/imapsync imapsync --testslive6
+    # docker run gilleslamiral/imapsync imapsync --testslive6 --nossl2
+}
+
+echo imapsync_docker_add_tag_version
+imapsync_docker_add_tag_version() {
+    docker images gilleslamiral/imapsync
+    echo 
+    version=`docker run gilleslamiral/imapsync imapsync --version`
+    echo $version
+    docker tag gilleslamiral/imapsync:latest gilleslamiral/imapsync:$version
+    docker images gilleslamiral/imapsync
+}
+
+
+
+echo imapsync_docker_testslive
+imapsync_docker_testslive() {
+    echo docker run gilleslamiral/imapsync imapsync --testslive
+    docker run gilleslamiral/imapsync imapsync --testslive
+}
+
+echo imapsync_docker_testslive6
+imapsync_docker_testslive6() {
+    echo docker run gilleslamiral/imapsync imapsync --testslive6 --ssl1 --ssl2
+    docker run gilleslamiral/imapsync imapsync --testslive6 --ssl1 --ssl2
+}
+
+echo imapsync_docker_tests
+imapsync_docker_tests() {
+    echo docker run gilleslamiral/imapsync imapsync --tests
+    docker run gilleslamiral/imapsync imapsync --tests
+}
+
+echo docker_delete_all_images
+docker_delete_all_images() {
+    docker rm `docker ps -a -q`
+    docker rmi `docker images -q`
+}
+
+echo docker_system_prune
+docker_system_prune()
+{
+        docker system prune
+}
+
+echo docker_delete_dandling_images
+docker_delete_dandling_images() {
+	docker images
+	dandling_images=`docker images -f dangling=true -q`
+	exited_containers=`docker ps -a -f status=exited -q`
+	test -n "$exited_containers" && docker rm $exited_containers
+	test -n "$dandling_images"   && docker rmi $dandling_images
+	docker images
+}
+
+
+echo imapsync_docker_rebuild_from_scratch
+imapsync_docker_rebuild_from_scratch() {
+    delete_all_images
+    docker images
+    imapsync_docker_build
+}
+
+echo imapsync_docker_upload
+imapsync_docker_upload() {
+    # upload only after successful tests
+    set -x \
+    && imapsync_docker_testslive \
+    && imapsync_docker_tests \
+    && docker run gilleslamiral/imapsync true \
+    && docker login --username=gilleslamiral --password=`cat $HOME/var/pass/secret.docker` \
+    && docker push gilleslamiral/imapsync:latest \
+    && set +x && echo imapsync push SUCCEEDED || echo imapsync push FAILED
+    set +x
+}
+
+

INSTALL.d/prerequisites_imapsync

@@ -0,0 +1,289 @@
+#!/bin/sh
+
+# $Id: prerequisites_imapsync,v 1.35 2019/11/27 15:58:46 gilles Exp gilles $
+
+MODULES_MANDATORY='
+App::cpanminus
+Authen::NTLM
+CGI
+Compress::Zlib
+Crypt::OpenSSL::RSA
+Data::Dumper
+Data::Uniqid
+Digest::HMAC
+Digest::HMAC_MD5
+Digest::MD5
+Dist::CheckConflicts
+Encode
+Encode::Byte
+Encode::IMAPUTF7
+File::Copy::Recursive
+File::Tail
+IO::Socket::INET
+IO::Socket::INET6
+IO::Socket::SSL
+IO::Tee
+JSON
+JSON::WebToken
+JSON::WebToken::Crypt::RSA
+HTML::Entities
+LWP::UserAgent
+Mail::IMAPClient
+MIME::Base64
+Module::Implementation
+Module::Runtime
+Module::ScanDeps
+Net::SSLeay
+Package::Stash
+Package::Stash::XS
+PAR::Packer
+Parse::RecDescent
+Pod::Usage
+Readonly
+Regexp::Common
+Sys::MemInfo
+Term::ReadKey
+Test::Fatal
+Test::Mock::Guard
+Test::MockObject
+Test::More
+Test::Pod
+Test::Requires
+Test::Deep
+Text::ParseWords
+Try::Tiny
+Unicode::String
+URI::Escape
+'
+
+MODULES_FOR_CODERS='
+Smart::Comments
+'
+
+
+test_perl() {
+# First we need perl
+
+	if perl -v > /dev/null 2>&1 ; then
+		perl_version=`perl -e 'printf "%vd\n", $^V;'`
+		echo Ok: Found Perl $perl_version
+		return 0
+	else
+		echo 'Failure: Perl is not here. You have to install Perl first.'
+		return 1
+	fi
+}
+
+test_make() {
+# Second we need make to build some Perl modules
+
+	if echo foo: | make -f - foo ; then
+		make_version=`make -v |head -1`
+		echo Ok: Found make $make_version
+		return 0
+	else
+		echo 'Failure: make is not here. You have to install the "make" command.'
+		return 1
+	fi
+}
+
+
+test_cpanm() {
+# Second we need make to build some Perl modules
+        # redirect "cpanm ... < /dev/null" is there for macos buid via ssh
+        # no clue why it's necessary
+	if cpanm -h > /dev/null 2>&1 < /dev/null; then
+		cpanm_version=`cpanm --version < /dev/null | head -1`
+		echo Ok: Found cpanm $cpanm_version
+		return 0
+	else
+		echo 'Failure: cpanm is not here. You have to install the "cpanm" command.'
+		return 1
+	fi
+}
+
+
+
+test_module() {
+	test -n $1 || return
+	M_tested=$1
+	shift
+	if perl -m"$M_tested" -e '' >/dev/null 2>&1 ; then
+		echo "Ok: Found Perl module $M_tested"
+	else
+		echo "Failure: Not found Perl module $M_tested $@"
+		LIST_TO_INSTALL="$LIST_TO_INSTALL $M_tested"
+	fi
+        return
+}
+
+test_mandatory_modules() {
+	for M in $MODULES_MANDATORY
+	do
+		test_module $M
+	done
+}
+
+
+search_modules_any() {
+	test -n "$*" || {
+		echo "All needed modules are already installed"
+		return
+	}
+        
+        # Debian, Ubuntu & Co
+	apt-cache -h > /dev/null 2>&1 && {
+		search_modules_apt "$@"
+		return
+	}
+        
+        # Centos & Co
+	yum -h > /dev/null 2>&1 && {
+		search_modules_yum  "$@"
+		return
+	}
+        
+        # ArchLinux & Co
+        pacman -h > /dev/null 2>&1 && {
+		search_modules_pacman  "$@"
+		return
+	}
+        
+        # FreeBSD
+	pkg version > /dev/null 2>&1 && {
+		search_modules_freebsd  "$@"
+		return
+	}
+        
+	# no yum, no apt-get, no pacman
+	{
+		search_modules_cpanm "$@"
+		return
+	}
+}
+
+search_modules_cpanm() {
+		cat <<EOD
+Here is a cpanm command to install missing Perl modules:
+cpanm $@
+EOD
+}
+
+search_modules_pacman() {
+	echo 
+	echo Searching pacman packages names
+        #echo pacman -Fy
+        #pacman -Fy 
+        echo pacman -S --noconfirm --needed  pkgfile
+        pacman -S --noconfirm --needed  pkgfile
+        echo pkgfile --update
+        pkgfile --update
+	for M in "$@" ; do
+		echo "==== Searching pacman package name for $M"
+		F=`echo $M|tr -s ":" "/"`.pm
+                
+                # Not very good "pacman -Fs"
+		#echo pacman -Fs  "$F"
+		#echo
+		#pacman -Fs  "$F"
+                #echo
+                # Better! pkgfile --reg
+                echo "pkgfile --reg $F | grep perl-"
+                echo
+                pkgfile --reg "$F" | grep perl-
+		echo
+	done
+}
+
+search_modules_yum() {
+	echo 
+	echo Searching rpm packages names
+	for M in "$@" ; do
+		echo "==== Searching rpm package name for $M"
+		F=`echo $M|tr -s ":" "/"`.pm
+		echo yum -q whatprovides "*/$F"
+		echo
+		yum -q whatprovides "*/$F"
+		echo
+	done
+}
+
+search_modules_apt() {
+	echo 
+	echo Searching deb packages names
+	for M in "$@" ; do
+		F=`echo $M|tr -s ":" "/"`.pm
+		echo "==== Searching deb package name for $M with: apt-file search /$F"
+		#echo apt-file search /$F
+		echo
+                if apt-file -h > /dev/null 2>&1
+                then
+                        apt-file search /$F
+                else
+                        echo "apt-file is not installed. Suggestion: apt-get install apt-file; apt-file update"
+                fi
+                echo
+		echo "==== Searching deb package name for $M with: apt-cache search $M"
+		#apt-cache search "$M"
+                apt-cache search "$M"
+		echo
+	done
+}
+
+search_modules_freebsd()
+{
+	echo 
+	echo Searching pkg FreeBSD names
+	for M in "$@" ; do
+		F=`echo $M|tr -s ":" "-"`
+		echo "==== Searching deb package name for $M with: pkg search p5-$F"
+		echo
+		pkg search "p5-$F"
+                echo
+	done
+
+}
+
+list_to_install() {
+	test -n "$LIST_TO_INSTALL" || return 0
+	echo
+	echo 'What you have to do before using imapsync:'
+	for M in $LIST_TO_INSTALL ; do
+		echo "Install Perl module $M"
+	done
+        # return false/bad if some modules are missing.
+        return 1
+}
+
+test_unix() {
+	echo '$SHELL says ' $SHELL
+	echo '$0 gives ' $0 
+	echo -n "ps -ef gives " ; ps -ef | grep $$ | grep -v grep| grep -v 'ps -ef'
+	sw_vers > /dev/null 2>&1 && sw_vers # Darwin
+	lsb_release -dirc > /dev/null 2>&1 && lsb_release -dirc # Linux
+	uname -a
+}
+
+
+
+test_unix
+#exit
+test_perl || exit 1
+test_make || exit
+test_mandatory_modules
+list_to_install
+EXIT=$?
+
+# Help the user to install missing modules
+search_modules_any $LIST_TO_INSTALL
+
+if test "$1" = "MODULES_MANDATORY"
+then
+        search_modules_any $MODULES_MANDATORY
+elif test -n "$1" 
+then
+        search_modules_any "$@"
+fi
+
+test_cpanm
+exit $EXIT

LICENSE

@@ -0,0 +1,15 @@
+                NO LIMIT PUBLIC LICENSE
+                 Version 0/0, June 2012
+
+Gilles LAMIRAL
+La Billais
+35580 Baulon
+France
+
+                NO LIMIT PUBLIC LICENSE
+Terms and conditions for copying, distribution, modification
+or anything else.
+
+ 0 No limits to do anything with this work and this license.
+ 1 GOTO 0
+

LOG_imapsync/2020_07_26_21_01_12_069_test1_test2.txt

@@ -0,0 +1,268 @@
+Here is imapsync 1.977 on host privremena, a linux system with 18.0/31.3 free GiB of RAM
+with Perl 5.28.1 and Mail::IMAPClient 3.42
+Transfer started at Sun Jul 26 21:01:12 2020
+PID is 13667 my PPID is 22856
+Log file is LOG_imapsync/2020_07_26_21_01_12_069_test1_test2.txt ( to change it, use --logfile path ; or use --nolog to turn off logging )
+Load is 0.86 0.99 1.00 2/1183 on 2 cores
+Current directory is /root/imapsync-master
+Real user id is root (uid 0)
+Effective user id is root (euid 0)
+$RCSfile: imapsync,v $ $Revision: 1.977 $ $Date: 2019/12/23 20:18:02 $ 
+Command line used, run by /usr/bin/perl:
+./imapsync --testslive
+Temp directory is /tmp ( to change it use --tmpdir dirpath )
+kill -QUIT 13667 # special behavior: call to sub catch_exit
+kill -TERM 13667 # special behavior: call to sub catch_exit
+kill -INT 13667 # special behavior: call to sub catch_reconnect
+kill -HUP 13667 # special behavior: call to sub catch_print
+kill -USR1 13667 # special behavior: call to sub toggle_sleep
+File /tmp/imapsync.pid does not exist
+PID file is /tmp/imapsync.pid ( to change it, use --pidfile filepath ; to avoid it use --pidfile "" )
+Writing my PID 13667 in /tmp/imapsync.pid
+Writing also my logfile name in /tmp/imapsync.pid : LOG_imapsync/2020_07_26_21_01_12_069_test1_test2.txt
+Modules version list:
+Authen::NTLM         Not installed
+CGI                  4.40
+Compress::Zlib       2.074
+Crypt::OpenSSL::RSA  Not installed
+Data::Uniqid         Not installed
+Digest::HMAC_MD5     1.01
+Digest::HMAC_SHA1    1.03
+Digest::MD5          2.55
+Encode               2.97
+Encode::IMAPUTF7     1.05
+File::Copy::Recursive 0.45
+File::Spec           3.74
+Getopt::Long         2.5
+HTML::Entities       3.69
+IO::Socket           1.39
+IO::Socket::INET     1.39
+IO::Socket::INET6    2.72
+IO::Socket::IP       0.39
+IO::Socket::SSL      2.060
+IO::Tee              0.65
+JSON                 Not installed
+JSON::WebToken       Not installed
+LWP                  6.36
+MIME::Base64         3.15
+Mail::IMAPClient     3.42
+Net::Ping            2.62
+Net::SSLeay          1.85
+Term::ReadKey        2.38
+Test::MockObject     Not installed
+Time::HiRes          1.9759
+URI::Escape          3.31
+Unicode::String      2.10
+( use --no-modulesversion to turn off printing this Perl modules list )
+Info: will resync flags for already transferred messages. Use --noresyncflags to not resync flags.
+Host1: probing ssl on port 993 ( use --nosslcheck to avoid this ssl probe ) 
+Host1: sslcheck detected open ssl port 993 so turning ssl on (use --nossl1 --notls1 to turn off SSL and TLS wizardry)
+Host2: probing ssl on port 993 ( use --nosslcheck to avoid this ssl probe ) 
+Host2: sslcheck detected open ssl port 993 so turning ssl on (use --nossl2 --notls2 to turn off SSL and TLS wizardry)
+SSL debug mode level is --debugssl 1 (can be set from 0 meaning no debug to 4 meaning max debug)
+Host1: SSL default mode is like --sslargs1 "SSL_verify_mode=0", meaning for host1 SSL_VERIFY_NONE, ie, do not check the certificate server.
+Host1: Use --sslargs1 SSL_verify_mode=1 to have SSL_VERIFY_PEER, ie, check the certificate server of host1
+Host2: SSL default mode is like --sslargs2 "SSL_verify_mode=0", meaning for host2 SSL_VERIFY_NONE, ie, do not check the certificate server.
+Host2: Use --sslargs2 SSL_verify_mode=1 to have SSL_VERIFY_PEER, ie, check the certificate server of host2
+Info: turned ON syncinternaldates, will set the internal dates (arrival dates) on host2 same as host1.
+Host1: will try to use LOGIN authentication on host1
+Host2: will try to use LOGIN authentication on host2
+Host1: imap connection timeout is 120 seconds
+Host2: imap connection timeout is 120 seconds
+Host1: IMAP server [test1.lamiral.info] port [993] user [test1]
+Host2: IMAP server [test2.lamiral.info] port [993] user [test2]
+Host1: connecting and login on host1 [test1.lamiral.info] port [993] with user [test1]
+Host1 IP address: 5.39.87.81
+Host1 banner: * OK [CAPABILITY IMAP4rev1 SASL-IR LOGIN-REFERRALS ID ENABLE IDLE LITERAL+ AUTH=PLAIN] Dovecot (Debian) ready.
+Host1 capability before authentication: IMAP4rev1 SASL-IR LOGIN-REFERRALS ID ENABLE IDLE LITERAL+ AUTH=PLAIN AUTH
+Host1: success login on [test1.lamiral.info] with user [test1] auth [LOGIN]
+Host2: connecting and login on host2 [test2.lamiral.info] port [993] with user [test2]
+Host2 IP address: 5.39.87.81
+Host2 banner: * OK [CAPABILITY IMAP4rev1 SASL-IR LOGIN-REFERRALS ID ENABLE IDLE LITERAL+ AUTH=PLAIN] Dovecot (Debian) ready.
+Host2 capability before authentication: IMAP4rev1 SASL-IR LOGIN-REFERRALS ID ENABLE IDLE LITERAL+ AUTH=PLAIN AUTH
+Host2: success login on [test2.lamiral.info] with user [test2] auth [LOGIN]
+Host1: state Authenticated
+Host2: state Authenticated
+Host1 capability once authenticated: IMAP4rev1 SASL-IR LOGIN-REFERRALS ID ENABLE IDLE SORT SORT=DISPLAY THREAD=REFERENCES THREAD=REFS THREAD=ORDEREDSUBJECT MULTIAPPEND URL-PARTIAL CATENATE UNSELECT CHILDREN NAMESPACE UIDPLUS LIST-EXTENDED I18NLEVEL=1 CONDSTORE QRESYNC ESEARCH ESORT SEARCHRES WITHIN CONTEXT=SEARCH LIST-STATUS BINARY MOVE SNIPPET=FUZZY LITERAL+ NOTIFY SPECIAL-USE THREAD I18NLEVEL CONTEXT SNIPPET
+Host2 capability once authenticated: IMAP4rev1 SASL-IR LOGIN-REFERRALS ID ENABLE IDLE SORT SORT=DISPLAY THREAD=REFERENCES THREAD=REFS THREAD=ORDEREDSUBJECT MULTIAPPEND URL-PARTIAL CATENATE UNSELECT CHILDREN NAMESPACE UIDPLUS LIST-EXTENDED I18NLEVEL=1 CONDSTORE QRESYNC ESEARCH ESORT SEARCHRES WITHIN CONTEXT=SEARCH LIST-STATUS BINARY MOVE SNIPPET=FUZZY LITERAL+ NOTIFY SPECIAL-USE THREAD I18NLEVEL CONTEXT SNIPPET
+
+Host1: found ID capability. Sending/receiving ID, presented in raw IMAP for now.
+In order to avoid sending/receiving ID, use option --noid
+Sending: 4 ID ("name" "imapsync" "version" "1.977" "os" "linux" "vendor" "Gilles LAMIRAL" "support-url" "https://imapsync.lamiral.info/" "date" "23-Dec-2019 20:18:02 +0000" "side" "host1")
+Sent 181 bytes
+Read: 	* ID ("name" "Dovecot")
+  	4 OK ID completed (0.001 + 0.000 secs).
+
+
+Host2: found ID capability. Sending/receiving ID, presented in raw IMAP for now.
+In order to avoid sending/receiving ID, use option --noid
+Sending: 4 ID ("name" "imapsync" "version" "1.977" "os" "linux" "vendor" "Gilles LAMIRAL" "support-url" "https://imapsync.lamiral.info/" "date" "23-Dec-2019 20:18:02 +0000" "side" "host2")
+Sent 181 bytes
+Read: 	* ID ("name" "Dovecot")
+  	4 OK ID completed (0.001 + 0.000 secs).
+
+Host1: found 2 folders.
+Host2: found 7 folders.
+Host1: guessing separator from folder listing: [/]
+Host1: separator given by NAMESPACE: [/]
+Host2: guessing separator from folder listing: [/]
+Host2: separator given by NAMESPACE: [/]
+Host1: guessing prefix from folder listing: []
+Host1: prefix given by NAMESPACE: []
+Host2: guessing prefix from folder listing: []
+Host2: prefix given by NAMESPACE: []
+Host1: separator and prefix: [/][]
+Host2: separator and prefix: [/][]
+Including all folders found by default. Use --subscribed or --folder or --folderrec or --include to select specific folders. Use --exclude to unselect specific folders.
+Host1: Checking wanted folders exist. Use --nocheckfoldersexist to avoid this check (shared of public namespace targeted).
+Host1: Checking wanted folders are selectable. Use --nocheckselectable to avoid this check.
+Turned off automapping folders ( use --automap to turn on automapping )
+
+++++ Listing folders
+All foldernames are presented between brackets like [X] where X is the foldername.
+When a foldername contains non-ASCII characters it is presented in the form
+[X] = [Y] where
+X is the imap foldername you have to use in command line options and
+Y is the utf8 output just printed for convenience, to recognize it.
+
+Host1: folders list (first the raw imap format then the [X] = [Y]):
+* LIST (\NoInferiors) "/" init
+* LIST (\HasNoChildren) "/" INBOX
+11 OK List completed (0.001 + 0.000 secs).
+
+[INBOX]
+[init]
+
+Host2: folders list (first the raw imap format then the [X] = [Y]):
+* LIST (\NoInferiors \Drafts) "/" Drafts
+* LIST (\NoInferiors) "/" DRAFTS
+* LIST (\NoInferiors) "/" Archives
+* LIST (\NoInferiors) "/" prueba
+* LIST (\NoInferiors) "/" "Deleted Messages"
+* LIST (\NoInferiors \UnMarked) "/" init
+* LIST (\HasNoChildren) "/" INBOX
+9 OK List completed (0.002 + 0.000 + 0.001 secs).
+
+[Archives]
+[DRAFTS]
+[Deleted Messages]
+[Drafts]
+[INBOX]
+[init]
+[prueba]
+
+Folders in host2 not in host1:
+[prueba]
+[Drafts]
+[Deleted Messages]
+[DRAFTS]
+[Archives]
+
+
+Folders sizes before the synchronization.
+You can remove foldersizes listings by using "--nofoldersizes" and "--nofoldersizesatend"
+but then you will also lose the ETA (Estimation Time of Arrival) given after each message copy.
+Host1 folder     1/2 [INBOX]                             Size:    133296 Messages:   328 Biggest:       416
+Host2 folder     1/2 [INBOX]                             Size:    133296 Messages:   328 Biggest:       416
+Host2-Host1                                                            0               0                  0
+
+Host1 folder     2/2 [init]                              Size:         0 Messages:     0 Biggest:         0
+Host2 folder     2/2 [init]                              Size:         0 Messages:     0 Biggest:         0
+Host2-Host1                                                            0               0                  0
+
+Host1 Nb folders:                     2 folders
+Host2 Nb folders:                     2 folders
+
+Host1 Nb messages:                  328 messages
+Host2 Nb messages:                  328 messages
+
+Host1 Total size:                133296 bytes (130.172 KiB)
+Host2 Total size:                133296 bytes (130.172 KiB)
+
+Host1 Biggest message:              416 bytes (0.406 KiB)
+Host2 Biggest message:              416 bytes (0.406 KiB)
+
+Time spent on sizing:         2.7 seconds
+++++ Looping on each one of 2 folders to sync
+ETA: Sun Jul 26 21:01:14 2020  0 s  328/328 msgs left
+Folder     1/2 [INBOX]                             -> [INBOX]                            
+Host1: folder [INBOX] has 328 messages in total (mentioned by SELECT)
+Host2: folder [INBOX] has 328 messages in total (mentioned by SELECT)
+Host2: folder [INBOX] permanentflags: 
+Host1: folder [INBOX] considering 328 messages
+Host2: folder [INBOX] considering 328 messages
+Host1: folder [INBOX] selected 328 messages, duplicates 0
+Host2: folder [INBOX] selected 328 messages, duplicates 0
+ETA: Sun Jul 26 21:01:15 2020  0 s  0/328 msgs left
+Folder     2/2 [init]                              -> [init]                             
+Host1: folder [init] has 0 messages in total (mentioned by SELECT)
+Host2: folder [init] has 0 messages in total (mentioned by SELECT)
+Host2: folder [init] permanentflags: 
+Host1: folder [init] considering 0 messages
+Host2: folder [init] considering 0 messages
+Host1: folder [init] selected 0 messages, duplicates 0
+Host2: folder [init] selected 0 messages, duplicates 0
+ETA: Sun Jul 26 21:01:15 2020  0 s  0/328 msgs left
+++++ End looping on each folder
+
+Folders sizes after the synchronization.
+You can remove this foldersizes listing by using  "--nofoldersizesatend"
+Host1 folder     1/2 [INBOX]                             Size:    133296 Messages:   328 Biggest:       416
+Host2 folder     1/2 [INBOX]                             Size:    133296 Messages:   328 Biggest:       416
+Host2-Host1                                                            0               0                  0
+
+Host1 folder     2/2 [init]                              Size:         0 Messages:     0 Biggest:         0
+Host2 folder     2/2 [init]                              Size:         0 Messages:     0 Biggest:         0
+Host2-Host1                                                            0               0                  0
+
+Host1 Nb folders:                     2 folders
+Host2 Nb folders:                     2 folders
+
+Host1 Nb messages:                  328 messages
+Host2 Nb messages:                  328 messages
+
+Host1 Total size:                133296 bytes (130.172 KiB)
+Host2 Total size:                133296 bytes (130.172 KiB)
+
+Host1 Biggest message:              416 bytes (0.406 KiB)
+Host2 Biggest message:              416 bytes (0.406 KiB)
+
+Time spent on sizing:         0.3 seconds
+++++ Statistics
+Transfer started on                     : Sun Jul 26 21:01:12 2020
+Transfer ended on                       : Sun Jul 26 21:01:15 2020
+Transfer time                           : 3.4 sec
+Folders synced                          : 2/2 synced
+Messages transferred                    : 0 
+Messages skipped                        : 328
+Messages found duplicate on host1       : 0
+Messages found duplicate on host2       : 0
+Messages found crossduplicate on host2  : 0
+Messages void (noheader) on host1       : 0  
+Messages void (noheader) on host2       : 0
+Messages found in host1 not in host2    : 0 messages
+Messages found in host2 not in host1    : 0 messages
+Messages deleted on host1               : 0
+Messages deleted on host2               : 0
+Total bytes transferred                 : 0 (0.000 KiB)
+Total bytes skipped                     : 133296 (130.172 KiB)
+Message rate                            : 0.0 messages/s
+Average bandwidth rate                  : 0.0 KiB/s
+Reconnections to host1                  : 0
+Reconnections to host2                  : 0
+Memory consumption at the end           : 176.3 MiB (started with 159.9 MiB)
+Load end is                             : 0.86 0.99 1.00 1/1183 on 2 cores
+Biggest message                         : 0 bytes (0.000 KiB)
+Memory/biggest message ratio            : NA
+Start difference host2 - host1          : 0 messages, 0 bytes (0.000 KiB)
+Final difference host2 - host1          : 0 messages, 0 bytes (0.000 KiB)
+The sync looks good, all 328 identified messages in host1 are on host2.
+There is no unidentified message
+The sync is strict, all 328 identified messages in host2 are on host1.
+Detected 0 errors
+
+Check if a new imapsync release is available by adding --releasecheck
+Homepage: https://imapsync.lamiral.info/
+Live tests ended successfully
+Exiting with return value 0 (EX_OK: successful termination) 0/50 nb_errors/max_errors
+Log file is LOG_imapsync/2020_07_26_21_01_12_069_test1_test2.txt ( to change it, use --logfile filepath ; or use --nolog to turn off logging )

LOG_imapsync/2020_07_29_12_41_38_758_office@green-line.co.rs_tester@ranitovic.in.rs.txt

@@ -0,0 +1,64 @@
+Here is imapsync 1.977 on host privremena, a linux system with 17.2/31.3 free GiB of RAM
+with Perl 5.28.1 and Mail::IMAPClient 3.42
+Transfer started at Wed Jul 29 12:41:38 2020
+PID is 13032 my PPID is 13031
+Log file is LOG_imapsync/2020_07_29_12_41_38_758_office@green-line.co.rs_tester@ranitovic.in.rs.txt ( to change it, use --logfile path ; or use --nolog to turn off logging )
+Load is 0.71 0.51 0.38 1/1181 on 2 cores
+Current directory is /root/imapsync-master
+Real user id is root (uid 0)
+Effective user id is root (euid 0)
+$RCSfile: imapsync,v $ $Revision: 1.977 $ $Date: 2019/12/23 20:18:02 $ 
+Command line used, run by /usr/bin/perl:
+./imapsync --addheader --automap --host1 cp8.ulimitserver.com --host2 cp8.ulimitserver.com --password1 MASKED --password2 MASKED --user1 office@green-line.co.rs --user2 tester@ranitovic.in.rs
+Temp directory is . ( to change it use --tmpdir dirpath )
+Under cgi context
+Umask set with 0077 (was 0022)
+REMOTE_ADDR is ::ffff:89.216.99.93
+HTTP_REFERER is http://148.251.112.220:8080/
+HTTP_USER_AGENT is Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Firefox/78.0
+SERVER_SOFTWARE is ./webserver
+SERVER_PORT is 8080
+HTTP_COOKIE is 686c9b6492d74d6d7c41621a12c6956f=la6q3dnkojbe6vjjq7boesovf2
+kill -QUIT 13032 # special behavior: call to sub catch_exit
+kill -TERM 13032 # special behavior: call to sub catch_exit
+kill -INT 13032 # special behavior: call to sub catch_reconnect
+kill -HUP 13032 # special behavior: call to sub catch_print
+kill -USR1 13032 # special behavior: call to sub toggle_sleep
+File ./imapsync_cp8.ulimitserver.com_office@green-line.co.rs_cp8.ulimitserver.com_tester@ranitovic.in.rs.pid does not exist
+Error reading file ./imapsync_cp8.ulimitserver.com_office@green-line.co.rs_cp8.ulimitserver.com_tester@ranitovic.in.rs.pid : No such file or directory
+PID file is ./imapsync_cp8.ulimitserver.com_office@green-line.co.rs_cp8.ulimitserver.com_tester@ranitovic.in.rs.pid ( to change it, use --pidfile filepath ; to avoid it use --pidfile "" )
+Writing my PID 13032 in ./imapsync_cp8.ulimitserver.com_office@green-line.co.rs_cp8.ulimitserver.com_tester@ranitovic.in.rs.pid
+Writing also my logfile name in ./imapsync_cp8.ulimitserver.com_office@green-line.co.rs_cp8.ulimitserver.com_tester@ranitovic.in.rs.pid : LOG_imapsync/2020_07_29_12_41_38_758_office@green-line.co.rs_tester@ranitovic.in.rs.txt
+Info: will resync flags for already transferred messages. Use --noresyncflags to not resync flags.
+Host1: probing ssl on port 993 ( use --nosslcheck to avoid this ssl probe ) 
+Host1: sslcheck detected open ssl port 993 so turning ssl on (use --nossl1 --notls1 to turn off SSL and TLS wizardry)
+Host2: probing ssl on port 993 ( use --nosslcheck to avoid this ssl probe ) 
+Host2: sslcheck detected open ssl port 993 so turning ssl on (use --nossl2 --notls2 to turn off SSL and TLS wizardry)
+SSL debug mode level is --debugssl 1 (can be set from 0 meaning no debug to 4 meaning max debug)
+Host1: SSL default mode is like --sslargs1 "SSL_verify_mode=0", meaning for host1 SSL_VERIFY_NONE, ie, do not check the certificate server.
+Host1: Use --sslargs1 SSL_verify_mode=1 to have SSL_VERIFY_PEER, ie, check the certificate server of host1
+Host2: SSL default mode is like --sslargs2 "SSL_verify_mode=0", meaning for host2 SSL_VERIFY_NONE, ie, do not check the certificate server.
+Host2: Use --sslargs2 SSL_verify_mode=1 to have SSL_VERIFY_PEER, ie, check the certificate server of host2
+Info: turned ON syncinternaldates, will set the internal dates (arrival dates) on host2 same as host1.
+Host1: will try to use LOGIN authentication on host1
+Host2: will try to use LOGIN authentication on host2
+Host1: imap connection timeout is 120 seconds
+Host2: imap connection timeout is 120 seconds
+Host1: IMAP server [cp8.ulimitserver.com] port [993] user [office@green-line.co.rs]
+Host2: IMAP server [cp8.ulimitserver.com] port [993] user [tester@ranitovic.in.rs]
+Host1: connecting and login on host1 [cp8.ulimitserver.com] port [993] with user [office@green-line.co.rs]
+Host1 IP address: 194.146.59.72
+Host1 banner: * OK [CAPABILITY IMAP4rev1 SASL-IR LOGIN-REFERRALS ID ENABLE IDLE NAMESPACE LITERAL+ AUTH=PLAIN AUTH=LOGIN] Dovecot ready.
+Host1 capability before authentication: IMAP4rev1 SASL-IR LOGIN-REFERRALS ID ENABLE IDLE NAMESPACE LITERAL+ AUTH=PLAIN AUTH=LOGIN AUTH
+Host1: cp8.ulimitserver.com says it has CAPABILITY for AUTHENTICATE LOGIN
+Host1: success login on [cp8.ulimitserver.com] with user [office@green-line.co.rs] auth [LOGIN]
+Host2: connecting and login on host2 [cp8.ulimitserver.com] port [993] with user [tester@ranitovic.in.rs]
+Host2 IP address: 194.146.59.72
+Host2 banner: * OK [CAPABILITY IMAP4rev1 SASL-IR LOGIN-REFERRALS ID ENABLE IDLE NAMESPACE LITERAL+ AUTH=PLAIN AUTH=LOGIN] Dovecot ready.
+Host2 capability before authentication: IMAP4rev1 SASL-IR LOGIN-REFERRALS ID ENABLE IDLE NAMESPACE LITERAL+ AUTH=PLAIN AUTH=LOGIN AUTH
+Host2: cp8.ulimitserver.com says it has CAPABILITY for AUTHENTICATE LOGIN
+Host2 info: authmech [LOGIN] user [tester@ranitovic.in.rs] authuser [] IsUnconnected []
+Host2 failure: Error login on [cp8.ulimitserver.com] with user [tester@ranitovic.in.rs] auth [LOGIN]: 2 NO [AUTHENTICATIONFAILED] Authentication failed.
+Exiting with return value 16 (EXIT_AUTHENTICATION_FAILURE) 1/20 nb_errors/max_errors
+Disconnecting from host1 cp8.ulimitserver.com user1 office@green-line.co.rs
+Log file is LOG_imapsync/2020_07_29_12_41_38_758_office@green-line.co.rs_tester@ranitovic.in.rs.txt ( to change it, use --logfile filepath ; or use --nolog to turn off logging )

LOG_imapsync/2020_07_29_12_44_14_956_office@green-line.co.rs_tester@ranitovic.in.rs.txt

@@ -0,0 +1,64 @@
+Here is imapsync 1.977 on host privremena, a linux system with 17.2/31.3 free GiB of RAM
+with Perl 5.28.1 and Mail::IMAPClient 3.42
+Transfer started at Wed Jul 29 12:44:14 2020
+PID is 13203 my PPID is 13202
+Log file is LOG_imapsync/2020_07_29_12_44_14_956_office@green-line.co.rs_tester@ranitovic.in.rs.txt ( to change it, use --logfile path ; or use --nolog to turn off logging )
+Load is 0.82 0.58 0.42 1/1193 on 2 cores
+Current directory is /root/imapsync-master
+Real user id is root (uid 0)
+Effective user id is root (euid 0)
+$RCSfile: imapsync,v $ $Revision: 1.977 $ $Date: 2019/12/23 20:18:02 $ 
+Command line used, run by /usr/bin/perl:
+./imapsync --addheader --automap --host1 cp8.ulimitserver.com --host2 cp8.ulimitserver.com --password1 MASKED --password2 MASKED --user1 office@green-line.co.rs --user2 tester@ranitovic.in.rs
+Temp directory is . ( to change it use --tmpdir dirpath )
+Under cgi context
+Umask set with 0077 (was 0022)
+REMOTE_ADDR is ::ffff:89.216.99.93
+HTTP_REFERER is http://148.251.112.220:8080/
+HTTP_USER_AGENT is Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Firefox/78.0
+SERVER_SOFTWARE is ./webserver
+SERVER_PORT is 8080
+HTTP_COOKIE is imapsync_runs=1; 686c9b6492d74d6d7c41621a12c6956f=la6q3dnkojbe6vjjq7boesovf2
+kill -QUIT 13203 # special behavior: call to sub catch_exit
+kill -TERM 13203 # special behavior: call to sub catch_exit
+kill -INT 13203 # special behavior: call to sub catch_reconnect
+kill -HUP 13203 # special behavior: call to sub catch_print
+kill -USR1 13203 # special behavior: call to sub toggle_sleep
+File ./imapsync_cp8.ulimitserver.com_office@green-line.co.rs_cp8.ulimitserver.com_tester@ranitovic.in.rs.pid does not exist
+Error reading file ./imapsync_cp8.ulimitserver.com_office@green-line.co.rs_cp8.ulimitserver.com_tester@ranitovic.in.rs.pid : No such file or directory
+PID file is ./imapsync_cp8.ulimitserver.com_office@green-line.co.rs_cp8.ulimitserver.com_tester@ranitovic.in.rs.pid ( to change it, use --pidfile filepath ; to avoid it use --pidfile "" )
+Writing my PID 13203 in ./imapsync_cp8.ulimitserver.com_office@green-line.co.rs_cp8.ulimitserver.com_tester@ranitovic.in.rs.pid
+Writing also my logfile name in ./imapsync_cp8.ulimitserver.com_office@green-line.co.rs_cp8.ulimitserver.com_tester@ranitovic.in.rs.pid : LOG_imapsync/2020_07_29_12_44_14_956_office@green-line.co.rs_tester@ranitovic.in.rs.txt
+Info: will resync flags for already transferred messages. Use --noresyncflags to not resync flags.
+Host1: probing ssl on port 993 ( use --nosslcheck to avoid this ssl probe ) 
+Host1: sslcheck detected open ssl port 993 so turning ssl on (use --nossl1 --notls1 to turn off SSL and TLS wizardry)
+Host2: probing ssl on port 993 ( use --nosslcheck to avoid this ssl probe ) 
+Host2: sslcheck detected open ssl port 993 so turning ssl on (use --nossl2 --notls2 to turn off SSL and TLS wizardry)
+SSL debug mode level is --debugssl 1 (can be set from 0 meaning no debug to 4 meaning max debug)
+Host1: SSL default mode is like --sslargs1 "SSL_verify_mode=0", meaning for host1 SSL_VERIFY_NONE, ie, do not check the certificate server.
+Host1: Use --sslargs1 SSL_verify_mode=1 to have SSL_VERIFY_PEER, ie, check the certificate server of host1
+Host2: SSL default mode is like --sslargs2 "SSL_verify_mode=0", meaning for host2 SSL_VERIFY_NONE, ie, do not check the certificate server.
+Host2: Use --sslargs2 SSL_verify_mode=1 to have SSL_VERIFY_PEER, ie, check the certificate server of host2
+Info: turned ON syncinternaldates, will set the internal dates (arrival dates) on host2 same as host1.
+Host1: will try to use LOGIN authentication on host1
+Host2: will try to use LOGIN authentication on host2
+Host1: imap connection timeout is 120 seconds
+Host2: imap connection timeout is 120 seconds
+Host1: IMAP server [cp8.ulimitserver.com] port [993] user [office@green-line.co.rs]
+Host2: IMAP server [cp8.ulimitserver.com] port [993] user [tester@ranitovic.in.rs]
+Host1: connecting and login on host1 [cp8.ulimitserver.com] port [993] with user [office@green-line.co.rs]
+Host1 IP address: 194.146.59.72
+Host1 banner: * OK [CAPABILITY IMAP4rev1 SASL-IR LOGIN-REFERRALS ID ENABLE IDLE NAMESPACE LITERAL+ AUTH=PLAIN AUTH=LOGIN] Dovecot ready.
+Host1 capability before authentication: IMAP4rev1 SASL-IR LOGIN-REFERRALS ID ENABLE IDLE NAMESPACE LITERAL+ AUTH=PLAIN AUTH=LOGIN AUTH
+Host1: cp8.ulimitserver.com says it has CAPABILITY for AUTHENTICATE LOGIN
+Host1: success login on [cp8.ulimitserver.com] with user [office@green-line.co.rs] auth [LOGIN]
+Host2: connecting and login on host2 [cp8.ulimitserver.com] port [993] with user [tester@ranitovic.in.rs]
+Host2 IP address: 194.146.59.72
+Host2 banner: * OK [CAPABILITY IMAP4rev1 SASL-IR LOGIN-REFERRALS ID ENABLE IDLE NAMESPACE LITERAL+ AUTH=PLAIN AUTH=LOGIN] Dovecot ready.
+Host2 capability before authentication: IMAP4rev1 SASL-IR LOGIN-REFERRALS ID ENABLE IDLE NAMESPACE LITERAL+ AUTH=PLAIN AUTH=LOGIN AUTH
+Host2: cp8.ulimitserver.com says it has CAPABILITY for AUTHENTICATE LOGIN
+Host2 info: authmech [LOGIN] user [tester@ranitovic.in.rs] authuser [] IsUnconnected []
+Host2 failure: Error login on [cp8.ulimitserver.com] with user [tester@ranitovic.in.rs] auth [LOGIN]: 2 NO [AUTHENTICATIONFAILED] Authentication failed.
+Exiting with return value 16 (EXIT_AUTHENTICATION_FAILURE) 1/20 nb_errors/max_errors
+Disconnecting from host1 cp8.ulimitserver.com user1 office@green-line.co.rs
+Log file is LOG_imapsync/2020_07_29_12_44_14_956_office@green-line.co.rs_tester@ranitovic.in.rs.txt ( to change it, use --logfile filepath ; or use --nolog to turn off logging )

LOG_imapsync/2020_07_29_14_23_24_648_office@green-line.co.rs_tester@ranitovic.in.rs.txt

@@ -0,0 +1,321 @@
+Here is imapsync 1.977 on host privremena, a linux system with 17.6/31.3 free GiB of RAM
+with Perl 5.28.1 and Mail::IMAPClient 3.42
+Transfer started at Wed Jul 29 14:23:24 2020
+PID is 18370 my PPID is 18369
+Log file is LOG_imapsync/2020_07_29_14_23_24_648_office@green-line.co.rs_tester@ranitovic.in.rs.txt ( to change it, use --logfile path ; or use --nolog to turn off logging )
+Load is 0.34 0.30 0.35 1/1188 on 2 cores
+Current directory is /root/imapsync-master
+Real user id is root (uid 0)
+Effective user id is root (euid 0)
+$RCSfile: imapsync,v $ $Revision: 1.977 $ $Date: 2019/12/23 20:18:02 $ 
+Command line used, run by /usr/bin/perl:
+./imapsync --addheader --automap --host1 cp8.ulimitserver.com --host2 cp8.ulimitserver.com --password1 MASKED --password2 MASKED --user1 office@green-line.co.rs --user2 tester@ranitovic.in.rs
+Temp directory is . ( to change it use --tmpdir dirpath )
+Under cgi context
+Umask set with 0077 (was 0022)
+REMOTE_ADDR is ::ffff:89.216.99.93
+HTTP_REFERER is http://148.251.112.220:8080/
+HTTP_USER_AGENT is Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Firefox/78.0
+SERVER_SOFTWARE is ./webserver
+SERVER_PORT is 8080
+HTTP_COOKIE is imapsync_runs=4; 686c9b6492d74d6d7c41621a12c6956f=la6q3dnkojbe6vjjq7boesovf2
+kill -QUIT 18370 # special behavior: call to sub catch_exit
+kill -TERM 18370 # special behavior: call to sub catch_exit
+kill -INT 18370 # special behavior: call to sub catch_reconnect
+kill -HUP 18370 # special behavior: call to sub catch_print
+kill -USR1 18370 # special behavior: call to sub toggle_sleep
+File ./imapsync_cp8.ulimitserver.com_office@green-line.co.rs_cp8.ulimitserver.com_tester@ranitovic.in.rs.pid does not exist
+Error reading file ./imapsync_cp8.ulimitserver.com_office@green-line.co.rs_cp8.ulimitserver.com_tester@ranitovic.in.rs.pid : No such file or directory
+PID file is ./imapsync_cp8.ulimitserver.com_office@green-line.co.rs_cp8.ulimitserver.com_tester@ranitovic.in.rs.pid ( to change it, use --pidfile filepath ; to avoid it use --pidfile "" )
+Writing my PID 18370 in ./imapsync_cp8.ulimitserver.com_office@green-line.co.rs_cp8.ulimitserver.com_tester@ranitovic.in.rs.pid
+Writing also my logfile name in ./imapsync_cp8.ulimitserver.com_office@green-line.co.rs_cp8.ulimitserver.com_tester@ranitovic.in.rs.pid : LOG_imapsync/2020_07_29_14_23_24_648_office@green-line.co.rs_tester@ranitovic.in.rs.txt
+Info: will resync flags for already transferred messages. Use --noresyncflags to not resync flags.
+Host1: probing ssl on port 993 ( use --nosslcheck to avoid this ssl probe ) 
+Host1: sslcheck detected open ssl port 993 so turning ssl on (use --nossl1 --notls1 to turn off SSL and TLS wizardry)
+Host2: probing ssl on port 993 ( use --nosslcheck to avoid this ssl probe ) 
+Host2: sslcheck detected open ssl port 993 so turning ssl on (use --nossl2 --notls2 to turn off SSL and TLS wizardry)
+SSL debug mode level is --debugssl 1 (can be set from 0 meaning no debug to 4 meaning max debug)
+Host1: SSL default mode is like --sslargs1 "SSL_verify_mode=0", meaning for host1 SSL_VERIFY_NONE, ie, do not check the certificate server.
+Host1: Use --sslargs1 SSL_verify_mode=1 to have SSL_VERIFY_PEER, ie, check the certificate server of host1
+Host2: SSL default mode is like --sslargs2 "SSL_verify_mode=0", meaning for host2 SSL_VERIFY_NONE, ie, do not check the certificate server.
+Host2: Use --sslargs2 SSL_verify_mode=1 to have SSL_VERIFY_PEER, ie, check the certificate server of host2
+Info: turned ON syncinternaldates, will set the internal dates (arrival dates) on host2 same as host1.
+Host1: will try to use LOGIN authentication on host1
+Host2: will try to use LOGIN authentication on host2
+Host1: imap connection timeout is 120 seconds
+Host2: imap connection timeout is 120 seconds
+Host1: IMAP server [cp8.ulimitserver.com] port [993] user [office@green-line.co.rs]
+Host2: IMAP server [cp8.ulimitserver.com] port [993] user [tester@ranitovic.in.rs]
+Host1: connecting and login on host1 [cp8.ulimitserver.com] port [993] with user [office@green-line.co.rs]
+Host1 IP address: 194.146.59.72
+Host1 banner: * OK [CAPABILITY IMAP4rev1 SASL-IR LOGIN-REFERRALS ID ENABLE IDLE NAMESPACE LITERAL+ AUTH=PLAIN AUTH=LOGIN] Dovecot ready.
+Host1 capability before authentication: IMAP4rev1 SASL-IR LOGIN-REFERRALS ID ENABLE IDLE NAMESPACE LITERAL+ AUTH=PLAIN AUTH=LOGIN AUTH
+Host1: cp8.ulimitserver.com says it has CAPABILITY for AUTHENTICATE LOGIN
+Host1: success login on [cp8.ulimitserver.com] with user [office@green-line.co.rs] auth [LOGIN]
+Host2: connecting and login on host2 [cp8.ulimitserver.com] port [993] with user [tester@ranitovic.in.rs]
+Host2 IP address: 194.146.59.72
+Host2 banner: * OK [CAPABILITY IMAP4rev1 SASL-IR LOGIN-REFERRALS ID ENABLE IDLE NAMESPACE LITERAL+ AUTH=PLAIN AUTH=LOGIN] Dovecot ready.
+Host2 capability before authentication: IMAP4rev1 SASL-IR LOGIN-REFERRALS ID ENABLE IDLE NAMESPACE LITERAL+ AUTH=PLAIN AUTH=LOGIN AUTH
+Host2: cp8.ulimitserver.com says it has CAPABILITY for AUTHENTICATE LOGIN
+Host2: success login on [cp8.ulimitserver.com] with user [tester@ranitovic.in.rs] auth [LOGIN]
+Host1: state Authenticated
+Host2: state Authenticated
+Host1 capability once authenticated: IMAP4rev1 SASL-IR LOGIN-REFERRALS ID ENABLE IDLE SORT SORT=DISPLAY THREAD=REFERENCES THREAD=REFS THREAD=ORDEREDSUBJECT MULTIAPPEND URL-PARTIAL CATENATE UNSELECT CHILDREN NAMESPACE UIDPLUS LIST-EXTENDED I18NLEVEL=1 CONDSTORE QRESYNC ESEARCH ESORT SEARCHRES WITHIN CONTEXT=SEARCH LIST-STATUS BINARY MOVE SNIPPET=FUZZY PREVIEW=FUZZY STATUS=SIZE NAMESPACE LITERAL+ NOTIFY SPECIAL-USE COMPRESS=DEFLATE QUOTA THREAD I18NLEVEL CONTEXT SNIPPET PREVIEW STATUS COMPRESS
+Host2 capability once authenticated: IMAP4rev1 SASL-IR LOGIN-REFERRALS ID ENABLE IDLE SORT SORT=DISPLAY THREAD=REFERENCES THREAD=REFS THREAD=ORDEREDSUBJECT MULTIAPPEND URL-PARTIAL CATENATE UNSELECT CHILDREN NAMESPACE UIDPLUS LIST-EXTENDED I18NLEVEL=1 CONDSTORE QRESYNC ESEARCH ESORT SEARCHRES WITHIN CONTEXT=SEARCH LIST-STATUS BINARY MOVE SNIPPET=FUZZY PREVIEW=FUZZY STATUS=SIZE NAMESPACE LITERAL+ NOTIFY SPECIAL-USE COMPRESS=DEFLATE QUOTA THREAD I18NLEVEL CONTEXT SNIPPET PREVIEW STATUS COMPRESS
+
+Host1: found ID capability. Sending/receiving ID, presented in raw IMAP for now.
+In order to avoid sending/receiving ID, use option --noid
+Sending: 4 ID ("name" "imapsync" "version" "1.977" "os" "linux" "vendor" "Gilles LAMIRAL" "support-url" "https://imapsync.lamiral.info/" "date" "23-Dec-2019 20:18:02 +0000" "side" "host1")
+Sent 181 bytes
+Read: 	* ID ("name" "Dovecot")
+  	4 OK ID completed (0.001 + 0.000 secs).
+
+
+Host2: found ID capability. Sending/receiving ID, presented in raw IMAP for now.
+In order to avoid sending/receiving ID, use option --noid
+Sending: 4 ID ("name" "imapsync" "version" "1.977" "os" "linux" "vendor" "Gilles LAMIRAL" "support-url" "https://imapsync.lamiral.info/" "date" "23-Dec-2019 20:18:02 +0000" "side" "host2")
+Sent 181 bytes
+Read: 	* ID ("name" "Dovecot")
+  	4 OK ID completed (0.001 + 0.000 secs).
+
+
+Host2: found quota, presented in raw IMAP
+Sending: 5 GETQUOTAROOT INBOX
+Sent 22 bytes
+Read: 	* QUOTAROOT INBOX Mailbox "cPanel Account"
+  	* QUOTA Mailbox (MESSAGE 12341 2147483647)
+  	* QUOTA "cPanel Account" (STORAGE 0 52428800)
+  	5 OK Getquotaroot completed (0.001 + 0.000 secs).
+
+Host2: Quota current storage is 0 bytes. Limit is 53687091200 bytes. So 0.00 % full
+Host1: found 6 folders.
+Host2: found 7 folders.
+Host1: guessing separator from folder listing: [.]
+Host1: separator given by NAMESPACE: [.]
+Host2: guessing separator from folder listing: [.]
+Host2: separator given by NAMESPACE: [.]
+Host1: guessing prefix from folder listing: [INBOX.]
+Host1: prefix given by NAMESPACE: [INBOX.]
+Host2: guessing prefix from folder listing: [INBOX.]
+Host2: prefix given by NAMESPACE: [INBOX.]
+Host1: separator and prefix: [.][INBOX.]
+Host2: separator and prefix: [.][INBOX.]
+Including all folders found by default. Use --subscribed or --folder or --folderrec or --include to select specific folders. Use --exclude to unselect specific folders.
+Host1: Checking wanted folders exist. Use --nocheckfoldersexist to avoid this check (shared of public namespace targeted).
+Host1: Checking wanted folders are selectable. Use --nocheckselectable to avoid this check.
+Turned on automapping folders ( use --noautomap to turn off automapping )
+Host1: special INBOX.Archive        = \Archive
+Host1: special INBOX.Trash          = \Trash
+Host1: special INBOX.spam           = \Junk
+Host1: special INBOX.Sent           = \Sent
+Host1: special INBOX.Drafts         = \Drafts
+
+Host2: special INBOX.Archive        = \Archive
+Host2: special INBOX.Sent           = \Sent
+Host2: special INBOX.spam           = \Junk
+Host2: special INBOX.Trash          = \Trash
+Host2: special INBOX.Drafts         = \Drafts
+
+
+++++ Listing folders
+All foldernames are presented between brackets like [X] where X is the foldername.
+When a foldername contains non-ASCII characters it is presented in the form
+[X] = [Y] where
+X is the imap foldername you have to use in command line options and
+Y is the utf8 output just printed for convenience, to recognize it.
+
+Host1: folders list (first the raw imap format then the [X] = [Y]):
+* LIST (\HasChildren) "." INBOX
+* LIST (\HasNoChildren \Archive) "." INBOX.Archive
+* LIST (\HasNoChildren \Trash) "." INBOX.Trash
+* LIST (\HasNoChildren \Junk) "." INBOX.spam
+* LIST (\HasNoChildren \Sent) "." INBOX.Sent
+* LIST (\HasNoChildren \Drafts) "." INBOX.Drafts
+16 OK List completed (0.001 + 0.000 secs).
+
+[INBOX]
+[INBOX.Archive]
+[INBOX.Drafts]
+[INBOX.Sent]
+[INBOX.Trash]
+[INBOX.spam]
+
+Host2: folders list (first the raw imap format then the [X] = [Y]):
+* LIST (\HasChildren) "." INBOX
+* LIST (\HasNoChildren \Archive) "." INBOX.Archive
+* LIST (\HasNoChildren \UnMarked \Sent) "." INBOX.Sent
+* LIST (\HasNoChildren) "." INBOX.Junk
+* LIST (\HasNoChildren \Junk) "." INBOX.spam
+* LIST (\HasNoChildren \Trash) "." INBOX.Trash
+* LIST (\HasNoChildren \Drafts) "." INBOX.Drafts
+11 OK List completed (0.001 + 0.000 secs).
+
+[INBOX]
+[INBOX.Archive]
+[INBOX.Drafts]
+[INBOX.Junk]
+[INBOX.Sent]
+[INBOX.Trash]
+[INBOX.spam]
+
+Folders in host2 not in host1:
+[INBOX.Junk]
+
+Folders mapping from --automap feature (use --f1f2 to override any mapping):
+[INBOX.Trash]                            -> [INBOX.Trash]                           
+[INBOX.spam]                             -> [INBOX.spam]                            
+[INBOX.Drafts]                           -> [INBOX.Drafts]                          
+[INBOX.Sent]                             -> [INBOX.Sent]                            
+[INBOX.Archive]                          -> [INBOX.Archive]                         
+
+Host1: will not syncing empty folders on host1. Use --noskipemptyfolders to create them anyway on host2
+
+Folders sizes before the synchronization.
+You can remove foldersizes listings by using "--nofoldersizes" and "--nofoldersizesatend"
+but then you will also lose the ETA (Estimation Time of Arrival) given after each message copy.
+Host1 folder     1/6 [INBOX]                             Size: 3606018126 Messages: 12338 Biggest:  10176467
+Host2 folder     1/6 [INBOX]                             Size: 3605929263 Messages: 12337 Biggest:  10176467
+Host2-Host1                                                       -88863              -1                  0
+
+Host1 folder     2/6 [INBOX.Archive]                     Size:         0 Messages:     0 Biggest:         0
+Host2 folder     2/6 [INBOX.Archive]                     Size:         0 Messages:     0 Biggest:         0
+Host2-Host1                                                            0               0                  0
+
+Host1 folder     3/6 [INBOX.Drafts]                      Size:         0 Messages:     0 Biggest:         0
+Host2 folder     3/6 [INBOX.Drafts]                      Size:         0 Messages:     0 Biggest:         0
+Host2-Host1                                                            0               0                  0
+
+Host1 folder     4/6 [INBOX.Sent]                        Size:         0 Messages:     0 Biggest:         0
+Host2 folder     4/6 [INBOX.Sent]                        Size:      1688 Messages:     4 Biggest:       568
+Host2-Host1                                                         1688               4                568
+
+Host1 folder     5/6 [INBOX.Trash]                       Size:         0 Messages:     0 Biggest:         0
+Host2 folder     5/6 [INBOX.Trash]                       Size:         0 Messages:     0 Biggest:         0
+Host2-Host1                                                            0               0                  0
+
+Host1 folder     6/6 [INBOX.spam]                        Size:         0 Messages:     0 Biggest:         0
+Host2 folder     6/6 [INBOX.spam]                        Size:         0 Messages:     0 Biggest:         0
+Host2-Host1                                                            0               0                  0
+
+Host1 Nb folders:                     6 folders
+Host2 Nb folders:                     6 folders
+
+Host1 Nb messages:                12338 messages
+Host2 Nb messages:                12341 messages
+
+Host1 Total size:            3606018126 bytes (3.358 GiB)
+Host2 Total size:            3605930951 bytes (3.358 GiB)
+
+Host1 Biggest message:         10176467 bytes (9.705 MiB)
+Host2 Biggest message:         10176467 bytes (9.705 MiB)
+
+Time spent on sizing:         4.2 seconds
+++++ Looping on each one of 6 folders to sync
+ETA: Wed Jul 29 14:23:29 2020  0 s  12338/12338 msgs left
+Folder     1/6 [INBOX]                             -> [INBOX]                            
+Host1: folder [INBOX] has 12338 messages in total (mentioned by SELECT)
+Host2: folder [INBOX] has 12337 messages in total (mentioned by SELECT)
+Host2: folder [INBOX] permanentflags: 
+Host1: folder [INBOX] considering 12338 messages
+Host2: folder [INBOX] considering 12337 messages
+Host1: folder [INBOX] selected 12338 messages, duplicates 3
+Host2: folder [INBOX] selected 12337 messages, duplicates 0
+ETA: Wed Jul 29 14:24:05 2020  0 s  0/12338 msgs left
+Folder     2/6 [INBOX.Archive]                     -> [INBOX.Archive]                    
+Host1: folder [INBOX.Archive] has 0 messages in total (mentioned by SELECT)
+Host1: skipping empty host1 folder [INBOX.Archive]
+ETA: Wed Jul 29 14:24:05 2020  0 s  0/12338 msgs left
+Folder     3/6 [INBOX.Drafts]                      -> [INBOX.Drafts]                     
+Host1: folder [INBOX.Drafts] has 0 messages in total (mentioned by SELECT)
+Host1: skipping empty host1 folder [INBOX.Drafts]
+ETA: Wed Jul 29 14:24:05 2020  0 s  0/12338 msgs left
+Folder     4/6 [INBOX.Sent]                        -> [INBOX.Sent]                       
+Host1: folder [INBOX.Sent] has 0 messages in total (mentioned by SELECT)
+Host1: skipping empty host1 folder [INBOX.Sent]
+ETA: Wed Jul 29 14:24:05 2020  0 s  0/12338 msgs left
+Folder     5/6 [INBOX.Trash]                       -> [INBOX.Trash]                      
+Host1: folder [INBOX.Trash] has 0 messages in total (mentioned by SELECT)
+Host1: skipping empty host1 folder [INBOX.Trash]
+ETA: Wed Jul 29 14:24:05 2020  0 s  0/12338 msgs left
+Folder     6/6 [INBOX.spam]                        -> [INBOX.spam]                       
+Host1: folder [INBOX.spam] has 0 messages in total (mentioned by SELECT)
+Host1: skipping empty host1 folder [INBOX.spam]
+ETA: Wed Jul 29 14:24:05 2020  0 s  0/12338 msgs left
+++++ End looping on each folder
+
+Folders sizes after the synchronization.
+You can remove this foldersizes listing by using  "--nofoldersizesatend"
+Host1 folder     1/6 [INBOX]                             Size: 3606018126 Messages: 12338 Biggest:  10176467
+Host2 folder     1/6 [INBOX]                             Size: 3605929263 Messages: 12337 Biggest:  10176467
+Host2-Host1                                                       -88863              -1                  0
+
+Host1 folder     2/6 [INBOX.Archive]                     Size:         0 Messages:     0 Biggest:         0
+Host2 folder     2/6 [INBOX.Archive]                     Size:         0 Messages:     0 Biggest:         0
+Host2-Host1                                                            0               0                  0
+
+Host1 folder     3/6 [INBOX.Drafts]                      Size:         0 Messages:     0 Biggest:         0
+Host2 folder     3/6 [INBOX.Drafts]                      Size:         0 Messages:     0 Biggest:         0
+Host2-Host1                                                            0               0                  0
+
+Host1 folder     4/6 [INBOX.Sent]                        Size:         0 Messages:     0 Biggest:         0
+Host2 folder     4/6 [INBOX.Sent]                        Size:      1688 Messages:     4 Biggest:       568
+Host2-Host1                                                         1688               4                568
+
+Host1 folder     5/6 [INBOX.Trash]                       Size:         0 Messages:     0 Biggest:         0
+Host2 folder     5/6 [INBOX.Trash]                       Size:         0 Messages:     0 Biggest:         0
+Host2-Host1                                                            0               0                  0
+
+Host1 folder     6/6 [INBOX.spam]                        Size:         0 Messages:     0 Biggest:         0
+Host2 folder     6/6 [INBOX.spam]                        Size:         0 Messages:     0 Biggest:         0
+Host2-Host1                                                            0               0                  0
+
+Host1 Nb folders:                     6 folders
+Host2 Nb folders:                     6 folders
+
+Host1 Nb messages:                12338 messages
+Host2 Nb messages:                12341 messages
+
+Host1 Total size:            3606018126 bytes (3.358 GiB)
+Host2 Total size:            3605930951 bytes (3.358 GiB)
+
+Host1 Biggest message:         10176467 bytes (9.705 MiB)
+Host2 Biggest message:         10176467 bytes (9.705 MiB)
+
+Time spent on sizing:         3.3 seconds
+++++ Statistics
+Transfer started on                     : Wed Jul 29 14:23:24 2020
+Transfer ended on                       : Wed Jul 29 14:24:08 2020
+Transfer time                           : 44.1 sec
+Folders synced                          : 6/6 synced
+Messages transferred                    : 0 
+Messages skipped                        : 12338
+Messages found duplicate on host1       : 3
+Messages found duplicate on host2       : 0
+Messages found crossduplicate on host2  : 0
+Messages void (noheader) on host1       : 0  
+Messages void (noheader) on host2       : 0
+Messages found in host1 not in host2    : 0 messages
+Messages found in host2 not in host1    : 2 messages
+Messages deleted on host1               : 0
+Messages deleted on host2               : 0
+Total bytes transferred                 : 0 (0.000 KiB)
+Total bytes skipped                     : 3605826992 (3.358 GiB)
+Message rate                            : 0.0 messages/s
+Average bandwidth rate                  : 0.0 KiB/s
+Reconnections to host1                  : 0
+Reconnections to host2                  : 0
+Memory consumption at the end           : 224.9 MiB (started with 159.9 MiB)
+Load end is                             : 0.48 0.33 0.36 1/1186 on 2 cores
+Biggest message                         : 0 bytes (0.000 KiB)
+Memory/biggest message ratio            : NA
+Start difference host2 - host1          : 3 messages, -87175 bytes (-85.132 KiB)
+Final difference host2 - host1          : 3 messages, -87175 bytes (-85.132 KiB)
+The sync looks good, all 12335 identified messages in host1 are on host2.
+There is no unidentified message
+The sync is not strict, there are 2 messages in host2 that are not on host1. Use --delete2 to delete them and have a strict sync. (12337 identified messages in host2)
+Detected 0 errors
+
+Check if a new imapsync release is available by adding --releasecheck
+Homepage: https://imapsync.lamiral.info/
+Exiting with return value 0 (EX_OK: successful termination) 0/20 nb_errors/max_errors
+Log file is LOG_imapsync/2020_07_29_14_23_24_648_office@green-line.co.rs_tester@ranitovic.in.rs.txt ( to change it, use --logfile filepath ; or use --nolog to turn off logging )

LOG_imapsync/2020_07_30_13_53_27_381_pobednik@gimnastika.rs_pobednik@gimnastika.rs.txt

@@ -0,0 +1,54 @@
+Here is imapsync 1.977 on host privremena, a linux system with 17.2/31.3 free GiB of RAM
+with Perl 5.28.1 and Mail::IMAPClient 3.42
+Transfer started at Thu Jul 30 13:53:27 2020
+PID is 17630 my PPID is 17629
+Log file is LOG_imapsync/2020_07_30_13_53_27_381_pobednik@gimnastika.rs_pobednik@gimnastika.rs.txt ( to change it, use --logfile path ; or use --nolog to turn off logging )
+Load is 0.27 0.44 0.45 1/1205 on 2 cores
+Current directory is /root/imapsync-master
+Real user id is root (uid 0)
+Effective user id is root (euid 0)
+$RCSfile: imapsync,v $ $Revision: 1.977 $ $Date: 2019/12/23 20:18:02 $ 
+Command line used, run by /usr/bin/perl:
+./imapsync --addheader --automap --host1 188.93.124.96 --host2 194.146.59.74 --password1 MASKED --password2 MASKED --user1 pobednik@gimnastika.rs --user2 pobednik@gimnastika.rs
+Temp directory is . ( to change it use --tmpdir dirpath )
+Under cgi context
+Umask set with 0077 (was 0022)
+REMOTE_ADDR is ::ffff:93.86.60.84
+HTTP_REFERER is http://148.251.112.220:8080/
+HTTP_USER_AGENT is Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:79.0) Gecko/20100101 Firefox/79.0
+SERVER_SOFTWARE is ./webserver
+SERVER_PORT is 8080
+kill -QUIT 17630 # special behavior: call to sub catch_exit
+kill -TERM 17630 # special behavior: call to sub catch_exit
+kill -INT 17630 # special behavior: call to sub catch_reconnect
+kill -HUP 17630 # special behavior: call to sub catch_print
+kill -USR1 17630 # special behavior: call to sub toggle_sleep
+File ./imapsync_188.93.124.96_pobednik@gimnastika.rs_194.146.59.74_pobednik@gimnastika.rs.pid does not exist
+Error reading file ./imapsync_188.93.124.96_pobednik@gimnastika.rs_194.146.59.74_pobednik@gimnastika.rs.pid : No such file or directory
+PID file is ./imapsync_188.93.124.96_pobednik@gimnastika.rs_194.146.59.74_pobednik@gimnastika.rs.pid ( to change it, use --pidfile filepath ; to avoid it use --pidfile "" )
+Writing my PID 17630 in ./imapsync_188.93.124.96_pobednik@gimnastika.rs_194.146.59.74_pobednik@gimnastika.rs.pid
+Writing also my logfile name in ./imapsync_188.93.124.96_pobednik@gimnastika.rs_194.146.59.74_pobednik@gimnastika.rs.pid : LOG_imapsync/2020_07_30_13_53_27_381_pobednik@gimnastika.rs_pobednik@gimnastika.rs.txt
+Info: will resync flags for already transferred messages. Use --noresyncflags to not resync flags.
+Host1: probing ssl on port 993 ( use --nosslcheck to avoid this ssl probe ) 
+Host1: sslcheck did not detected open ssl port 993. Will use standard 143 port.
+Host2: probing ssl on port 993 ( use --nosslcheck to avoid this ssl probe ) 
+Host2: sslcheck detected open ssl port 993 so turning ssl on (use --nossl2 --notls2 to turn off SSL and TLS wizardry)
+SSL debug mode level is --debugssl 1 (can be set from 0 meaning no debug to 4 meaning max debug)
+Host2: SSL default mode is like --sslargs2 "SSL_verify_mode=0", meaning for host2 SSL_VERIFY_NONE, ie, do not check the certificate server.
+Host2: Use --sslargs2 SSL_verify_mode=1 to have SSL_VERIFY_PEER, ie, check the certificate server of host2
+Info: turned ON syncinternaldates, will set the internal dates (arrival dates) on host2 same as host1.
+Host1: will try to use LOGIN authentication on host1
+Host2: will try to use LOGIN authentication on host2
+Host1: imap connection timeout is 120 seconds
+Host2: imap connection timeout is 120 seconds
+Host1: IMAP server [188.93.124.96] port [143] user [pobednik@gimnastika.rs]
+Host2: IMAP server [194.146.59.74] port [993] user [pobednik@gimnastika.rs]
+Host1: connecting and login on host1 [188.93.124.96] port [143] with user [pobednik@gimnastika.rs]
+Host1 IP address: 188.93.124.96
+Host1 banner: * OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE IDLE AUTH=PLAIN AUTH=LOGIN] Dovecot ready.
+Host1 capability before authentication: IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE IDLE AUTH=PLAIN AUTH=LOGIN AUTH
+Host1: 188.93.124.96 says it has CAPABILITY for AUTHENTICATE LOGIN
+Host1 info: authmech [LOGIN] user [pobednik@gimnastika.rs] authuser [] IsUnconnected []
+Host1 failure: Error login on [188.93.124.96] with user [pobednik@gimnastika.rs] auth [LOGIN]: 2 NO [AUTHENTICATIONFAILED] Authentication failed.
+Exiting with return value 16 (EXIT_AUTHENTICATION_FAILURE) 1/20 nb_errors/max_errors
+Log file is LOG_imapsync/2020_07_30_13_53_27_381_pobednik@gimnastika.rs_pobednik@gimnastika.rs.txt ( to change it, use --logfile filepath ; or use --nolog to turn off logging )

LOG_imapsync/2020_07_30_13_54_59_990_pobednik@gimnastika.rs_pobednik@gimnastika.rs.txt

@@ -0,0 +1,55 @@
+Here is imapsync 1.977 on host privremena, a linux system with 17.2/31.3 free GiB of RAM
+with Perl 5.28.1 and Mail::IMAPClient 3.42
+Transfer started at Thu Jul 30 13:54:59 2020
+PID is 17703 my PPID is 17702
+Log file is LOG_imapsync/2020_07_30_13_54_59_990_pobednik@gimnastika.rs_pobednik@gimnastika.rs.txt ( to change it, use --logfile path ; or use --nolog to turn off logging )
+Load is 0.47 0.45 0.46 3/1191 on 2 cores
+Current directory is /root/imapsync-master
+Real user id is root (uid 0)
+Effective user id is root (euid 0)
+$RCSfile: imapsync,v $ $Revision: 1.977 $ $Date: 2019/12/23 20:18:02 $ 
+Command line used, run by /usr/bin/perl:
+./imapsync --addheader --automap --host1 188.93.124.96 --host2 194.146.59.74 --password1 MASKED --password2 MASKED --user1 pobednik@gimnastika.rs --user2 pobednik@gimnastika.rs
+Temp directory is . ( to change it use --tmpdir dirpath )
+Under cgi context
+Umask set with 0077 (was 0022)
+REMOTE_ADDR is ::ffff:93.86.60.84
+HTTP_REFERER is http://148.251.112.220:8080/
+HTTP_USER_AGENT is Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:79.0) Gecko/20100101 Firefox/79.0
+SERVER_SOFTWARE is ./webserver
+SERVER_PORT is 8080
+HTTP_COOKIE is imapsync_runs=1
+kill -QUIT 17703 # special behavior: call to sub catch_exit
+kill -TERM 17703 # special behavior: call to sub catch_exit
+kill -INT 17703 # special behavior: call to sub catch_reconnect
+kill -HUP 17703 # special behavior: call to sub catch_print
+kill -USR1 17703 # special behavior: call to sub toggle_sleep
+File ./imapsync_188.93.124.96_pobednik@gimnastika.rs_194.146.59.74_pobednik@gimnastika.rs.pid does not exist
+Error reading file ./imapsync_188.93.124.96_pobednik@gimnastika.rs_194.146.59.74_pobednik@gimnastika.rs.pid : No such file or directory
+PID file is ./imapsync_188.93.124.96_pobednik@gimnastika.rs_194.146.59.74_pobednik@gimnastika.rs.pid ( to change it, use --pidfile filepath ; to avoid it use --pidfile "" )
+Writing my PID 17703 in ./imapsync_188.93.124.96_pobednik@gimnastika.rs_194.146.59.74_pobednik@gimnastika.rs.pid
+Writing also my logfile name in ./imapsync_188.93.124.96_pobednik@gimnastika.rs_194.146.59.74_pobednik@gimnastika.rs.pid : LOG_imapsync/2020_07_30_13_54_59_990_pobednik@gimnastika.rs_pobednik@gimnastika.rs.txt
+Info: will resync flags for already transferred messages. Use --noresyncflags to not resync flags.
+Host1: probing ssl on port 993 ( use --nosslcheck to avoid this ssl probe ) 
+Host1: sslcheck did not detected open ssl port 993. Will use standard 143 port.
+Host2: probing ssl on port 993 ( use --nosslcheck to avoid this ssl probe ) 
+Host2: sslcheck detected open ssl port 993 so turning ssl on (use --nossl2 --notls2 to turn off SSL and TLS wizardry)
+SSL debug mode level is --debugssl 1 (can be set from 0 meaning no debug to 4 meaning max debug)
+Host2: SSL default mode is like --sslargs2 "SSL_verify_mode=0", meaning for host2 SSL_VERIFY_NONE, ie, do not check the certificate server.
+Host2: Use --sslargs2 SSL_verify_mode=1 to have SSL_VERIFY_PEER, ie, check the certificate server of host2
+Info: turned ON syncinternaldates, will set the internal dates (arrival dates) on host2 same as host1.
+Host1: will try to use LOGIN authentication on host1
+Host2: will try to use LOGIN authentication on host2
+Host1: imap connection timeout is 120 seconds
+Host2: imap connection timeout is 120 seconds
+Host1: IMAP server [188.93.124.96] port [143] user [pobednik@gimnastika.rs]
+Host2: IMAP server [194.146.59.74] port [993] user [pobednik@gimnastika.rs]
+Host1: connecting and login on host1 [188.93.124.96] port [143] with user [pobednik@gimnastika.rs]
+Host1 IP address: 188.93.124.96
+Host1 banner: * OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE IDLE AUTH=PLAIN AUTH=LOGIN] Dovecot ready.
+Host1 capability before authentication: IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE IDLE AUTH=PLAIN AUTH=LOGIN AUTH
+Host1: 188.93.124.96 says it has CAPABILITY for AUTHENTICATE LOGIN
+Host1 info: authmech [LOGIN] user [pobednik@gimnastika.rs] authuser [] IsUnconnected []
+Host1 failure: Error login on [188.93.124.96] with user [pobednik@gimnastika.rs] auth [LOGIN]: 2 NO [AUTHENTICATIONFAILED] Authentication failed.
+Exiting with return value 16 (EXIT_AUTHENTICATION_FAILURE) 1/20 nb_errors/max_errors
+Log file is LOG_imapsync/2020_07_30_13_54_59_990_pobednik@gimnastika.rs_pobednik@gimnastika.rs.txt ( to change it, use --logfile filepath ; or use --nolog to turn off logging )

LOG_imapsync/2020_07_30_13_59_24_827_pobednik@gimnastika.rs_pobednik@gimnastika.rs.txt

@@ -0,0 +1,55 @@
+Here is imapsync 1.977 on host privremena, a linux system with 17.2/31.3 free GiB of RAM
+with Perl 5.28.1 and Mail::IMAPClient 3.42
+Transfer started at Thu Jul 30 13:59:24 2020
+PID is 17986 my PPID is 17985
+Log file is LOG_imapsync/2020_07_30_13_59_24_827_pobednik@gimnastika.rs_pobednik@gimnastika.rs.txt ( to change it, use --logfile path ; or use --nolog to turn off logging )
+Load is 0.08 0.25 0.36 1/1211 on 2 cores
+Current directory is /root/imapsync-master
+Real user id is root (uid 0)
+Effective user id is root (euid 0)
+$RCSfile: imapsync,v $ $Revision: 1.977 $ $Date: 2019/12/23 20:18:02 $ 
+Command line used, run by /usr/bin/perl:
+./imapsync --addheader --automap --host1 188.93.124.96 --host2 194.146.59.74 --password1 MASKED --password2 MASKED --user1 pobednik@gimnastika.rs --user2 pobednik@gimnastika.rs
+Temp directory is . ( to change it use --tmpdir dirpath )
+Under cgi context
+Umask set with 0077 (was 0022)
+REMOTE_ADDR is ::ffff:93.86.60.84
+HTTP_REFERER is http://148.251.112.220:8080/
+HTTP_USER_AGENT is Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:79.0) Gecko/20100101 Firefox/79.0
+SERVER_SOFTWARE is ./webserver
+SERVER_PORT is 8080
+HTTP_COOKIE is imapsync_runs=2
+kill -QUIT 17986 # special behavior: call to sub catch_exit
+kill -TERM 17986 # special behavior: call to sub catch_exit
+kill -INT 17986 # special behavior: call to sub catch_reconnect
+kill -HUP 17986 # special behavior: call to sub catch_print
+kill -USR1 17986 # special behavior: call to sub toggle_sleep
+File ./imapsync_188.93.124.96_pobednik@gimnastika.rs_194.146.59.74_pobednik@gimnastika.rs.pid does not exist
+Error reading file ./imapsync_188.93.124.96_pobednik@gimnastika.rs_194.146.59.74_pobednik@gimnastika.rs.pid : No such file or directory
+PID file is ./imapsync_188.93.124.96_pobednik@gimnastika.rs_194.146.59.74_pobednik@gimnastika.rs.pid ( to change it, use --pidfile filepath ; to avoid it use --pidfile "" )
+Writing my PID 17986 in ./imapsync_188.93.124.96_pobednik@gimnastika.rs_194.146.59.74_pobednik@gimnastika.rs.pid
+Writing also my logfile name in ./imapsync_188.93.124.96_pobednik@gimnastika.rs_194.146.59.74_pobednik@gimnastika.rs.pid : LOG_imapsync/2020_07_30_13_59_24_827_pobednik@gimnastika.rs_pobednik@gimnastika.rs.txt
+Info: will resync flags for already transferred messages. Use --noresyncflags to not resync flags.
+Host1: probing ssl on port 993 ( use --nosslcheck to avoid this ssl probe ) 
+Host1: sslcheck did not detected open ssl port 993. Will use standard 143 port.
+Host2: probing ssl on port 993 ( use --nosslcheck to avoid this ssl probe ) 
+Host2: sslcheck detected open ssl port 993 so turning ssl on (use --nossl2 --notls2 to turn off SSL and TLS wizardry)
+SSL debug mode level is --debugssl 1 (can be set from 0 meaning no debug to 4 meaning max debug)
+Host2: SSL default mode is like --sslargs2 "SSL_verify_mode=0", meaning for host2 SSL_VERIFY_NONE, ie, do not check the certificate server.
+Host2: Use --sslargs2 SSL_verify_mode=1 to have SSL_VERIFY_PEER, ie, check the certificate server of host2
+Info: turned ON syncinternaldates, will set the internal dates (arrival dates) on host2 same as host1.
+Host1: will try to use LOGIN authentication on host1
+Host2: will try to use LOGIN authentication on host2
+Host1: imap connection timeout is 120 seconds
+Host2: imap connection timeout is 120 seconds
+Host1: IMAP server [188.93.124.96] port [143] user [pobednik@gimnastika.rs]
+Host2: IMAP server [194.146.59.74] port [993] user [pobednik@gimnastika.rs]
+Host1: connecting and login on host1 [188.93.124.96] port [143] with user [pobednik@gimnastika.rs]
+Host1 IP address: 188.93.124.96
+Host1 banner: * OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE IDLE AUTH=PLAIN AUTH=LOGIN] Dovecot ready.
+Host1 capability before authentication: IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE IDLE AUTH=PLAIN AUTH=LOGIN AUTH
+Host1: 188.93.124.96 says it has CAPABILITY for AUTHENTICATE LOGIN
+Host1 info: authmech [LOGIN] user [pobednik@gimnastika.rs] authuser [] IsUnconnected []
+Host1 failure: Error login on [188.93.124.96] with user [pobednik@gimnastika.rs] auth [LOGIN]: 2 NO [AUTHENTICATIONFAILED] Authentication failed.
+Exiting with return value 16 (EXIT_AUTHENTICATION_FAILURE) 1/20 nb_errors/max_errors
+Log file is LOG_imapsync/2020_07_30_13_59_24_827_pobednik@gimnastika.rs_pobednik@gimnastika.rs.txt ( to change it, use --logfile filepath ; or use --nolog to turn off logging )

LOG_imapsync/2020_10_29_00_50_42_413_forumbb@beobuild.rs_forumbb@beobuild.rs.txt

@@ -0,0 +1,307 @@
+Here is imapsync 1.977 on host privremena, a linux system with 18.8/31.3 free GiB of RAM
+with Perl 5.28.1 and Mail::IMAPClient 3.42
+Transfer started at Thu Oct 29 00:50:42 2020
+PID is 8126 my PPID is 8125
+Log file is LOG_imapsync/2020_10_29_00_50_42_413_forumbb@beobuild.rs_forumbb@beobuild.rs.txt ( to change it, use --logfile path ; or use --nolog to turn off logging )
+Load is 0.43 0.37 0.45 4/1197 on 2 cores
+Current directory is /root/imapsync-master
+Real user id is root (uid 0)
+Effective user id is root (euid 0)
+$RCSfile: imapsync,v $ $Revision: 1.977 $ $Date: 2019/12/23 20:18:02 $ 
+Command line used, run by /usr/bin/perl:
+./imapsync --addheader --automap --host1 cp8.ulimitserver.com --host2 194.146.57.67 --password1 MASKED --password2 MASKED --user1 forumbb@beobuild.rs --user2 forumbb@beobuild.rs
+Temp directory is . ( to change it use --tmpdir dirpath )
+Under cgi context
+Umask set with 0077 (was 0022)
+REMOTE_ADDR is ::ffff:93.86.60.84
+HTTP_REFERER is http://148.251.112.220:8080/
+HTTP_USER_AGENT is Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Firefox/78.0
+SERVER_SOFTWARE is ./webserver
+SERVER_PORT is 8080
+HTTP_COOKIE is imapsync_runs=4
+kill -QUIT 8126 # special behavior: call to sub catch_exit
+kill -TERM 8126 # special behavior: call to sub catch_exit
+kill -INT 8126 # special behavior: call to sub catch_reconnect
+kill -HUP 8126 # special behavior: call to sub catch_print
+kill -USR1 8126 # special behavior: call to sub toggle_sleep
+File ./imapsync_cp8.ulimitserver.com_forumbb@beobuild.rs_194.146.57.67_forumbb@beobuild.rs.pid does not exist
+Error reading file ./imapsync_cp8.ulimitserver.com_forumbb@beobuild.rs_194.146.57.67_forumbb@beobuild.rs.pid : No such file or directory
+PID file is ./imapsync_cp8.ulimitserver.com_forumbb@beobuild.rs_194.146.57.67_forumbb@beobuild.rs.pid ( to change it, use --pidfile filepath ; to avoid it use --pidfile "" )
+Writing my PID 8126 in ./imapsync_cp8.ulimitserver.com_forumbb@beobuild.rs_194.146.57.67_forumbb@beobuild.rs.pid
+Writing also my logfile name in ./imapsync_cp8.ulimitserver.com_forumbb@beobuild.rs_194.146.57.67_forumbb@beobuild.rs.pid : LOG_imapsync/2020_10_29_00_50_42_413_forumbb@beobuild.rs_forumbb@beobuild.rs.txt
+Info: will resync flags for already transferred messages. Use --noresyncflags to not resync flags.
+Host1: probing ssl on port 993 ( use --nosslcheck to avoid this ssl probe ) 
+Host1: sslcheck detected open ssl port 993 so turning ssl on (use --nossl1 --notls1 to turn off SSL and TLS wizardry)
+Host2: probing ssl on port 993 ( use --nosslcheck to avoid this ssl probe ) 
+Host2: sslcheck detected open ssl port 993 so turning ssl on (use --nossl2 --notls2 to turn off SSL and TLS wizardry)
+SSL debug mode level is --debugssl 1 (can be set from 0 meaning no debug to 4 meaning max debug)
+Host1: SSL default mode is like --sslargs1 "SSL_verify_mode=0", meaning for host1 SSL_VERIFY_NONE, ie, do not check the certificate server.
+Host1: Use --sslargs1 SSL_verify_mode=1 to have SSL_VERIFY_PEER, ie, check the certificate server of host1
+Host2: SSL default mode is like --sslargs2 "SSL_verify_mode=0", meaning for host2 SSL_VERIFY_NONE, ie, do not check the certificate server.
+Host2: Use --sslargs2 SSL_verify_mode=1 to have SSL_VERIFY_PEER, ie, check the certificate server of host2
+Info: turned ON syncinternaldates, will set the internal dates (arrival dates) on host2 same as host1.
+Host1: will try to use LOGIN authentication on host1
+Host2: will try to use LOGIN authentication on host2
+Host1: imap connection timeout is 120 seconds
+Host2: imap connection timeout is 120 seconds
+Host1: IMAP server [cp8.ulimitserver.com] port [993] user [forumbb@beobuild.rs]
+Host2: IMAP server [194.146.57.67] port [993] user [forumbb@beobuild.rs]
+Host1: connecting and login on host1 [cp8.ulimitserver.com] port [993] with user [forumbb@beobuild.rs]
+Host1 IP address: 194.146.59.72
+Host1 banner: * OK [CAPABILITY IMAP4rev1 SASL-IR LOGIN-REFERRALS ID ENABLE IDLE NAMESPACE LITERAL+ AUTH=PLAIN AUTH=LOGIN] Dovecot ready.
+Host1 capability before authentication: IMAP4rev1 SASL-IR LOGIN-REFERRALS ID ENABLE IDLE NAMESPACE LITERAL+ AUTH=PLAIN AUTH=LOGIN AUTH
+Host1: cp8.ulimitserver.com says it has CAPABILITY for AUTHENTICATE LOGIN
+Host1: success login on [cp8.ulimitserver.com] with user [forumbb@beobuild.rs] auth [LOGIN]
+Host2: connecting and login on host2 [194.146.57.67] port [993] with user [forumbb@beobuild.rs]
+Host2 IP address: 194.146.57.67
+Host2 banner: * OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE IDLE AUTH=PLAIN AUTH=LOGIN AUTH=DIGEST-MD5 AUTH=CRAM-MD5] Dovecot (Ubuntu) ready.
+Host2 capability before authentication: IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE IDLE AUTH=PLAIN AUTH=LOGIN AUTH=DIGEST-MD5 AUTH=CRAM-MD5 AUTH
+Host2: 194.146.57.67 says it has CAPABILITY for AUTHENTICATE LOGIN
+Host2: success login on [194.146.57.67] with user [forumbb@beobuild.rs] auth [LOGIN]
+Host1: state Authenticated
+Host2: state Authenticated
+Host1 capability once authenticated: IMAP4rev1 SASL-IR LOGIN-REFERRALS ID ENABLE IDLE SORT SORT=DISPLAY THREAD=REFERENCES THREAD=REFS THREAD=ORDEREDSUBJECT MULTIAPPEND URL-PARTIAL CATENATE UNSELECT CHILDREN NAMESPACE UIDPLUS LIST-EXTENDED I18NLEVEL=1 CONDSTORE QRESYNC ESEARCH ESORT SEARCHRES WITHIN CONTEXT=SEARCH LIST-STATUS BINARY MOVE SNIPPET=FUZZY PREVIEW=FUZZY STATUS=SIZE NAMESPACE LITERAL+ NOTIFY SPECIAL-USE COMPRESS=DEFLATE QUOTA THREAD I18NLEVEL CONTEXT SNIPPET PREVIEW STATUS COMPRESS
+Host2 capability once authenticated: IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE IDLE SORT SORT=DISPLAY THREAD=REFERENCES THREAD=REFS THREAD=ORDEREDSUBJECT MULTIAPPEND URL-PARTIAL CATENATE UNSELECT CHILDREN NAMESPACE UIDPLUS LIST-EXTENDED I18NLEVEL=1 CONDSTORE QRESYNC ESEARCH ESORT SEARCHRES WITHIN CONTEXT=SEARCH LIST-STATUS BINARY MOVE THREAD I18NLEVEL CONTEXT
+
+Host1: found ID capability. Sending/receiving ID, presented in raw IMAP for now.
+In order to avoid sending/receiving ID, use option --noid
+Sending: 4 ID ("name" "imapsync" "version" "1.977" "os" "linux" "vendor" "Gilles LAMIRAL" "support-url" "https://imapsync.lamiral.info/" "date" "23-Dec-2019 20:18:02 +0000" "side" "host1")
+Sent 181 bytes
+Read: 	* ID ("name" "Dovecot")
+  	4 OK ID completed (0.001 + 0.000 secs).
+
+
+Host2: found ID capability. Sending/receiving ID, presented in raw IMAP for now.
+In order to avoid sending/receiving ID, use option --noid
+Sending: 4 ID ("name" "imapsync" "version" "1.977" "os" "linux" "vendor" "Gilles LAMIRAL" "support-url" "https://imapsync.lamiral.info/" "date" "23-Dec-2019 20:18:02 +0000" "side" "host2")
+Sent 181 bytes
+Read: 	* ID ("name" "Dovecot")
+  	4 OK ID completed (0.001 + 0.000 secs).
+
+Host1: found 7 folders.
+Host2: found 1 folders.
+Host1: guessing separator from folder listing: [.]
+Host1: separator given by NAMESPACE: [.]
+Host2: guessing separator from folder listing: [/]
+Host2: separator given by NAMESPACE: [.]
+Host1: guessing prefix from folder listing: [INBOX.]
+Host1: prefix given by NAMESPACE: [INBOX.]
+Host2: guessing prefix from folder listing: []
+Host2: prefix given by NAMESPACE: []
+Host1: separator and prefix: [.][INBOX.]
+Host2: separator and prefix: [.][]
+Including all folders found by default. Use --subscribed or --folder or --folderrec or --include to select specific folders. Use --exclude to unselect specific folders.
+Host1: Checking wanted folders exist. Use --nocheckfoldersexist to avoid this check (shared of public namespace targeted).
+Host1: Checking wanted folders are selectable. Use --nocheckselectable to avoid this check.
+Turned on automapping folders ( use --noautomap to turn off automapping )
+Host1: special INBOX.Sent           = \Sent
+Host1: special INBOX.spam           = \Junk
+Host1: special INBOX.Trash          = \Trash
+Host1: special INBOX.Drafts         = \Drafts
+Host1: special INBOX.Archive        = \Archive
+
+
+++++ Listing folders
+All foldernames are presented between brackets like [X] where X is the foldername.
+When a foldername contains non-ASCII characters it is presented in the form
+[X] = [Y] where
+X is the imap foldername you have to use in command line options and
+Y is the utf8 output just printed for convenience, to recognize it.
+
+Host1: folders list (first the raw imap format then the [X] = [Y]):
+* LIST (\HasChildren) "." INBOX
+* LIST (\HasNoChildren \Sent) "." INBOX.Sent
+* LIST (\HasNoChildren) "." INBOX.Junk
+* LIST (\HasNoChildren \Junk) "." INBOX.spam
+* LIST (\HasNoChildren \Trash) "." INBOX.Trash
+* LIST (\HasNoChildren \Drafts) "." INBOX.Drafts
+* LIST (\HasNoChildren \Archive) "." INBOX.Archive
+17 OK List completed (0.001 + 0.000 secs).
+
+[INBOX]
+[INBOX.Archive]
+[INBOX.Drafts]
+[INBOX.Junk]
+[INBOX.Sent]
+[INBOX.Trash]
+[INBOX.spam]
+
+Host2: folders list (first the raw imap format then the [X] = [Y]):
+* LIST (\HasNoChildren) "." INBOX
+10 OK List completed (0.001 + 0.000 secs).
+
+[INBOX]
+
+Host1: will not syncing empty folders on host1. Use --noskipemptyfolders to create them anyway on host2
+
+Folders sizes before the synchronization.
+You can remove foldersizes listings by using "--nofoldersizes" and "--nofoldersizesatend"
+but then you will also lose the ETA (Estimation Time of Arrival) given after each message copy.
+Host1 folder     1/7 [INBOX]                             Size:     80378 Messages:     1 Biggest:     80378
+Host2 folder     1/7 [INBOX]                             Size:         0 Messages:     0 Biggest:         0
+Host2-Host1                                                       -80378              -1             -80378
+
+Host1 folder     2/7 [INBOX.Archive]                     Size:         0 Messages:     0 Biggest:         0
+Host2 folder     2/7 [Archive]                            does not exist yet
+Host2-Host1                                                            0               0                  0
+
+Host1 folder     3/7 [INBOX.Drafts]                      Size:         0 Messages:     0 Biggest:         0
+Host2 folder     3/7 [Drafts]                             does not exist yet
+Host2-Host1                                                            0               0                  0
+
+Host1 folder     4/7 [INBOX.Junk]                        Size:         0 Messages:     0 Biggest:         0
+Host2 folder     4/7 [Junk]                               does not exist yet
+Host2-Host1                                                            0               0                  0
+
+Host1 folder     5/7 [INBOX.Sent]                        Size:         0 Messages:     0 Biggest:         0
+Host2 folder     5/7 [Sent]                               does not exist yet
+Host2-Host1                                                            0               0                  0
+
+Host1 folder     6/7 [INBOX.Trash]                       Size:      1055 Messages:     1 Biggest:      1055
+Host2 folder     6/7 [Trash]                              does not exist yet
+Host2-Host1                                                        -1055              -1              -1055
+
+Host1 folder     7/7 [INBOX.spam]                        Size:         0 Messages:     0 Biggest:         0
+Host2 folder     7/7 [spam]                               does not exist yet
+Host2-Host1                                                            0               0                  0
+
+Host1 Nb folders:                     7 folders
+Host2 Nb folders:                     7 folders
+
+Host1 Nb messages:                    2 messages
+Host2 Nb messages:                    0 messages
+
+Host1 Total size:                 81433 bytes (79.524 KiB)
+Host2 Total size:                     0 bytes (0.000 KiB)
+
+Host1 Biggest message:            80378 bytes (78.494 KiB)
+Host2 Biggest message:                0 bytes (0.000 KiB)
+
+Time spent on sizing:         2.0 seconds
+++++ Looping on each one of 7 folders to sync
+ETA: Thu Oct 29 00:50:44 2020  0 s  2/2 msgs left
+Folder     1/7 [INBOX]                             -> [INBOX]                            
+Host1: folder [INBOX] has 1 messages in total (mentioned by SELECT)
+Host2: folder [INBOX] has 0 messages in total (mentioned by SELECT)
+Host2: folder [INBOX] permanentflags: 
+Host1: folder [INBOX] considering 1 messages
+Host2: folder [INBOX] considering 0 messages
+Host1: folder [INBOX] selected 1 messages, duplicates 0
+Host2: folder [INBOX] selected 0 messages, duplicates 0
+msg INBOX/2 {80378}           copied to INBOX/1          2.23 msgs/s  175.199 KiB/s 78.494 KiB copied ETA: Thu Oct 29 00:50:45 2020  0 s  1/2 msgs left
+ETA: Thu Oct 29 00:50:45 2020  0 s  1/2 msgs left
+Folder     2/7 [INBOX.Archive]                     -> [Archive]                          
+Host1: folder [INBOX.Archive] has 0 messages in total (mentioned by SELECT)
+Host1: skipping empty host1 folder [INBOX.Archive]
+ETA: Thu Oct 29 00:50:45 2020  0 s  1/2 msgs left
+Folder     3/7 [INBOX.Drafts]                      -> [Drafts]                           
+Host1: folder [INBOX.Drafts] has 0 messages in total (mentioned by SELECT)
+Host1: skipping empty host1 folder [INBOX.Drafts]
+ETA: Thu Oct 29 00:50:45 2020  1 s  1/2 msgs left
+Folder     4/7 [INBOX.Junk]                        -> [Junk]                             
+Host1: folder [INBOX.Junk] has 0 messages in total (mentioned by SELECT)
+Host1: skipping empty host1 folder [INBOX.Junk]
+ETA: Thu Oct 29 00:50:45 2020  1 s  1/2 msgs left
+Folder     5/7 [INBOX.Sent]                        -> [Sent]                             
+Host1: folder [INBOX.Sent] has 0 messages in total (mentioned by SELECT)
+Host1: skipping empty host1 folder [INBOX.Sent]
+ETA: Thu Oct 29 00:50:45 2020  1 s  1/2 msgs left
+Folder     6/7 [INBOX.Trash]                       -> [Trash]                            
+Host1: folder [INBOX.Trash] has 1 messages in total (mentioned by SELECT)
+Creating folder [Trash] on host2
+Created folder [Trash] on host2
+Host2: folder [Trash] has 0 messages in total (mentioned by SELECT)
+Host2: folder [Trash] permanentflags: 
+Host2: Subscribing to folder Trash
+Host1: folder [INBOX.Trash] considering 1 messages
+Host2: folder [Trash] considering 0 messages
+Host1: folder [INBOX.Trash] selected 1 messages, duplicates 0
+Host2: folder [Trash] selected 0 messages, duplicates 0
+msg INBOX.Trash/1 {1055}            copied to Trash/1          2.02 msgs/s  80.221 KiB/s 79.524 KiB copied ETA: Thu Oct 29 00:50:45 2020  0 s  0/2 msgs left
+ETA: Thu Oct 29 00:50:45 2020  0 s  0/2 msgs left
+Folder     7/7 [INBOX.spam]                        -> [spam]                             
+Host1: folder [INBOX.spam] has 0 messages in total (mentioned by SELECT)
+Host1: skipping empty host1 folder [INBOX.spam]
+ETA: Thu Oct 29 00:50:45 2020  0 s  0/2 msgs left
+++++ End looping on each folder
+
+Folders sizes after the synchronization.
+You can remove this foldersizes listing by using  "--nofoldersizesatend"
+Host1 folder     1/7 [INBOX]                             Size:     80378 Messages:     1 Biggest:     80378
+Host2 folder     1/7 [INBOX]                             Size:     80378 Messages:     1 Biggest:     80378
+Host2-Host1                                                            0               0                  0
+
+Host1 folder     2/7 [INBOX.Archive]                     Size:         0 Messages:     0 Biggest:         0
+Host2 folder     2/7 [Archive]                            does not exist yet
+Host2-Host1                                                            0               0                  0
+
+Host1 folder     3/7 [INBOX.Drafts]                      Size:         0 Messages:     0 Biggest:         0
+Host2 folder     3/7 [Drafts]                             does not exist yet
+Host2-Host1                                                            0               0                  0
+
+Host1 folder     4/7 [INBOX.Junk]                        Size:         0 Messages:     0 Biggest:         0
+Host2 folder     4/7 [Junk]                               does not exist yet
+Host2-Host1                                                            0               0                  0
+
+Host1 folder     5/7 [INBOX.Sent]                        Size:         0 Messages:     0 Biggest:         0
+Host2 folder     5/7 [Sent]                               does not exist yet
+Host2-Host1                                                            0               0                  0
+
+Host1 folder     6/7 [INBOX.Trash]                       Size:      1055 Messages:     1 Biggest:      1055
+Host2 folder     6/7 [Trash]                             Size:      1055 Messages:     1 Biggest:      1055
+Host2-Host1                                                            0               0                  0
+
+Host1 folder     7/7 [INBOX.spam]                        Size:         0 Messages:     0 Biggest:         0
+Host2 folder     7/7 [spam]                               does not exist yet
+Host2-Host1                                                            0               0                  0
+
+Host1 Nb folders:                     7 folders
+Host2 Nb folders:                     7 folders
+
+Host1 Nb messages:                    2 messages
+Host2 Nb messages:                    2 messages
+
+Host1 Total size:                 81433 bytes (79.524 KiB)
+Host2 Total size:                 81433 bytes (79.524 KiB)
+
+Host1 Biggest message:            80378 bytes (78.494 KiB)
+Host2 Biggest message:            80378 bytes (78.494 KiB)
+
+Time spent on sizing:         0.6 seconds
+++++ Statistics
+Transfer started on                     : Thu Oct 29 00:50:42 2020
+Transfer ended on                       : Thu Oct 29 00:50:46 2020
+Transfer time                           : 3.7 sec
+Folders synced                          : 7/7 synced
+Messages transferred                    : 2 
+Messages skipped                        : 0
+Messages found duplicate on host1       : 0
+Messages found duplicate on host2       : 0
+Messages found crossduplicate on host2  : 0
+Messages void (noheader) on host1       : 0  
+Messages void (noheader) on host2       : 0
+Messages found in host1 not in host2    : 0 messages
+Messages found in host2 not in host1    : 0 messages
+Messages deleted on host1               : 0
+Messages deleted on host2               : 0
+Total bytes transferred                 : 81433 (79.524 KiB)
+Total bytes skipped                     : 0 (0.000 KiB)
+Message rate                            : 0.5 messages/s
+Average bandwidth rate                  : 21.6 KiB/s
+Reconnections to host1                  : 0
+Reconnections to host2                  : 0
+Memory consumption at the end           : 165.8 MiB (started with 159.9 MiB)
+Load end is                             : 0.39 0.37 0.45 2/1197 on 2 cores
+Biggest message                         : 80378 bytes (78.494 KiB)
+Memory/biggest message ratio            : 2163.3
+Start difference host2 - host1          : -2 messages, -81433 bytes (-79.524 KiB)
+Final difference host2 - host1          : 0 messages, 0 bytes (0.000 KiB)
+The sync looks good, all 2 identified messages in host1 are on host2.
+There is no unidentified message
+The sync is strict, all 2 identified messages in host2 are on host1.
+Detected 0 errors
+
+Check if a new imapsync release is available by adding --releasecheck
+Homepage: https://imapsync.lamiral.info/
+Exiting with return value 0 (EX_OK: successful termination) 0/20 nb_errors/max_errors
+Log file is LOG_imapsync/2020_10_29_00_50_42_413_forumbb@beobuild.rs_forumbb@beobuild.rs.txt ( to change it, use --logfile filepath ; or use --nolog to turn off logging )

LOG_imapsync/2020_10_29_00_50_55_391_forumbb@beobuild.rs_forumbb@beobuild.rs.txt

@@ -0,0 +1,309 @@
+Here is imapsync 1.977 on host privremena, a linux system with 18.8/31.3 free GiB of RAM
+with Perl 5.28.1 and Mail::IMAPClient 3.42
+Transfer started at Thu Oct 29 00:50:55 2020
+PID is 8134 my PPID is 8133
+Log file is LOG_imapsync/2020_10_29_00_50_55_391_forumbb@beobuild.rs_forumbb@beobuild.rs.txt ( to change it, use --logfile path ; or use --nolog to turn off logging )
+Load is 0.33 0.35 0.45 1/1195 on 2 cores
+Current directory is /root/imapsync-master
+Real user id is root (uid 0)
+Effective user id is root (euid 0)
+$RCSfile: imapsync,v $ $Revision: 1.977 $ $Date: 2019/12/23 20:18:02 $ 
+Command line used, run by /usr/bin/perl:
+./imapsync --addheader --automap --host1 cp8.ulimitserver.com --host2 194.146.57.67 --password1 MASKED --password2 MASKED --user1 forumbb@beobuild.rs --user2 forumbb@beobuild.rs
+Temp directory is . ( to change it use --tmpdir dirpath )
+Under cgi context
+Umask set with 0077 (was 0022)
+REMOTE_ADDR is ::ffff:93.86.60.84
+HTTP_REFERER is http://148.251.112.220:8080/
+HTTP_USER_AGENT is Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Firefox/78.0
+SERVER_SOFTWARE is ./webserver
+SERVER_PORT is 8080
+HTTP_COOKIE is imapsync_runs=5
+kill -QUIT 8134 # special behavior: call to sub catch_exit
+kill -TERM 8134 # special behavior: call to sub catch_exit
+kill -INT 8134 # special behavior: call to sub catch_reconnect
+kill -HUP 8134 # special behavior: call to sub catch_print
+kill -USR1 8134 # special behavior: call to sub toggle_sleep
+File ./imapsync_cp8.ulimitserver.com_forumbb@beobuild.rs_194.146.57.67_forumbb@beobuild.rs.pid does not exist
+Error reading file ./imapsync_cp8.ulimitserver.com_forumbb@beobuild.rs_194.146.57.67_forumbb@beobuild.rs.pid : No such file or directory
+PID file is ./imapsync_cp8.ulimitserver.com_forumbb@beobuild.rs_194.146.57.67_forumbb@beobuild.rs.pid ( to change it, use --pidfile filepath ; to avoid it use --pidfile "" )
+Writing my PID 8134 in ./imapsync_cp8.ulimitserver.com_forumbb@beobuild.rs_194.146.57.67_forumbb@beobuild.rs.pid
+Writing also my logfile name in ./imapsync_cp8.ulimitserver.com_forumbb@beobuild.rs_194.146.57.67_forumbb@beobuild.rs.pid : LOG_imapsync/2020_10_29_00_50_55_391_forumbb@beobuild.rs_forumbb@beobuild.rs.txt
+Info: will resync flags for already transferred messages. Use --noresyncflags to not resync flags.
+Host1: probing ssl on port 993 ( use --nosslcheck to avoid this ssl probe ) 
+Host1: sslcheck detected open ssl port 993 so turning ssl on (use --nossl1 --notls1 to turn off SSL and TLS wizardry)
+Host2: probing ssl on port 993 ( use --nosslcheck to avoid this ssl probe ) 
+Host2: sslcheck detected open ssl port 993 so turning ssl on (use --nossl2 --notls2 to turn off SSL and TLS wizardry)
+SSL debug mode level is --debugssl 1 (can be set from 0 meaning no debug to 4 meaning max debug)
+Host1: SSL default mode is like --sslargs1 "SSL_verify_mode=0", meaning for host1 SSL_VERIFY_NONE, ie, do not check the certificate server.
+Host1: Use --sslargs1 SSL_verify_mode=1 to have SSL_VERIFY_PEER, ie, check the certificate server of host1
+Host2: SSL default mode is like --sslargs2 "SSL_verify_mode=0", meaning for host2 SSL_VERIFY_NONE, ie, do not check the certificate server.
+Host2: Use --sslargs2 SSL_verify_mode=1 to have SSL_VERIFY_PEER, ie, check the certificate server of host2
+Info: turned ON syncinternaldates, will set the internal dates (arrival dates) on host2 same as host1.
+Host1: will try to use LOGIN authentication on host1
+Host2: will try to use LOGIN authentication on host2
+Host1: imap connection timeout is 120 seconds
+Host2: imap connection timeout is 120 seconds
+Host1: IMAP server [cp8.ulimitserver.com] port [993] user [forumbb@beobuild.rs]
+Host2: IMAP server [194.146.57.67] port [993] user [forumbb@beobuild.rs]
+Host1: connecting and login on host1 [cp8.ulimitserver.com] port [993] with user [forumbb@beobuild.rs]
+Host1 IP address: 194.146.59.72
+Host1 banner: * OK [CAPABILITY IMAP4rev1 SASL-IR LOGIN-REFERRALS ID ENABLE IDLE NAMESPACE LITERAL+ AUTH=PLAIN AUTH=LOGIN] Dovecot ready.
+Host1 capability before authentication: IMAP4rev1 SASL-IR LOGIN-REFERRALS ID ENABLE IDLE NAMESPACE LITERAL+ AUTH=PLAIN AUTH=LOGIN AUTH
+Host1: cp8.ulimitserver.com says it has CAPABILITY for AUTHENTICATE LOGIN
+Host1: success login on [cp8.ulimitserver.com] with user [forumbb@beobuild.rs] auth [LOGIN]
+Host2: connecting and login on host2 [194.146.57.67] port [993] with user [forumbb@beobuild.rs]
+Host2 IP address: 194.146.57.67
+Host2 banner: * OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE IDLE AUTH=PLAIN AUTH=LOGIN AUTH=DIGEST-MD5 AUTH=CRAM-MD5] Dovecot (Ubuntu) ready.
+Host2 capability before authentication: IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE IDLE AUTH=PLAIN AUTH=LOGIN AUTH=DIGEST-MD5 AUTH=CRAM-MD5 AUTH
+Host2: 194.146.57.67 says it has CAPABILITY for AUTHENTICATE LOGIN
+Host2: success login on [194.146.57.67] with user [forumbb@beobuild.rs] auth [LOGIN]
+Host1: state Authenticated
+Host2: state Authenticated
+Host1 capability once authenticated: IMAP4rev1 SASL-IR LOGIN-REFERRALS ID ENABLE IDLE SORT SORT=DISPLAY THREAD=REFERENCES THREAD=REFS THREAD=ORDEREDSUBJECT MULTIAPPEND URL-PARTIAL CATENATE UNSELECT CHILDREN NAMESPACE UIDPLUS LIST-EXTENDED I18NLEVEL=1 CONDSTORE QRESYNC ESEARCH ESORT SEARCHRES WITHIN CONTEXT=SEARCH LIST-STATUS BINARY MOVE SNIPPET=FUZZY PREVIEW=FUZZY STATUS=SIZE NAMESPACE LITERAL+ NOTIFY SPECIAL-USE COMPRESS=DEFLATE QUOTA THREAD I18NLEVEL CONTEXT SNIPPET PREVIEW STATUS COMPRESS
+Host2 capability once authenticated: IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE IDLE SORT SORT=DISPLAY THREAD=REFERENCES THREAD=REFS THREAD=ORDEREDSUBJECT MULTIAPPEND URL-PARTIAL CATENATE UNSELECT CHILDREN NAMESPACE UIDPLUS LIST-EXTENDED I18NLEVEL=1 CONDSTORE QRESYNC ESEARCH ESORT SEARCHRES WITHIN CONTEXT=SEARCH LIST-STATUS BINARY MOVE THREAD I18NLEVEL CONTEXT
+
+Host1: found ID capability. Sending/receiving ID, presented in raw IMAP for now.
+In order to avoid sending/receiving ID, use option --noid
+Sending: 4 ID ("name" "imapsync" "version" "1.977" "os" "linux" "vendor" "Gilles LAMIRAL" "support-url" "https://imapsync.lamiral.info/" "date" "23-Dec-2019 20:18:02 +0000" "side" "host1")
+Sent 181 bytes
+Read: 	* ID ("name" "Dovecot")
+  	4 OK ID completed (0.001 + 0.000 secs).
+
+
+Host2: found ID capability. Sending/receiving ID, presented in raw IMAP for now.
+In order to avoid sending/receiving ID, use option --noid
+Sending: 4 ID ("name" "imapsync" "version" "1.977" "os" "linux" "vendor" "Gilles LAMIRAL" "support-url" "https://imapsync.lamiral.info/" "date" "23-Dec-2019 20:18:02 +0000" "side" "host2")
+Sent 181 bytes
+Read: 	* ID ("name" "Dovecot")
+  	4 OK ID completed (0.001 + 0.000 secs).
+
+Host1: found 7 folders.
+Host2: found 2 folders.
+Host1: guessing separator from folder listing: [.]
+Host1: separator given by NAMESPACE: [.]
+Host2: guessing separator from folder listing: [/]
+Host2: separator given by NAMESPACE: [.]
+Host1: guessing prefix from folder listing: [INBOX.]
+Host1: prefix given by NAMESPACE: [INBOX.]
+Host2: guessing prefix from folder listing: []
+Host2: prefix given by NAMESPACE: []
+Host1: separator and prefix: [.][INBOX.]
+Host2: separator and prefix: [.][]
+Including all folders found by default. Use --subscribed or --folder or --folderrec or --include to select specific folders. Use --exclude to unselect specific folders.
+Host1: Checking wanted folders exist. Use --nocheckfoldersexist to avoid this check (shared of public namespace targeted).
+Host1: Checking wanted folders are selectable. Use --nocheckselectable to avoid this check.
+Turned on automapping folders ( use --noautomap to turn off automapping )
+Host1: special INBOX.Archive        = \Archive
+Host1: special INBOX.Sent           = \Sent
+Host1: special INBOX.spam           = \Junk
+Host1: special INBOX.Trash          = \Trash
+Host1: special INBOX.Drafts         = \Drafts
+
+Host2: special Trash                = \Trash
+
+
+++++ Listing folders
+All foldernames are presented between brackets like [X] where X is the foldername.
+When a foldername contains non-ASCII characters it is presented in the form
+[X] = [Y] where
+X is the imap foldername you have to use in command line options and
+Y is the utf8 output just printed for convenience, to recognize it.
+
+Host1: folders list (first the raw imap format then the [X] = [Y]):
+* LIST (\HasChildren) "." INBOX
+* LIST (\HasNoChildren \Archive) "." INBOX.Archive
+* LIST (\HasNoChildren \Sent) "." INBOX.Sent
+* LIST (\HasNoChildren) "." INBOX.Junk
+* LIST (\HasNoChildren \Junk) "." INBOX.spam
+* LIST (\HasNoChildren \Trash) "." INBOX.Trash
+* LIST (\HasNoChildren \Drafts) "." INBOX.Drafts
+17 OK List completed (0.001 + 0.000 secs).
+
+[INBOX]
+[INBOX.Archive]
+[INBOX.Drafts]
+[INBOX.Junk]
+[INBOX.Sent]
+[INBOX.Trash]
+[INBOX.spam]
+
+Host2: folders list (first the raw imap format then the [X] = [Y]):
+* LIST (\HasNoChildren \Trash) "." Trash
+* LIST (\HasNoChildren) "." INBOX
+10 OK List completed (0.001 + 0.000 secs).
+
+[INBOX]
+[Trash]
+
+Folders mapping from --automap feature (use --f1f2 to override any mapping):
+[INBOX.Trash]                            -> [Trash]                                 
+
+Host1: will not syncing empty folders on host1. Use --noskipemptyfolders to create them anyway on host2
+
+Folders sizes before the synchronization.
+You can remove foldersizes listings by using "--nofoldersizes" and "--nofoldersizesatend"
+but then you will also lose the ETA (Estimation Time of Arrival) given after each message copy.
+Host1 folder     1/7 [INBOX]                             Size:     80378 Messages:     1 Biggest:     80378
+Host2 folder     1/7 [INBOX]                             Size:     80378 Messages:     1 Biggest:     80378
+Host2-Host1                                                            0               0                  0
+
+Host1 folder     2/7 [INBOX.Archive]                     Size:         0 Messages:     0 Biggest:         0
+Host2 folder     2/7 [Archive]                            does not exist yet
+Host2-Host1                                                            0               0                  0
+
+Host1 folder     3/7 [INBOX.Drafts]                      Size:         0 Messages:     0 Biggest:         0
+Host2 folder     3/7 [Drafts]                             does not exist yet
+Host2-Host1                                                            0               0                  0
+
+Host1 folder     4/7 [INBOX.Junk]                        Size:         0 Messages:     0 Biggest:         0
+Host2 folder     4/7 [Junk]                               does not exist yet
+Host2-Host1                                                            0               0                  0
+
+Host1 folder     5/7 [INBOX.Sent]                        Size:         0 Messages:     0 Biggest:         0
+Host2 folder     5/7 [Sent]                               does not exist yet
+Host2-Host1                                                            0               0                  0
+
+Host1 folder     6/7 [INBOX.Trash]                       Size:      1055 Messages:     1 Biggest:      1055
+Host2 folder     6/7 [Trash]                             Size:      1055 Messages:     1 Biggest:      1055
+Host2-Host1                                                            0               0                  0
+
+Host1 folder     7/7 [INBOX.spam]                        Size:         0 Messages:     0 Biggest:         0
+Host2 folder     7/7 [spam]                               does not exist yet
+Host2-Host1                                                            0               0                  0
+
+Host1 Nb folders:                     7 folders
+Host2 Nb folders:                     7 folders
+
+Host1 Nb messages:                    2 messages
+Host2 Nb messages:                    2 messages
+
+Host1 Total size:                 81433 bytes (79.524 KiB)
+Host2 Total size:                 81433 bytes (79.524 KiB)
+
+Host1 Biggest message:            80378 bytes (78.494 KiB)
+Host2 Biggest message:            80378 bytes (78.494 KiB)
+
+Time spent on sizing:         2.0 seconds
+++++ Looping on each one of 7 folders to sync
+ETA: Thu Oct 29 00:50:57 2020  0 s  2/2 msgs left
+Folder     1/7 [INBOX]                             -> [INBOX]                            
+Host1: folder [INBOX] has 1 messages in total (mentioned by SELECT)
+Host2: folder [INBOX] has 1 messages in total (mentioned by SELECT)
+Host2: folder [INBOX] permanentflags: 
+Host1: folder [INBOX] considering 1 messages
+Host2: folder [INBOX] considering 1 messages
+Host1: folder [INBOX] selected 1 messages, duplicates 0
+Host2: folder [INBOX] selected 1 messages, duplicates 0
+ETA: Thu Oct 29 00:50:57 2020  0 s  1/2 msgs left
+Folder     2/7 [INBOX.Archive]                     -> [Archive]                          
+Host1: folder [INBOX.Archive] has 0 messages in total (mentioned by SELECT)
+Host1: skipping empty host1 folder [INBOX.Archive]
+ETA: Thu Oct 29 00:50:57 2020  0 s  1/2 msgs left
+Folder     3/7 [INBOX.Drafts]                      -> [Drafts]                           
+Host1: folder [INBOX.Drafts] has 0 messages in total (mentioned by SELECT)
+Host1: skipping empty host1 folder [INBOX.Drafts]
+ETA: Thu Oct 29 00:50:58 2020  0 s  1/2 msgs left
+Folder     4/7 [INBOX.Junk]                        -> [Junk]                             
+Host1: folder [INBOX.Junk] has 0 messages in total (mentioned by SELECT)
+Host1: skipping empty host1 folder [INBOX.Junk]
+ETA: Thu Oct 29 00:50:58 2020  0 s  1/2 msgs left
+Folder     5/7 [INBOX.Sent]                        -> [Sent]                             
+Host1: folder [INBOX.Sent] has 0 messages in total (mentioned by SELECT)
+Host1: skipping empty host1 folder [INBOX.Sent]
+ETA: Thu Oct 29 00:50:58 2020  0 s  1/2 msgs left
+Folder     6/7 [INBOX.Trash]                       -> [Trash]                            
+Host1: folder [INBOX.Trash] has 1 messages in total (mentioned by SELECT)
+Host2: folder [Trash] has 1 messages in total (mentioned by SELECT)
+Host2: folder [Trash] permanentflags: 
+Host1: folder [INBOX.Trash] considering 1 messages
+Host2: folder [Trash] considering 1 messages
+Host1: folder [INBOX.Trash] selected 1 messages, duplicates 0
+Host2: folder [Trash] selected 1 messages, duplicates 0
+ETA: Thu Oct 29 00:50:58 2020  0 s  0/2 msgs left
+Folder     7/7 [INBOX.spam]                        -> [spam]                             
+Host1: folder [INBOX.spam] has 0 messages in total (mentioned by SELECT)
+Host1: skipping empty host1 folder [INBOX.spam]
+ETA: Thu Oct 29 00:50:58 2020  0 s  0/2 msgs left
+++++ End looping on each folder
+
+Folders sizes after the synchronization.
+You can remove this foldersizes listing by using  "--nofoldersizesatend"
+Host1 folder     1/7 [INBOX]                             Size:     80378 Messages:     1 Biggest:     80378
+Host2 folder     1/7 [INBOX]                             Size:     80378 Messages:     1 Biggest:     80378
+Host2-Host1                                                            0               0                  0
+
+Host1 folder     2/7 [INBOX.Archive]                     Size:         0 Messages:     0 Biggest:         0
+Host2 folder     2/7 [Archive]                            does not exist yet
+Host2-Host1                                                            0               0                  0
+
+Host1 folder     3/7 [INBOX.Drafts]                      Size:         0 Messages:     0 Biggest:         0
+Host2 folder     3/7 [Drafts]                             does not exist yet
+Host2-Host1                                                            0               0                  0
+
+Host1 folder     4/7 [INBOX.Junk]                        Size:         0 Messages:     0 Biggest:         0
+Host2 folder     4/7 [Junk]                               does not exist yet
+Host2-Host1                                                            0               0                  0
+
+Host1 folder     5/7 [INBOX.Sent]                        Size:         0 Messages:     0 Biggest:         0
+Host2 folder     5/7 [Sent]                               does not exist yet
+Host2-Host1                                                            0               0                  0
+
+Host1 folder     6/7 [INBOX.Trash]                       Size:      1055 Messages:     1 Biggest:      1055
+Host2 folder     6/7 [Trash]                             Size:      1055 Messages:     1 Biggest:      1055
+Host2-Host1                                                            0               0                  0
+
+Host1 folder     7/7 [INBOX.spam]                        Size:         0 Messages:     0 Biggest:         0
+Host2 folder     7/7 [spam]                               does not exist yet
+Host2-Host1                                                            0               0                  0
+
+Host1 Nb folders:                     7 folders
+Host2 Nb folders:                     7 folders
+
+Host1 Nb messages:                    2 messages
+Host2 Nb messages:                    2 messages
+
+Host1 Total size:                 81433 bytes (79.524 KiB)
+Host2 Total size:                 81433 bytes (79.524 KiB)
+
+Host1 Biggest message:            80378 bytes (78.494 KiB)
+Host2 Biggest message:            80378 bytes (78.494 KiB)
+
+Time spent on sizing:         0.6 seconds
+++++ Statistics
+Transfer started on                     : Thu Oct 29 00:50:55 2020
+Transfer ended on                       : Thu Oct 29 00:50:58 2020
+Transfer time                           : 3.4 sec
+Folders synced                          : 7/7 synced
+Messages transferred                    : 0 
+Messages skipped                        : 2
+Messages found duplicate on host1       : 0
+Messages found duplicate on host2       : 0
+Messages found crossduplicate on host2  : 0
+Messages void (noheader) on host1       : 0  
+Messages void (noheader) on host2       : 0
+Messages found in host1 not in host2    : 0 messages
+Messages found in host2 not in host1    : 0 messages
+Messages deleted on host1               : 0
+Messages deleted on host2               : 0
+Total bytes transferred                 : 0 (0.000 KiB)
+Total bytes skipped                     : 81433 (79.524 KiB)
+Message rate                            : 0.0 messages/s
+Average bandwidth rate                  : 0.0 KiB/s
+Reconnections to host1                  : 0
+Reconnections to host2                  : 0
+Memory consumption at the end           : 165.2 MiB (started with 159.9 MiB)
+Load end is                             : 0.33 0.35 0.45 1/1199 on 2 cores
+Biggest message                         : 0 bytes (0.000 KiB)
+Memory/biggest message ratio            : NA
+Start difference host2 - host1          : 0 messages, 0 bytes (0.000 KiB)
+Final difference host2 - host1          : 0 messages, 0 bytes (0.000 KiB)
+The sync looks good, all 2 identified messages in host1 are on host2.
+There is no unidentified message
+The sync is strict, all 2 identified messages in host2 are on host1.
+Detected 0 errors
+
+Check if a new imapsync release is available by adding --releasecheck
+Homepage: https://imapsync.lamiral.info/
+Exiting with return value 0 (EX_OK: successful termination) 0/20 nb_errors/max_errors
+Log file is LOG_imapsync/2020_10_29_00_50_55_391_forumbb@beobuild.rs_forumbb@beobuild.rs.txt ( to change it, use --logfile filepath ; or use --nolog to turn off logging )

LOG_imapsync/2020_10_29_00_51_11_433_forumsend@beobuild.rs_forumsend@beobuild.rs.txt

@@ -0,0 +1,298 @@
+Here is imapsync 1.977 on host privremena, a linux system with 18.8/31.3 free GiB of RAM
+with Perl 5.28.1 and Mail::IMAPClient 3.42
+Transfer started at Thu Oct 29 00:51:11 2020
+PID is 8143 my PPID is 8142
+Log file is LOG_imapsync/2020_10_29_00_51_11_433_forumsend@beobuild.rs_forumsend@beobuild.rs.txt ( to change it, use --logfile path ; or use --nolog to turn off logging )
+Load is 0.26 0.34 0.44 1/1200 on 2 cores
+Current directory is /root/imapsync-master
+Real user id is root (uid 0)
+Effective user id is root (euid 0)
+$RCSfile: imapsync,v $ $Revision: 1.977 $ $Date: 2019/12/23 20:18:02 $ 
+Command line used, run by /usr/bin/perl:
+./imapsync --addheader --automap --host1 cp8.ulimitserver.com --host2 194.146.57.67 --password1 MASKED --password2 MASKED --user1 forumsend@beobuild.rs --user2 forumsend@beobuild.rs
+Temp directory is . ( to change it use --tmpdir dirpath )
+Under cgi context
+Umask set with 0077 (was 0022)
+REMOTE_ADDR is ::ffff:93.86.60.84
+HTTP_REFERER is http://148.251.112.220:8080/
+HTTP_USER_AGENT is Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Firefox/78.0
+SERVER_SOFTWARE is ./webserver
+SERVER_PORT is 8080
+HTTP_COOKIE is imapsync_runs=6
+kill -QUIT 8143 # special behavior: call to sub catch_exit
+kill -TERM 8143 # special behavior: call to sub catch_exit
+kill -INT 8143 # special behavior: call to sub catch_reconnect
+kill -HUP 8143 # special behavior: call to sub catch_print
+kill -USR1 8143 # special behavior: call to sub toggle_sleep
+File ./imapsync_cp8.ulimitserver.com_forumsend@beobuild.rs_194.146.57.67_forumsend@beobuild.rs.pid does not exist
+Error reading file ./imapsync_cp8.ulimitserver.com_forumsend@beobuild.rs_194.146.57.67_forumsend@beobuild.rs.pid : No such file or directory
+PID file is ./imapsync_cp8.ulimitserver.com_forumsend@beobuild.rs_194.146.57.67_forumsend@beobuild.rs.pid ( to change it, use --pidfile filepath ; to avoid it use --pidfile "" )
+Writing my PID 8143 in ./imapsync_cp8.ulimitserver.com_forumsend@beobuild.rs_194.146.57.67_forumsend@beobuild.rs.pid
+Writing also my logfile name in ./imapsync_cp8.ulimitserver.com_forumsend@beobuild.rs_194.146.57.67_forumsend@beobuild.rs.pid : LOG_imapsync/2020_10_29_00_51_11_433_forumsend@beobuild.rs_forumsend@beobuild.rs.txt
+Info: will resync flags for already transferred messages. Use --noresyncflags to not resync flags.
+Host1: probing ssl on port 993 ( use --nosslcheck to avoid this ssl probe ) 
+Host1: sslcheck detected open ssl port 993 so turning ssl on (use --nossl1 --notls1 to turn off SSL and TLS wizardry)
+Host2: probing ssl on port 993 ( use --nosslcheck to avoid this ssl probe ) 
+Host2: sslcheck detected open ssl port 993 so turning ssl on (use --nossl2 --notls2 to turn off SSL and TLS wizardry)
+SSL debug mode level is --debugssl 1 (can be set from 0 meaning no debug to 4 meaning max debug)
+Host1: SSL default mode is like --sslargs1 "SSL_verify_mode=0", meaning for host1 SSL_VERIFY_NONE, ie, do not check the certificate server.
+Host1: Use --sslargs1 SSL_verify_mode=1 to have SSL_VERIFY_PEER, ie, check the certificate server of host1
+Host2: SSL default mode is like --sslargs2 "SSL_verify_mode=0", meaning for host2 SSL_VERIFY_NONE, ie, do not check the certificate server.
+Host2: Use --sslargs2 SSL_verify_mode=1 to have SSL_VERIFY_PEER, ie, check the certificate server of host2
+Info: turned ON syncinternaldates, will set the internal dates (arrival dates) on host2 same as host1.
+Host1: will try to use LOGIN authentication on host1
+Host2: will try to use LOGIN authentication on host2
+Host1: imap connection timeout is 120 seconds
+Host2: imap connection timeout is 120 seconds
+Host1: IMAP server [cp8.ulimitserver.com] port [993] user [forumsend@beobuild.rs]
+Host2: IMAP server [194.146.57.67] port [993] user [forumsend@beobuild.rs]
+Host1: connecting and login on host1 [cp8.ulimitserver.com] port [993] with user [forumsend@beobuild.rs]
+Host1 IP address: 194.146.59.72
+Host1 banner: * OK [CAPABILITY IMAP4rev1 SASL-IR LOGIN-REFERRALS ID ENABLE IDLE NAMESPACE LITERAL+ AUTH=PLAIN AUTH=LOGIN] Dovecot ready.
+Host1 capability before authentication: IMAP4rev1 SASL-IR LOGIN-REFERRALS ID ENABLE IDLE NAMESPACE LITERAL+ AUTH=PLAIN AUTH=LOGIN AUTH
+Host1: cp8.ulimitserver.com says it has CAPABILITY for AUTHENTICATE LOGIN
+Host1: success login on [cp8.ulimitserver.com] with user [forumsend@beobuild.rs] auth [LOGIN]
+Host2: connecting and login on host2 [194.146.57.67] port [993] with user [forumsend@beobuild.rs]
+Host2 IP address: 194.146.57.67
+Host2 banner: * OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE IDLE AUTH=PLAIN AUTH=LOGIN AUTH=DIGEST-MD5 AUTH=CRAM-MD5] Dovecot (Ubuntu) ready.
+Host2 capability before authentication: IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE IDLE AUTH=PLAIN AUTH=LOGIN AUTH=DIGEST-MD5 AUTH=CRAM-MD5 AUTH
+Host2: 194.146.57.67 says it has CAPABILITY for AUTHENTICATE LOGIN
+Host2: success login on [194.146.57.67] with user [forumsend@beobuild.rs] auth [LOGIN]
+Host1: state Authenticated
+Host2: state Authenticated
+Host1 capability once authenticated: IMAP4rev1 SASL-IR LOGIN-REFERRALS ID ENABLE IDLE SORT SORT=DISPLAY THREAD=REFERENCES THREAD=REFS THREAD=ORDEREDSUBJECT MULTIAPPEND URL-PARTIAL CATENATE UNSELECT CHILDREN NAMESPACE UIDPLUS LIST-EXTENDED I18NLEVEL=1 CONDSTORE QRESYNC ESEARCH ESORT SEARCHRES WITHIN CONTEXT=SEARCH LIST-STATUS BINARY MOVE SNIPPET=FUZZY PREVIEW=FUZZY STATUS=SIZE NAMESPACE LITERAL+ NOTIFY SPECIAL-USE COMPRESS=DEFLATE QUOTA THREAD I18NLEVEL CONTEXT SNIPPET PREVIEW STATUS COMPRESS
+Host2 capability once authenticated: IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE IDLE SORT SORT=DISPLAY THREAD=REFERENCES THREAD=REFS THREAD=ORDEREDSUBJECT MULTIAPPEND URL-PARTIAL CATENATE UNSELECT CHILDREN NAMESPACE UIDPLUS LIST-EXTENDED I18NLEVEL=1 CONDSTORE QRESYNC ESEARCH ESORT SEARCHRES WITHIN CONTEXT=SEARCH LIST-STATUS BINARY MOVE THREAD I18NLEVEL CONTEXT
+
+Host1: found ID capability. Sending/receiving ID, presented in raw IMAP for now.
+In order to avoid sending/receiving ID, use option --noid
+Sending: 4 ID ("name" "imapsync" "version" "1.977" "os" "linux" "vendor" "Gilles LAMIRAL" "support-url" "https://imapsync.lamiral.info/" "date" "23-Dec-2019 20:18:02 +0000" "side" "host1")
+Sent 181 bytes
+Read: 	* ID ("name" "Dovecot")
+  	4 OK ID completed (0.001 + 0.000 secs).
+
+
+Host2: found ID capability. Sending/receiving ID, presented in raw IMAP for now.
+In order to avoid sending/receiving ID, use option --noid
+Sending: 4 ID ("name" "imapsync" "version" "1.977" "os" "linux" "vendor" "Gilles LAMIRAL" "support-url" "https://imapsync.lamiral.info/" "date" "23-Dec-2019 20:18:02 +0000" "side" "host2")
+Sent 181 bytes
+Read: 	* ID ("name" "Dovecot")
+  	4 OK ID completed (0.001 + 0.000 secs).
+
+Host1: found 7 folders.
+Host2: found 1 folders.
+Host1: guessing separator from folder listing: [.]
+Host1: separator given by NAMESPACE: [.]
+Host2: guessing separator from folder listing: [/]
+Host2: separator given by NAMESPACE: [.]
+Host1: guessing prefix from folder listing: [INBOX.]
+Host1: prefix given by NAMESPACE: [INBOX.]
+Host2: guessing prefix from folder listing: []
+Host2: prefix given by NAMESPACE: []
+Host1: separator and prefix: [.][INBOX.]
+Host2: separator and prefix: [.][]
+Including all folders found by default. Use --subscribed or --folder or --folderrec or --include to select specific folders. Use --exclude to unselect specific folders.
+Host1: Checking wanted folders exist. Use --nocheckfoldersexist to avoid this check (shared of public namespace targeted).
+Host1: Checking wanted folders are selectable. Use --nocheckselectable to avoid this check.
+Turned on automapping folders ( use --noautomap to turn off automapping )
+Host1: special INBOX.Sent           = \Sent
+Host1: special INBOX.spam           = \Junk
+Host1: special INBOX.Trash          = \Trash
+Host1: special INBOX.Drafts         = \Drafts
+Host1: special INBOX.Archive        = \Archive
+
+
+++++ Listing folders
+All foldernames are presented between brackets like [X] where X is the foldername.
+When a foldername contains non-ASCII characters it is presented in the form
+[X] = [Y] where
+X is the imap foldername you have to use in command line options and
+Y is the utf8 output just printed for convenience, to recognize it.
+
+Host1: folders list (first the raw imap format then the [X] = [Y]):
+* LIST (\HasChildren) "." INBOX
+* LIST (\HasNoChildren \Sent) "." INBOX.Sent
+* LIST (\HasNoChildren) "." INBOX.Junk
+* LIST (\HasNoChildren \Junk) "." INBOX.spam
+* LIST (\HasNoChildren \Trash) "." INBOX.Trash
+* LIST (\HasNoChildren \Drafts) "." INBOX.Drafts
+* LIST (\HasNoChildren \Archive) "." INBOX.Archive
+17 OK List completed (0.001 + 0.000 secs).
+
+[INBOX]
+[INBOX.Archive]
+[INBOX.Drafts]
+[INBOX.Junk]
+[INBOX.Sent]
+[INBOX.Trash]
+[INBOX.spam]
+
+Host2: folders list (first the raw imap format then the [X] = [Y]):
+* LIST (\HasNoChildren) "." INBOX
+10 OK List completed (0.001 + 0.000 secs).
+
+[INBOX]
+
+Host1: will not syncing empty folders on host1. Use --noskipemptyfolders to create them anyway on host2
+
+Folders sizes before the synchronization.
+You can remove foldersizes listings by using "--nofoldersizes" and "--nofoldersizesatend"
+but then you will also lose the ETA (Estimation Time of Arrival) given after each message copy.
+Host1 folder     1/7 [INBOX]                             Size:     80526 Messages:     1 Biggest:     80526
+Host2 folder     1/7 [INBOX]                             Size:         0 Messages:     0 Biggest:         0
+Host2-Host1                                                       -80526              -1             -80526
+
+Host1 folder     2/7 [INBOX.Archive]                     Size:         0 Messages:     0 Biggest:         0
+Host2 folder     2/7 [Archive]                            does not exist yet
+Host2-Host1                                                            0               0                  0
+
+Host1 folder     3/7 [INBOX.Drafts]                      Size:         0 Messages:     0 Biggest:         0
+Host2 folder     3/7 [Drafts]                             does not exist yet
+Host2-Host1                                                            0               0                  0
+
+Host1 folder     4/7 [INBOX.Junk]                        Size:         0 Messages:     0 Biggest:         0
+Host2 folder     4/7 [Junk]                               does not exist yet
+Host2-Host1                                                            0               0                  0
+
+Host1 folder     5/7 [INBOX.Sent]                        Size:         0 Messages:     0 Biggest:         0
+Host2 folder     5/7 [Sent]                               does not exist yet
+Host2-Host1                                                            0               0                  0
+
+Host1 folder     6/7 [INBOX.Trash]                       Size:         0 Messages:     0 Biggest:         0
+Host2 folder     6/7 [Trash]                              does not exist yet
+Host2-Host1                                                            0               0                  0
+
+Host1 folder     7/7 [INBOX.spam]                        Size:         0 Messages:     0 Biggest:         0
+Host2 folder     7/7 [spam]                               does not exist yet
+Host2-Host1                                                            0               0                  0
+
+Host1 Nb folders:                     7 folders
+Host2 Nb folders:                     7 folders
+
+Host1 Nb messages:                    1 messages
+Host2 Nb messages:                    0 messages
+
+Host1 Total size:                 80526 bytes (78.639 KiB)
+Host2 Total size:                     0 bytes (0.000 KiB)
+
+Host1 Biggest message:            80526 bytes (78.639 KiB)
+Host2 Biggest message:                0 bytes (0.000 KiB)
+
+Time spent on sizing:         1.9 seconds
+++++ Looping on each one of 7 folders to sync
+ETA: Thu Oct 29 00:51:13 2020  0 s  1/1 msgs left
+Folder     1/7 [INBOX]                             -> [INBOX]                            
+Host1: folder [INBOX] has 1 messages in total (mentioned by SELECT)
+Host2: folder [INBOX] has 0 messages in total (mentioned by SELECT)
+Host2: folder [INBOX] permanentflags: 
+Host1: folder [INBOX] considering 1 messages
+Host2: folder [INBOX] considering 0 messages
+Host1: folder [INBOX] selected 1 messages, duplicates 0
+Host2: folder [INBOX] selected 0 messages, duplicates 0
+msg INBOX/1 {80526}           copied to INBOX/1          2.22 msgs/s  174.940 KiB/s 78.639 KiB copied ETA: Thu Oct 29 00:51:13 2020  0 s  0/1 msgs left
+ETA: Thu Oct 29 00:51:13 2020  0 s  0/1 msgs left
+Folder     2/7 [INBOX.Archive]                     -> [Archive]                          
+Host1: folder [INBOX.Archive] has 0 messages in total (mentioned by SELECT)
+Host1: skipping empty host1 folder [INBOX.Archive]
+ETA: Thu Oct 29 00:51:13 2020  0 s  0/1 msgs left
+Folder     3/7 [INBOX.Drafts]                      -> [Drafts]                           
+Host1: folder [INBOX.Drafts] has 0 messages in total (mentioned by SELECT)
+Host1: skipping empty host1 folder [INBOX.Drafts]
+ETA: Thu Oct 29 00:51:13 2020  0 s  0/1 msgs left
+Folder     4/7 [INBOX.Junk]                        -> [Junk]                             
+Host1: folder [INBOX.Junk] has 0 messages in total (mentioned by SELECT)
+Host1: skipping empty host1 folder [INBOX.Junk]
+ETA: Thu Oct 29 00:51:13 2020  0 s  0/1 msgs left
+Folder     5/7 [INBOX.Sent]                        -> [Sent]                             
+Host1: folder [INBOX.Sent] has 0 messages in total (mentioned by SELECT)
+Host1: skipping empty host1 folder [INBOX.Sent]
+ETA: Thu Oct 29 00:51:13 2020  0 s  0/1 msgs left
+Folder     6/7 [INBOX.Trash]                       -> [Trash]                            
+Host1: folder [INBOX.Trash] has 0 messages in total (mentioned by SELECT)
+Host1: skipping empty host1 folder [INBOX.Trash]
+ETA: Thu Oct 29 00:51:13 2020  0 s  0/1 msgs left
+Folder     7/7 [INBOX.spam]                        -> [spam]                             
+Host1: folder [INBOX.spam] has 0 messages in total (mentioned by SELECT)
+Host1: skipping empty host1 folder [INBOX.spam]
+ETA: Thu Oct 29 00:51:13 2020  0 s  0/1 msgs left
+++++ End looping on each folder
+
+Folders sizes after the synchronization.
+You can remove this foldersizes listing by using  "--nofoldersizesatend"
+Host1 folder     1/7 [INBOX]                             Size:     80526 Messages:     1 Biggest:     80526
+Host2 folder     1/7 [INBOX]                             Size:     80526 Messages:     1 Biggest:     80526
+Host2-Host1                                                            0               0                  0
+
+Host1 folder     2/7 [INBOX.Archive]                     Size:         0 Messages:     0 Biggest:         0
+Host2 folder     2/7 [Archive]                            does not exist yet
+Host2-Host1                                                            0               0                  0
+
+Host1 folder     3/7 [INBOX.Drafts]                      Size:         0 Messages:     0 Biggest:         0
+Host2 folder     3/7 [Drafts]                             does not exist yet
+Host2-Host1                                                            0               0                  0
+
+Host1 folder     4/7 [INBOX.Junk]                        Size:         0 Messages:     0 Biggest:         0
+Host2 folder     4/7 [Junk]                               does not exist yet
+Host2-Host1                                                            0               0                  0
+
+Host1 folder     5/7 [INBOX.Sent]                        Size:         0 Messages:     0 Biggest:         0
+Host2 folder     5/7 [Sent]                               does not exist yet
+Host2-Host1                                                            0               0                  0
+
+Host1 folder     6/7 [INBOX.Trash]                       Size:         0 Messages:     0 Biggest:         0
+Host2 folder     6/7 [Trash]                              does not exist yet
+Host2-Host1                                                            0               0                  0
+
+Host1 folder     7/7 [INBOX.spam]                        Size:         0 Messages:     0 Biggest:         0
+Host2 folder     7/7 [spam]                               does not exist yet
+Host2-Host1                                                            0               0                  0
+
+Host1 Nb folders:                     7 folders
+Host2 Nb folders:                     7 folders
+
+Host1 Nb messages:                    1 messages
+Host2 Nb messages:                    1 messages
+
+Host1 Total size:                 80526 bytes (78.639 KiB)
+Host2 Total size:                 80526 bytes (78.639 KiB)
+
+Host1 Biggest message:            80526 bytes (78.639 KiB)
+Host2 Biggest message:            80526 bytes (78.639 KiB)
+
+Time spent on sizing:         0.5 seconds
+++++ Statistics
+Transfer started on                     : Thu Oct 29 00:51:11 2020
+Transfer ended on                       : Thu Oct 29 00:51:14 2020
+Transfer time                           : 3.1 sec
+Folders synced                          : 7/7 synced
+Messages transferred                    : 1 
+Messages skipped                        : 0
+Messages found duplicate on host1       : 0
+Messages found duplicate on host2       : 0
+Messages found crossduplicate on host2  : 0
+Messages void (noheader) on host1       : 0  
+Messages void (noheader) on host2       : 0
+Messages found in host1 not in host2    : 0 messages
+Messages found in host2 not in host1    : 0 messages
+Messages deleted on host1               : 0
+Messages deleted on host2               : 0
+Total bytes transferred                 : 80526 (78.639 KiB)
+Total bytes skipped                     : 0 (0.000 KiB)
+Message rate                            : 0.3 messages/s
+Average bandwidth rate                  : 25.1 KiB/s
+Reconnections to host1                  : 0
+Reconnections to host2                  : 0
+Memory consumption at the end           : 165.7 MiB (started with 159.9 MiB)
+Load end is                             : 0.26 0.34 0.44 3/1217 on 2 cores
+Biggest message                         : 80526 bytes (78.639 KiB)
+Memory/biggest message ratio            : 2158.1
+Start difference host2 - host1          : -1 messages, -80526 bytes (-78.639 KiB)
+Final difference host2 - host1          : 0 messages, 0 bytes (0.000 KiB)
+The sync looks good, all 1 identified messages in host1 are on host2.
+There is no unidentified message
+The sync is strict, all 1 identified messages in host2 are on host1.
+Detected 0 errors
+
+Check if a new imapsync release is available by adding --releasecheck
+Homepage: https://imapsync.lamiral.info/
+Exiting with return value 0 (EX_OK: successful termination) 0/20 nb_errors/max_errors
+Log file is LOG_imapsync/2020_10_29_00_51_11_433_forumsend@beobuild.rs_forumsend@beobuild.rs.txt ( to change it, use --logfile filepath ; or use --nolog to turn off logging )

LOG_imapsync/2020_10_29_00_51_48_438_postmaster@beobuild.rs_postmaster@beobuild.rs.txt

@@ -0,0 +1,301 @@
+Here is imapsync 1.977 on host privremena, a linux system with 18.8/31.3 free GiB of RAM
+with Perl 5.28.1 and Mail::IMAPClient 3.42
+Transfer started at Thu Oct 29 00:51:48 2020
+PID is 8197 my PPID is 8196
+Log file is LOG_imapsync/2020_10_29_00_51_48_438_postmaster@beobuild.rs_postmaster@beobuild.rs.txt ( to change it, use --logfile path ; or use --nolog to turn off logging )
+Load is 0.14 0.30 0.42 8/1199 on 2 cores
+Current directory is /root/imapsync-master
+Real user id is root (uid 0)
+Effective user id is root (euid 0)
+$RCSfile: imapsync,v $ $Revision: 1.977 $ $Date: 2019/12/23 20:18:02 $ 
+Command line used, run by /usr/bin/perl:
+./imapsync --addheader --automap --host1 cp8.ulimitserver.com --host2 194.146.57.67 --password1 MASKED --password2 MASKED --user1 postmaster@beobuild.rs --user2 postmaster@beobuild.rs
+Temp directory is . ( to change it use --tmpdir dirpath )
+Under cgi context
+Umask set with 0077 (was 0022)
+REMOTE_ADDR is ::ffff:93.86.60.84
+HTTP_REFERER is http://148.251.112.220:8080/
+HTTP_USER_AGENT is Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Firefox/78.0
+SERVER_SOFTWARE is ./webserver
+SERVER_PORT is 8080
+HTTP_COOKIE is imapsync_runs=7
+kill -QUIT 8197 # special behavior: call to sub catch_exit
+kill -TERM 8197 # special behavior: call to sub catch_exit
+kill -INT 8197 # special behavior: call to sub catch_reconnect
+kill -HUP 8197 # special behavior: call to sub catch_print
+kill -USR1 8197 # special behavior: call to sub toggle_sleep
+File ./imapsync_cp8.ulimitserver.com_postmaster@beobuild.rs_194.146.57.67_postmaster@beobuild.rs.pid does not exist
+Error reading file ./imapsync_cp8.ulimitserver.com_postmaster@beobuild.rs_194.146.57.67_postmaster@beobuild.rs.pid : No such file or directory
+PID file is ./imapsync_cp8.ulimitserver.com_postmaster@beobuild.rs_194.146.57.67_postmaster@beobuild.rs.pid ( to change it, use --pidfile filepath ; to avoid it use --pidfile "" )
+Writing my PID 8197 in ./imapsync_cp8.ulimitserver.com_postmaster@beobuild.rs_194.146.57.67_postmaster@beobuild.rs.pid
+Writing also my logfile name in ./imapsync_cp8.ulimitserver.com_postmaster@beobuild.rs_194.146.57.67_postmaster@beobuild.rs.pid : LOG_imapsync/2020_10_29_00_51_48_438_postmaster@beobuild.rs_postmaster@beobuild.rs.txt
+Info: will resync flags for already transferred messages. Use --noresyncflags to not resync flags.
+Host1: probing ssl on port 993 ( use --nosslcheck to avoid this ssl probe ) 
+Host1: sslcheck detected open ssl port 993 so turning ssl on (use --nossl1 --notls1 to turn off SSL and TLS wizardry)
+Host2: probing ssl on port 993 ( use --nosslcheck to avoid this ssl probe ) 
+Host2: sslcheck detected open ssl port 993 so turning ssl on (use --nossl2 --notls2 to turn off SSL and TLS wizardry)
+SSL debug mode level is --debugssl 1 (can be set from 0 meaning no debug to 4 meaning max debug)
+Host1: SSL default mode is like --sslargs1 "SSL_verify_mode=0", meaning for host1 SSL_VERIFY_NONE, ie, do not check the certificate server.
+Host1: Use --sslargs1 SSL_verify_mode=1 to have SSL_VERIFY_PEER, ie, check the certificate server of host1
+Host2: SSL default mode is like --sslargs2 "SSL_verify_mode=0", meaning for host2 SSL_VERIFY_NONE, ie, do not check the certificate server.
+Host2: Use --sslargs2 SSL_verify_mode=1 to have SSL_VERIFY_PEER, ie, check the certificate server of host2
+Info: turned ON syncinternaldates, will set the internal dates (arrival dates) on host2 same as host1.
+Host1: will try to use LOGIN authentication on host1
+Host2: will try to use LOGIN authentication on host2
+Host1: imap connection timeout is 120 seconds
+Host2: imap connection timeout is 120 seconds
+Host1: IMAP server [cp8.ulimitserver.com] port [993] user [postmaster@beobuild.rs]
+Host2: IMAP server [194.146.57.67] port [993] user [postmaster@beobuild.rs]
+Host1: connecting and login on host1 [cp8.ulimitserver.com] port [993] with user [postmaster@beobuild.rs]
+Host1 IP address: 194.146.59.72
+Host1 banner: * OK [CAPABILITY IMAP4rev1 SASL-IR LOGIN-REFERRALS ID ENABLE IDLE NAMESPACE LITERAL+ AUTH=PLAIN AUTH=LOGIN] Dovecot ready.
+Host1 capability before authentication: IMAP4rev1 SASL-IR LOGIN-REFERRALS ID ENABLE IDLE NAMESPACE LITERAL+ AUTH=PLAIN AUTH=LOGIN AUTH
+Host1: cp8.ulimitserver.com says it has CAPABILITY for AUTHENTICATE LOGIN
+Host1: success login on [cp8.ulimitserver.com] with user [postmaster@beobuild.rs] auth [LOGIN]
+Host2: connecting and login on host2 [194.146.57.67] port [993] with user [postmaster@beobuild.rs]
+Host2 IP address: 194.146.57.67
+Host2 banner: * OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE IDLE AUTH=PLAIN AUTH=LOGIN AUTH=DIGEST-MD5 AUTH=CRAM-MD5] Dovecot (Ubuntu) ready.
+Host2 capability before authentication: IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE IDLE AUTH=PLAIN AUTH=LOGIN AUTH=DIGEST-MD5 AUTH=CRAM-MD5 AUTH
+Host2: 194.146.57.67 says it has CAPABILITY for AUTHENTICATE LOGIN
+Host2: success login on [194.146.57.67] with user [postmaster@beobuild.rs] auth [LOGIN]
+Host1: state Authenticated
+Host2: state Authenticated
+Host1 capability once authenticated: IMAP4rev1 SASL-IR LOGIN-REFERRALS ID ENABLE IDLE SORT SORT=DISPLAY THREAD=REFERENCES THREAD=REFS THREAD=ORDEREDSUBJECT MULTIAPPEND URL-PARTIAL CATENATE UNSELECT CHILDREN NAMESPACE UIDPLUS LIST-EXTENDED I18NLEVEL=1 CONDSTORE QRESYNC ESEARCH ESORT SEARCHRES WITHIN CONTEXT=SEARCH LIST-STATUS BINARY MOVE SNIPPET=FUZZY PREVIEW=FUZZY STATUS=SIZE NAMESPACE LITERAL+ NOTIFY SPECIAL-USE COMPRESS=DEFLATE QUOTA THREAD I18NLEVEL CONTEXT SNIPPET PREVIEW STATUS COMPRESS
+Host2 capability once authenticated: IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE IDLE SORT SORT=DISPLAY THREAD=REFERENCES THREAD=REFS THREAD=ORDEREDSUBJECT MULTIAPPEND URL-PARTIAL CATENATE UNSELECT CHILDREN NAMESPACE UIDPLUS LIST-EXTENDED I18NLEVEL=1 CONDSTORE QRESYNC ESEARCH ESORT SEARCHRES WITHIN CONTEXT=SEARCH LIST-STATUS BINARY MOVE THREAD I18NLEVEL CONTEXT
+
+Host1: found ID capability. Sending/receiving ID, presented in raw IMAP for now.
+In order to avoid sending/receiving ID, use option --noid
+Sending: 4 ID ("name" "imapsync" "version" "1.977" "os" "linux" "vendor" "Gilles LAMIRAL" "support-url" "https://imapsync.lamiral.info/" "date" "23-Dec-2019 20:18:02 +0000" "side" "host1")
+Sent 181 bytes
+Read: 	* ID ("name" "Dovecot")
+  	4 OK ID completed (0.001 + 0.000 secs).
+
+
+Host2: found ID capability. Sending/receiving ID, presented in raw IMAP for now.
+In order to avoid sending/receiving ID, use option --noid
+Sending: 4 ID ("name" "imapsync" "version" "1.977" "os" "linux" "vendor" "Gilles LAMIRAL" "support-url" "https://imapsync.lamiral.info/" "date" "23-Dec-2019 20:18:02 +0000" "side" "host2")
+Sent 181 bytes
+Read: 	* ID ("name" "Dovecot")
+  	4 OK ID completed (0.001 + 0.000 secs).
+
+Host1: found 7 folders.
+Host2: found 1 folders.
+Host1: guessing separator from folder listing: [.]
+Host1: separator given by NAMESPACE: [.]
+Host2: guessing separator from folder listing: [/]
+Host2: separator given by NAMESPACE: [.]
+Host1: guessing prefix from folder listing: [INBOX.]
+Host1: prefix given by NAMESPACE: [INBOX.]
+Host2: guessing prefix from folder listing: []
+Host2: prefix given by NAMESPACE: []
+Host1: separator and prefix: [.][INBOX.]
+Host2: separator and prefix: [.][]
+Including all folders found by default. Use --subscribed or --folder or --folderrec or --include to select specific folders. Use --exclude to unselect specific folders.
+Host1: Checking wanted folders exist. Use --nocheckfoldersexist to avoid this check (shared of public namespace targeted).
+Host1: Checking wanted folders are selectable. Use --nocheckselectable to avoid this check.
+Turned on automapping folders ( use --noautomap to turn off automapping )
+Host1: special INBOX.Sent           = \Sent
+Host1: special INBOX.spam           = \Junk
+Host1: special INBOX.Trash          = \Trash
+Host1: special INBOX.Drafts         = \Drafts
+Host1: special INBOX.Archive        = \Archive
+
+
+++++ Listing folders
+All foldernames are presented between brackets like [X] where X is the foldername.
+When a foldername contains non-ASCII characters it is presented in the form
+[X] = [Y] where
+X is the imap foldername you have to use in command line options and
+Y is the utf8 output just printed for convenience, to recognize it.
+
+Host1: folders list (first the raw imap format then the [X] = [Y]):
+* LIST (\HasChildren) "." INBOX
+* LIST (\HasNoChildren \Sent) "." INBOX.Sent
+* LIST (\HasNoChildren) "." INBOX.Junk
+* LIST (\HasNoChildren \Junk) "." INBOX.spam
+* LIST (\HasNoChildren \Trash) "." INBOX.Trash
+* LIST (\HasNoChildren \Drafts) "." INBOX.Drafts
+* LIST (\HasNoChildren \Archive) "." INBOX.Archive
+17 OK List completed (0.001 + 0.000 secs).
+
+[INBOX]
+[INBOX.Archive]
+[INBOX.Drafts]
+[INBOX.Junk]
+[INBOX.Sent]
+[INBOX.Trash]
+[INBOX.spam]
+
+Host2: folders list (first the raw imap format then the [X] = [Y]):
+* LIST (\HasNoChildren) "." INBOX
+10 OK List completed (0.001 + 0.000 secs).
+
+[INBOX]
+
+Host1: will not syncing empty folders on host1. Use --noskipemptyfolders to create them anyway on host2
+
+Folders sizes before the synchronization.
+You can remove foldersizes listings by using "--nofoldersizes" and "--nofoldersizesatend"
+but then you will also lose the ETA (Estimation Time of Arrival) given after each message copy.
+Host1 folder     1/7 [INBOX]                             Size:    121880 Messages:     4 Biggest:     80598
+Host2 folder     1/7 [INBOX]                             Size:         0 Messages:     0 Biggest:         0
+Host2-Host1                                                      -121880              -4             -80598
+
+Host1 folder     2/7 [INBOX.Archive]                     Size:         0 Messages:     0 Biggest:         0
+Host2 folder     2/7 [Archive]                            does not exist yet
+Host2-Host1                                                            0               0                  0
+
+Host1 folder     3/7 [INBOX.Drafts]                      Size:         0 Messages:     0 Biggest:         0
+Host2 folder     3/7 [Drafts]                             does not exist yet
+Host2-Host1                                                            0               0                  0
+
+Host1 folder     4/7 [INBOX.Junk]                        Size:         0 Messages:     0 Biggest:         0
+Host2 folder     4/7 [Junk]                               does not exist yet
+Host2-Host1                                                            0               0                  0
+
+Host1 folder     5/7 [INBOX.Sent]                        Size:         0 Messages:     0 Biggest:         0
+Host2 folder     5/7 [Sent]                               does not exist yet
+Host2-Host1                                                            0               0                  0
+
+Host1 folder     6/7 [INBOX.Trash]                       Size:         0 Messages:     0 Biggest:         0
+Host2 folder     6/7 [Trash]                              does not exist yet
+Host2-Host1                                                            0               0                  0
+
+Host1 folder     7/7 [INBOX.spam]                        Size:         0 Messages:     0 Biggest:         0
+Host2 folder     7/7 [spam]                               does not exist yet
+Host2-Host1                                                            0               0                  0
+
+Host1 Nb folders:                     7 folders
+Host2 Nb folders:                     7 folders
+
+Host1 Nb messages:                    4 messages
+Host2 Nb messages:                    0 messages
+
+Host1 Total size:                121880 bytes (119.023 KiB)
+Host2 Total size:                     0 bytes (0.000 KiB)
+
+Host1 Biggest message:            80598 bytes (78.709 KiB)
+Host2 Biggest message:                0 bytes (0.000 KiB)
+
+Time spent on sizing:         1.9 seconds
+++++ Looping on each one of 7 folders to sync
+ETA: Thu Oct 29 00:51:50 2020  0 s  4/4 msgs left
+Folder     1/7 [INBOX]                             -> [INBOX]                            
+Host1: folder [INBOX] has 4 messages in total (mentioned by SELECT)
+Host2: folder [INBOX] has 0 messages in total (mentioned by SELECT)
+Host2: folder [INBOX] permanentflags: 
+Host1: folder [INBOX] considering 4 messages
+Host2: folder [INBOX] considering 0 messages
+Host1: folder [INBOX] selected 4 messages, duplicates 0
+Host2: folder [INBOX] selected 0 messages, duplicates 0
+msg INBOX/1 {1070}            copied to INBOX/1          2.96 msgs/s  3.097 KiB/s 1.045 KiB copied ETA: Thu Oct 29 00:51:51 2020  1 s  3/4 msgs left
+msg INBOX/2 {20087}           copied to INBOX/2          4.15 msgs/s  42.924 KiB/s 20.661 KiB copied ETA: Thu Oct 29 00:51:51 2020  0 s  2/4 msgs left
+msg INBOX/3 {20125}           copied to INBOX/3          5.00 msgs/s  67.198 KiB/s 40.314 KiB copied ETA: Thu Oct 29 00:51:51 2020  0 s  1/4 msgs left
+msg INBOX/4 {80598}           copied to INBOX/4          5.37 msgs/s  159.762 KiB/s 119.023 KiB copied ETA: Thu Oct 29 00:51:51 2020  0 s  0/4 msgs left
+ETA: Thu Oct 29 00:51:51 2020  0 s  0/4 msgs left
+Folder     2/7 [INBOX.Archive]                     -> [Archive]                          
+Host1: folder [INBOX.Archive] has 0 messages in total (mentioned by SELECT)
+Host1: skipping empty host1 folder [INBOX.Archive]
+ETA: Thu Oct 29 00:51:51 2020  0 s  0/4 msgs left
+Folder     3/7 [INBOX.Drafts]                      -> [Drafts]                           
+Host1: folder [INBOX.Drafts] has 0 messages in total (mentioned by SELECT)
+Host1: skipping empty host1 folder [INBOX.Drafts]
+ETA: Thu Oct 29 00:51:51 2020  0 s  0/4 msgs left
+Folder     4/7 [INBOX.Junk]                        -> [Junk]                             
+Host1: folder [INBOX.Junk] has 0 messages in total (mentioned by SELECT)
+Host1: skipping empty host1 folder [INBOX.Junk]
+ETA: Thu Oct 29 00:51:51 2020  0 s  0/4 msgs left
+Folder     5/7 [INBOX.Sent]                        -> [Sent]                             
+Host1: folder [INBOX.Sent] has 0 messages in total (mentioned by SELECT)
+Host1: skipping empty host1 folder [INBOX.Sent]
+ETA: Thu Oct 29 00:51:51 2020  0 s  0/4 msgs left
+Folder     6/7 [INBOX.Trash]                       -> [Trash]                            
+Host1: folder [INBOX.Trash] has 0 messages in total (mentioned by SELECT)
+Host1: skipping empty host1 folder [INBOX.Trash]
+ETA: Thu Oct 29 00:51:51 2020  0 s  0/4 msgs left
+Folder     7/7 [INBOX.spam]                        -> [spam]                             
+Host1: folder [INBOX.spam] has 0 messages in total (mentioned by SELECT)
+Host1: skipping empty host1 folder [INBOX.spam]
+ETA: Thu Oct 29 00:51:51 2020  0 s  0/4 msgs left
+++++ End looping on each folder
+
+Folders sizes after the synchronization.
+You can remove this foldersizes listing by using  "--nofoldersizesatend"
+Host1 folder     1/7 [INBOX]                             Size:    121880 Messages:     4 Biggest:     80598
+Host2 folder     1/7 [INBOX]                             Size:    121880 Messages:     4 Biggest:     80598
+Host2-Host1                                                            0               0                  0
+
+Host1 folder     2/7 [INBOX.Archive]                     Size:         0 Messages:     0 Biggest:         0
+Host2 folder     2/7 [Archive]                            does not exist yet
+Host2-Host1                                                            0               0                  0
+
+Host1 folder     3/7 [INBOX.Drafts]                      Size:         0 Messages:     0 Biggest:         0
+Host2 folder     3/7 [Drafts]                             does not exist yet
+Host2-Host1                                                            0               0                  0
+
+Host1 folder     4/7 [INBOX.Junk]                        Size:         0 Messages:     0 Biggest:         0
+Host2 folder     4/7 [Junk]                               does not exist yet
+Host2-Host1                                                            0               0                  0
+
+Host1 folder     5/7 [INBOX.Sent]                        Size:         0 Messages:     0 Biggest:         0
+Host2 folder     5/7 [Sent]                               does not exist yet
+Host2-Host1                                                            0               0                  0
+
+Host1 folder     6/7 [INBOX.Trash]                       Size:         0 Messages:     0 Biggest:         0
+Host2 folder     6/7 [Trash]                              does not exist yet
+Host2-Host1                                                            0               0                  0
+
+Host1 folder     7/7 [INBOX.spam]                        Size:         0 Messages:     0 Biggest:         0
+Host2 folder     7/7 [spam]                               does not exist yet
+Host2-Host1                                                            0               0                  0
+
+Host1 Nb folders:                     7 folders
+Host2 Nb folders:                     7 folders
+
+Host1 Nb messages:                    4 messages
+Host2 Nb messages:                    4 messages
+
+Host1 Total size:                121880 bytes (119.023 KiB)
+Host2 Total size:                121880 bytes (119.023 KiB)
+
+Host1 Biggest message:            80598 bytes (78.709 KiB)
+Host2 Biggest message:            80598 bytes (78.709 KiB)
+
+Time spent on sizing:         0.5 seconds
+++++ Statistics
+Transfer started on                     : Thu Oct 29 00:51:48 2020
+Transfer ended on                       : Thu Oct 29 00:51:51 2020
+Transfer time                           : 3.4 sec
+Folders synced                          : 7/7 synced
+Messages transferred                    : 4 
+Messages skipped                        : 0
+Messages found duplicate on host1       : 0
+Messages found duplicate on host2       : 0
+Messages found crossduplicate on host2  : 0
+Messages void (noheader) on host1       : 0  
+Messages void (noheader) on host2       : 0
+Messages found in host1 not in host2    : 0 messages
+Messages found in host2 not in host1    : 0 messages
+Messages deleted on host1               : 0
+Messages deleted on host2               : 0
+Total bytes transferred                 : 121880 (119.023 KiB)
+Total bytes skipped                     : 0 (0.000 KiB)
+Message rate                            : 1.2 messages/s
+Average bandwidth rate                  : 35.2 KiB/s
+Reconnections to host1                  : 0
+Reconnections to host2                  : 0
+Memory consumption at the end           : 165.9 MiB (started with 159.9 MiB)
+Load end is                             : 0.21 0.31 0.43 1/1203 on 2 cores
+Biggest message                         : 80598 bytes (78.709 KiB)
+Memory/biggest message ratio            : 2158.8
+Start difference host2 - host1          : -4 messages, -121880 bytes (-119.023 KiB)
+Final difference host2 - host1          : 0 messages, 0 bytes (0.000 KiB)
+The sync looks good, all 4 identified messages in host1 are on host2.
+There is no unidentified message
+The sync is strict, all 4 identified messages in host2 are on host1.
+Detected 0 errors
+
+Check if a new imapsync release is available by adding --releasecheck
+Homepage: https://imapsync.lamiral.info/
+Exiting with return value 0 (EX_OK: successful termination) 0/20 nb_errors/max_errors
+Log file is LOG_imapsync/2020_10_29_00_51_48_438_postmaster@beobuild.rs_postmaster@beobuild.rs.txt ( to change it, use --logfile filepath ; or use --nolog to turn off logging )

LOG_imapsync/2020_11_04_14_32_34_024_info@petco.rs_info@petco.rs.txt

@@ -0,0 +1,911 @@
+Here is imapsync 1.977 on host privremena, a linux system with 18.7/31.3 free GiB of RAM
+with Perl 5.28.1 and Mail::IMAPClient 3.42
+Transfer started at Wed Nov  4 14:32:34 2020
+PID is 26200 my PPID is 26199
+Log file is LOG_imapsync/2020_11_04_14_32_34_024_info@petco.rs_info@petco.rs.txt ( to change it, use --logfile path ; or use --nolog to turn off logging )
+Load is 0.32 0.29 0.35 1/1188 on 2 cores
+Current directory is /root/imapsync-master
+Real user id is root (uid 0)
+Effective user id is root (euid 0)
+$RCSfile: imapsync,v $ $Revision: 1.977 $ $Date: 2019/12/23 20:18:02 $ 
+Command line used, run by /usr/bin/perl:
+./imapsync --addheader --automap --host1 188.93.126.108 --host2 194.146.56.136 --password1 MASKED --password2 MASKED --user1 info@petco.rs --user2 info@petco.rs
+Temp directory is . ( to change it use --tmpdir dirpath )
+Under cgi context
+Umask set with 0077 (was 0022)
+REMOTE_ADDR is ::ffff:178.218.165.9
+HTTP_REFERER is http://148.251.112.220:8080/
+HTTP_USER_AGENT is Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/86.0.4240.111 Safari/537.36 Edg/86.0.622.61
+SERVER_SOFTWARE is ./webserver
+SERVER_PORT is 8080
+kill -QUIT 26200 # special behavior: call to sub catch_exit
+kill -TERM 26200 # special behavior: call to sub catch_exit
+kill -INT 26200 # special behavior: call to sub catch_reconnect
+kill -HUP 26200 # special behavior: call to sub catch_print
+kill -USR1 26200 # special behavior: call to sub toggle_sleep
+File ./imapsync_188.93.126.108_info@petco.rs_194.146.56.136_info@petco.rs.pid does not exist
+Error reading file ./imapsync_188.93.126.108_info@petco.rs_194.146.56.136_info@petco.rs.pid : No such file or directory
+PID file is ./imapsync_188.93.126.108_info@petco.rs_194.146.56.136_info@petco.rs.pid ( to change it, use --pidfile filepath ; to avoid it use --pidfile "" )
+Writing my PID 26200 in ./imapsync_188.93.126.108_info@petco.rs_194.146.56.136_info@petco.rs.pid
+Writing also my logfile name in ./imapsync_188.93.126.108_info@petco.rs_194.146.56.136_info@petco.rs.pid : LOG_imapsync/2020_11_04_14_32_34_024_info@petco.rs_info@petco.rs.txt
+Info: will resync flags for already transferred messages. Use --noresyncflags to not resync flags.
+Host1: probing ssl on port 993 ( use --nosslcheck to avoid this ssl probe ) 
+Host1: sslcheck detected open ssl port 993 so turning ssl on (use --nossl1 --notls1 to turn off SSL and TLS wizardry)
+Host2: probing ssl on port 993 ( use --nosslcheck to avoid this ssl probe ) 
+Host2: sslcheck detected open ssl port 993 so turning ssl on (use --nossl2 --notls2 to turn off SSL and TLS wizardry)
+SSL debug mode level is --debugssl 1 (can be set from 0 meaning no debug to 4 meaning max debug)
+Host1: SSL default mode is like --sslargs1 "SSL_verify_mode=0", meaning for host1 SSL_VERIFY_NONE, ie, do not check the certificate server.
+Host1: Use --sslargs1 SSL_verify_mode=1 to have SSL_VERIFY_PEER, ie, check the certificate server of host1
+Host2: SSL default mode is like --sslargs2 "SSL_verify_mode=0", meaning for host2 SSL_VERIFY_NONE, ie, do not check the certificate server.
+Host2: Use --sslargs2 SSL_verify_mode=1 to have SSL_VERIFY_PEER, ie, check the certificate server of host2
+Info: turned ON syncinternaldates, will set the internal dates (arrival dates) on host2 same as host1.
+Host1: will try to use LOGIN authentication on host1
+Host2: will try to use LOGIN authentication on host2
+Host1: imap connection timeout is 120 seconds
+Host2: imap connection timeout is 120 seconds
+Host1: IMAP server [188.93.126.108] port [993] user [info@petco.rs]
+Host2: IMAP server [194.146.56.136] port [993] user [info@petco.rs]
+Host1: connecting and login on host1 [188.93.126.108] port [993] with user [info@petco.rs]
+Host1 IP address: 188.93.126.108
+Host1 banner: * OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE IDLE AUTH=PLAIN AUTH=LOGIN] Dovecot ready.
+Host1 capability before authentication: IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE IDLE AUTH=PLAIN AUTH=LOGIN AUTH
+Host1: 188.93.126.108 says it has CAPABILITY for AUTHENTICATE LOGIN
+Host1: success login on [188.93.126.108] with user [info@petco.rs] auth [LOGIN]
+Host2: connecting and login on host2 [194.146.56.136] port [993] with user [info@petco.rs]
+Host2 IP address: 194.146.56.136
+Host2 banner: * OK [CAPABILITY IMAP4rev1 SASL-IR LOGIN-REFERRALS ID ENABLE IDLE LITERAL+ AUTH=PLAIN AUTH=LOGIN] Dovecot ready.
+Host2 capability before authentication: IMAP4rev1 SASL-IR LOGIN-REFERRALS ID ENABLE IDLE LITERAL+ AUTH=PLAIN AUTH=LOGIN AUTH
+Host2: 194.146.56.136 says it has CAPABILITY for AUTHENTICATE LOGIN
+Host2: success login on [194.146.56.136] with user [info@petco.rs] auth [LOGIN]
+Host1: state Authenticated
+Host2: state Authenticated
+Host1 capability once authenticated: IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE IDLE SORT SORT=DISPLAY THREAD=REFERENCES THREAD=REFS THREAD=ORDEREDSUBJECT MULTIAPPEND URL-PARTIAL CATENATE UNSELECT CHILDREN NAMESPACE UIDPLUS LIST-EXTENDED I18NLEVEL=1 CONDSTORE QRESYNC ESEARCH ESORT SEARCHRES WITHIN CONTEXT=SEARCH LIST-STATUS SPECIAL-USE BINARY MOVE QUOTA THREAD I18NLEVEL CONTEXT
+Host2 capability once authenticated: IMAP4rev1 SASL-IR LOGIN-REFERRALS ID ENABLE IDLE SORT SORT=DISPLAY THREAD=REFERENCES THREAD=REFS THREAD=ORDEREDSUBJECT MULTIAPPEND URL-PARTIAL CATENATE UNSELECT CHILDREN NAMESPACE UIDPLUS LIST-EXTENDED I18NLEVEL=1 CONDSTORE QRESYNC ESEARCH ESORT SEARCHRES WITHIN CONTEXT=SEARCH LIST-STATUS BINARY MOVE SNIPPET=FUZZY PREVIEW=FUZZY STATUS=SIZE LITERAL+ NOTIFY SPECIAL-USE THREAD I18NLEVEL CONTEXT SNIPPET PREVIEW STATUS
+
+Host1: found ID capability. Sending/receiving ID, presented in raw IMAP for now.
+In order to avoid sending/receiving ID, use option --noid
+Sending: 4 ID ("name" "imapsync" "version" "1.977" "os" "linux" "vendor" "Gilles LAMIRAL" "support-url" "https://imapsync.lamiral.info/" "date" "23-Dec-2019 20:18:02 +0000" "side" "host1")
+Sent 181 bytes
+Read: 	* ID ("name" "Dovecot")
+  	4 OK ID completed.
+
+
+Host2: found ID capability. Sending/receiving ID, presented in raw IMAP for now.
+In order to avoid sending/receiving ID, use option --noid
+Sending: 4 ID ("name" "imapsync" "version" "1.977" "os" "linux" "vendor" "Gilles LAMIRAL" "support-url" "https://imapsync.lamiral.info/" "date" "23-Dec-2019 20:18:02 +0000" "side" "host2")
+Sent 181 bytes
+Read: 	* ID ("name" "Dovecot")
+  	4 OK ID completed (0.001 + 0.000 secs).
+
+Host1: found 6 folders.
+Host2: found 3 folders.
+Host1: guessing separator from folder listing: [/]
+Host1: separator given by NAMESPACE: [.]
+Host2: guessing separator from folder listing: [/]
+Host2: separator given by NAMESPACE: [.]
+Host1: guessing prefix from folder listing: []
+Host1: prefix given by NAMESPACE: []
+Host2: guessing prefix from folder listing: []
+Host2: prefix given by NAMESPACE: []
+Host1: separator and prefix: [.][]
+Host2: separator and prefix: [.][]
+Including all folders found by default. Use --subscribed or --folder or --folderrec or --include to select specific folders. Use --exclude to unselect specific folders.
+Host1: Checking wanted folders exist. Use --nocheckfoldersexist to avoid this check (shared of public namespace targeted).
+Host1: Checking wanted folders are selectable. Use --nocheckselectable to avoid this check.
+Turned on automapping folders ( use --noautomap to turn off automapping )
+Host2: special Trash                = \Trash
+Host2: special Sent                 = \Sent
+
+Host1: Spam not \Junk because set to Junk
+
+++++ Listing folders
+All foldernames are presented between brackets like [X] where X is the foldername.
+When a foldername contains non-ASCII characters it is presented in the form
+[X] = [Y] where
+X is the imap foldername you have to use in command line options and
+Y is the utf8 output just printed for convenience, to recognize it.
+
+Host1: folders list (first the raw imap format then the [X] = [Y]):
+* LIST (\HasNoChildren) "." Sent
+* LIST (\HasNoChildren) "." Junk
+* LIST (\HasNoChildren) "." Spam
+* LIST (\HasNoChildren) "." Trash
+* LIST (\HasNoChildren) "." Drafts
+* LIST (\HasNoChildren) "." INBOX
+16 OK List completed.
+
+[Drafts]
+[INBOX]
+[Junk]
+[Sent]
+[Spam]
+[Trash]
+
+Host2: folders list (first the raw imap format then the [X] = [Y]):
+* LIST (\HasNoChildren \Trash) "." Trash
+* LIST (\HasNoChildren \Sent) "." Sent
+* LIST (\HasNoChildren) "." INBOX
+10 OK List completed (0.001 + 0.000 secs).
+
+[INBOX]
+[Sent]
+[Trash]
+
+Folders mapping from --automap feature (use --f1f2 to override any mapping):
+[Sent]                                   -> [Sent]                                  
+[Trash]                                  -> [Trash]                                 
+
+Host1: will not syncing empty folders on host1. Use --noskipemptyfolders to create them anyway on host2
+
+Folders sizes before the synchronization.
+You can remove foldersizes listings by using "--nofoldersizes" and "--nofoldersizesatend"
+but then you will also lose the ETA (Estimation Time of Arrival) given after each message copy.
+Host1 folder     1/6 [Drafts]                            Size:       796 Messages:     1 Biggest:       796
+Host2 folder     1/6 [Drafts]                             does not exist yet
+Host2-Host1                                                         -796              -1               -796
+
+Host1 folder     2/6 [INBOX]                             Size:  21792684 Messages:   311 Biggest:   2723952
+Host2 folder     2/6 [INBOX]                             Size:         0 Messages:     0 Biggest:         0
+Host2-Host1                                                    -21792684            -311           -2723952
+
+Host1 folder     3/6 [Junk]                              Size:         0 Messages:     0 Biggest:         0
+Host2 folder     3/6 [Junk]                               does not exist yet
+Host2-Host1                                                            0               0                  0
+
+Host1 folder     4/6 [Sent]                              Size:  17726462 Messages:   197 Biggest:   1152231
+Host2 folder     4/6 [Sent]                              Size:         0 Messages:     0 Biggest:         0
+Host2-Host1                                                    -17726462            -197           -1152231
+
+Host1 folder     5/6 [Spam]                              Size:         0 Messages:     0 Biggest:         0
+Host2 folder     5/6 [Spam]                               does not exist yet
+Host2-Host1                                                            0               0                  0
+
+Host1 folder     6/6 [Trash]                             Size:    209248 Messages:    96 Biggest:     34890
+Host2 folder     6/6 [Trash]                             Size:         0 Messages:     0 Biggest:         0
+Host2-Host1                                                      -209248             -96             -34890
+
+Host1 Nb folders:                     6 folders
+Host2 Nb folders:                     6 folders
+
+Host1 Nb messages:                  605 messages
+Host2 Nb messages:                    0 messages
+
+Host1 Total size:              39729190 bytes (37.889 MiB)
+Host2 Total size:                     0 bytes (0.000 KiB)
+
+Host1 Biggest message:          2723952 bytes (2.598 MiB)
+Host2 Biggest message:                0 bytes (0.000 KiB)
+
+Time spent on sizing:         2.8 seconds
+++++ Looping on each one of 6 folders to sync
+ETA: Wed Nov  4 14:32:36 2020  0 s  605/605 msgs left
+Folder     1/6 [Drafts]                            -> [Drafts]                           
+Host1: folder [Drafts] has 1 messages in total (mentioned by SELECT)
+Creating folder [Drafts] on host2
+Created folder [Drafts] on host2
+Host2: folder [Drafts] has 0 messages in total (mentioned by SELECT)
+Host2: folder [Drafts] permanentflags: 
+Host2: Subscribing to folder Drafts
+Host1: folder [Drafts] considering 1 messages
+Host2: folder [Drafts] considering 0 messages
+Host1: folder [Drafts] selected 1 messages, duplicates 0
+Host2: folder [Drafts] selected 0 messages, duplicates 0
+msg Drafts/10 {796}            copied to Drafts/1          2.02 msgs/s  1.569 KiB/s 0.777 KiB copied ETA: Wed Nov  4 14:37:36 2020  299 s  604/605 msgs left
+ETA: Wed Nov  4 14:37:36 2020  299 s  604/605 msgs left
+Folder     2/6 [INBOX]                             -> [INBOX]                            
+Host1: folder [INBOX] has 311 messages in total (mentioned by SELECT)
+Host2: folder [INBOX] has 0 messages in total (mentioned by SELECT)
+Host2: folder [INBOX] permanentflags: 
+Host1: folder [INBOX] considering 311 messages
+Host2: folder [INBOX] considering 0 messages
+Host1: folder [INBOX] selected 311 messages, duplicates 0
+Host2: folder [INBOX] selected 0 messages, duplicates 0
+msg INBOX/19 {103823}         copied to INBOX/1          1.26 msgs/s  64.425 KiB/s 102.167 KiB copied ETA: Wed Nov  4 14:40:36 2020  478 s  603/605 msgs left
+msg INBOX/20 {644}            copied to INBOX/2          1.78 msgs/s  61.042 KiB/s 102.796 KiB copied ETA: Wed Nov  4 14:38:16 2020  338 s  602/605 msgs left
+msg INBOX/21 {56182}          copied to INBOX/3          2.19 msgs/s  86.295 KiB/s 157.661 KiB copied ETA: Wed Nov  4 14:37:13 2020  275 s  601/605 msgs left
+msg INBOX/22 {43078}          copied to INBOX/4          2.53 msgs/s  101.002 KiB/s 199.729 KiB copied ETA: Wed Nov  4 14:36:36 2020  237 s  600/605 msgs left
+msg INBOX/23 {103731}         copied to INBOX/5          2.80 msgs/s  140.627 KiB/s 301.029 KiB copied ETA: Wed Nov  4 14:36:12 2020  214 s  599/605 msgs left
+msg INBOX/24 {67022}          copied to INBOX/6          3.06 msgs/s  160.114 KiB/s 366.480 KiB copied ETA: Wed Nov  4 14:35:54 2020  196 s  598/605 msgs left
+msg INBOX/33 {642}            copied to INBOX/7          3.36 msgs/s  154.006 KiB/s 367.107 KiB copied ETA: Wed Nov  4 14:35:37 2020  178 s  597/605 msgs left
+msg INBOX/34 {103908}         copied to INBOX/8          3.55 msgs/s  184.944 KiB/s 468.580 KiB copied ETA: Wed Nov  4 14:35:27 2020  168 s  596/605 msgs left
+msg INBOX/35 {104561}         copied to INBOX/9          3.70 msgs/s  211.238 KiB/s 570.690 KiB copied ETA: Wed Nov  4 14:35:20 2020  161 s  595/605 msgs left
+msg INBOX/37 {103851}         copied to INBOX/10         3.86 msgs/s  235.553 KiB/s 672.107 KiB copied ETA: Wed Nov  4 14:35:13 2020  154 s  594/605 msgs left
+msg INBOX/41 {102838}         copied to INBOX/11         4.00 msgs/s  257.201 KiB/s 772.535 KiB copied ETA: Wed Nov  4 14:35:08 2020  148 s  593/605 msgs left
+msg INBOX/43 {682}            copied to INBOX/12         4.18 msgs/s  248.529 KiB/s 773.201 KiB copied ETA: Wed Nov  4 14:35:01 2020  142 s  592/605 msgs left
+msg INBOX/44 {2857}           copied to INBOX/13         4.36 msgs/s  241.616 KiB/s 775.991 KiB copied ETA: Wed Nov  4 14:34:55 2020  136 s  591/605 msgs left
+msg INBOX/45 {682}            copied to INBOX/14         4.53 msgs/s  234.661 KiB/s 776.657 KiB copied ETA: Wed Nov  4 14:34:50 2020  130 s  590/605 msgs left
+msg INBOX/46 {17979}          copied to INBOX/15         4.67 msgs/s  231.717 KiB/s 794.215 KiB copied ETA: Wed Nov  4 14:34:46 2020  126 s  589/605 msgs left
+msg INBOX/47 {7862}           copied to INBOX/16         4.83 msgs/s  227.748 KiB/s 801.893 KiB copied ETA: Wed Nov  4 14:34:42 2020  122 s  588/605 msgs left
+msg INBOX/48 {2485}           copied to INBOX/17         4.99 msgs/s  222.771 KiB/s 804.319 KiB copied ETA: Wed Nov  4 14:34:38 2020  118 s  587/605 msgs left
+msg INBOX/49 {644}            copied to INBOX/18         5.13 msgs/s  217.260 KiB/s 804.948 KiB copied ETA: Wed Nov  4 14:34:34 2020  114 s  586/605 msgs left
+msg INBOX/50 {102743}         copied to INBOX/19         5.19 msgs/s  234.720 KiB/s 905.283 KiB copied ETA: Wed Nov  4 14:34:33 2020  113 s  585/605 msgs left
+msg INBOX/52 {102725}         copied to INBOX/20         5.25 msgs/s  251.173 KiB/s 0.982 MiB copied ETA: Wed Nov  4 14:34:32 2020  111 s  584/605 msgs left
+msg INBOX/53 {2547}           copied to INBOX/21         5.07 msgs/s  232.457 KiB/s 0.984 MiB copied ETA: Wed Nov  4 14:34:36 2020  115 s  583/605 msgs left
+msg INBOX/55 {104675}         copied to INBOX/22         5.13 msgs/s  247.488 KiB/s 1.084 MiB copied ETA: Wed Nov  4 14:34:34 2020  114 s  582/605 msgs left
+msg INBOX/63 {104771}         copied to INBOX/23         5.17 msgs/s  261.343 KiB/s 1.184 MiB copied ETA: Wed Nov  4 14:34:33 2020  112 s  581/605 msgs left
+msg INBOX/65 {14641}          copied to INBOX/24         5.27 msgs/s  258.450 KiB/s 1.198 MiB copied ETA: Wed Nov  4 14:34:31 2020  110 s  580/605 msgs left
+msg INBOX/71 {11645}          copied to INBOX/25         5.37 msgs/s  255.869 KiB/s 1.209 MiB copied ETA: Wed Nov  4 14:34:29 2020  108 s  579/605 msgs left
+msg INBOX/72 {104635}         copied to INBOX/26         5.42 msgs/s  268.917 KiB/s 1.309 MiB copied ETA: Wed Nov  4 14:34:28 2020  107 s  578/605 msgs left
+msg INBOX/73 {13227}          copied to INBOX/27         5.51 msgs/s  266.329 KiB/s 1.322 MiB copied ETA: Wed Nov  4 14:34:26 2020  105 s  577/605 msgs left
+msg INBOX/74 {14838}          copied to INBOX/28         5.60 msgs/s  264.082 KiB/s 1.336 MiB copied ETA: Wed Nov  4 14:34:24 2020  103 s  576/605 msgs left
+msg INBOX/76 {103799}         copied to INBOX/29         5.63 msgs/s  275.772 KiB/s 1.435 MiB copied ETA: Wed Nov  4 14:34:24 2020  102 s  575/605 msgs left
+msg INBOX/78 {106512}         copied to INBOX/30         5.66 msgs/s  287.246 KiB/s 1.536 MiB copied ETA: Wed Nov  4 14:34:23 2020  101 s  574/605 msgs left
+msg INBOX/79 {103829}         copied to INBOX/31         5.68 msgs/s  297.492 KiB/s 1.635 MiB copied ETA: Wed Nov  4 14:34:23 2020  101 s  573/605 msgs left
+msg INBOX/80 {104516}         copied to INBOX/32         5.72 msgs/s  307.851 KiB/s 1.735 MiB copied ETA: Wed Nov  4 14:34:22 2020  100 s  572/605 msgs left
+msg INBOX/84 {103839}         copied to INBOX/33         5.75 msgs/s  317.359 KiB/s 1.834 MiB copied ETA: Wed Nov  4 14:34:22 2020  99 s  571/605 msgs left
+msg INBOX/88 {109132}         copied to INBOX/34         5.76 msgs/s  326.841 KiB/s 1.938 MiB copied ETA: Wed Nov  4 14:34:21 2020  99 s  570/605 msgs left
+msg INBOX/91 {107619}         copied to INBOX/35         5.79 msgs/s  335.961 KiB/s 2.041 MiB copied ETA: Wed Nov  4 14:34:21 2020  98 s  569/605 msgs left
+msg INBOX/92 {124656}         copied to INBOX/36         5.83 msgs/s  348.321 KiB/s 2.160 MiB copied ETA: Wed Nov  4 14:34:20 2020  97 s  568/605 msgs left
+msg INBOX/93 {103795}         copied to INBOX/37         5.84 msgs/s  355.610 KiB/s 2.259 MiB copied ETA: Wed Nov  4 14:34:20 2020  97 s  567/605 msgs left
+msg INBOX/95 {1603}           copied to INBOX/38         5.91 msgs/s  350.906 KiB/s 2.260 MiB copied ETA: Wed Nov  4 14:34:19 2020  96 s  566/605 msgs left
+msg INBOX/97 {108540}         copied to INBOX/39         5.92 msgs/s  358.525 KiB/s 2.364 MiB copied ETA: Wed Nov  4 14:34:18 2020  95 s  565/605 msgs left
+msg INBOX/98 {103837}         copied to INBOX/40         5.93 msgs/s  365.004 KiB/s 2.463 MiB copied ETA: Wed Nov  4 14:34:18 2020  95 s  564/605 msgs left
+msg INBOX/100 {104127}        copied to INBOX/41         5.95 msgs/s  371.387 KiB/s 2.562 MiB copied ETA: Wed Nov  4 14:34:18 2020  95 s  563/605 msgs left
+msg INBOX/101 {104691}        copied to INBOX/42         5.93 msgs/s  375.702 KiB/s 2.662 MiB copied ETA: Wed Nov  4 14:34:18 2020  95 s  562/605 msgs left
+msg INBOX/103 {112102}        copied to INBOX/43         5.94 msgs/s  382.847 KiB/s 2.769 MiB copied ETA: Wed Nov  4 14:34:18 2020  94 s  561/605 msgs left
+msg INBOX/104 {31529}         copied to INBOX/44         5.98 msgs/s  380.898 KiB/s 2.799 MiB copied ETA: Wed Nov  4 14:34:18 2020  94 s  560/605 msgs left
+msg INBOX/106 {104771}        copied to INBOX/45         5.97 msgs/s  385.537 KiB/s 2.899 MiB copied ETA: Wed Nov  4 14:34:18 2020  94 s  559/605 msgs left
+msg INBOX/111 {104014}        copied to INBOX/46         6.00 msgs/s  391.779 KiB/s 2.998 MiB copied ETA: Wed Nov  4 14:34:17 2020  93 s  558/605 msgs left
+msg INBOX/112 {18003}         copied to INBOX/47         6.02 msgs/s  387.527 KiB/s 3.015 MiB copied ETA: Wed Nov  4 14:34:17 2020  92 s  557/605 msgs left
+msg INBOX/113 {113172}        copied to INBOX/48         6.03 msgs/s  393.415 KiB/s 3.123 MiB copied ETA: Wed Nov  4 14:34:17 2020  92 s  556/605 msgs left
+msg INBOX/116 {155187}        copied to INBOX/49         6.05 msgs/s  405.018 KiB/s 3.271 MiB copied ETA: Wed Nov  4 14:34:16 2020  92 s  555/605 msgs left
+msg INBOX/117 {49331}         copied to INBOX/50         6.05 msgs/s  403.402 KiB/s 3.318 MiB copied ETA: Wed Nov  4 14:34:16 2020  91 s  554/605 msgs left
+msg INBOX/123 {635}           copied to INBOX/51         6.10 msgs/s  398.877 KiB/s 3.319 MiB copied ETA: Wed Nov  4 14:34:15 2020  91 s  553/605 msgs left
+msg INBOX/125 {45778}         copied to INBOX/52         6.11 msgs/s  397.250 KiB/s 3.362 MiB copied ETA: Wed Nov  4 14:34:15 2020  90 s  552/605 msgs left
+msg INBOX/129 {644}           copied to INBOX/53         6.16 msgs/s  392.821 KiB/s 3.363 MiB copied ETA: Wed Nov  4 14:34:15 2020  89 s  551/605 msgs left
+msg INBOX/130 {2862}          copied to INBOX/54         6.20 msgs/s  388.785 KiB/s 3.366 MiB copied ETA: Wed Nov  4 14:34:14 2020  89 s  550/605 msgs left
+msg INBOX/131 {2862}          copied to INBOX/55         6.25 msgs/s  384.796 KiB/s 3.368 MiB copied ETA: Wed Nov  4 14:34:13 2020  88 s  549/605 msgs left
+msg INBOX/132 {3209}          copied to INBOX/56         6.29 msgs/s  381.203 KiB/s 3.372 MiB copied ETA: Wed Nov  4 14:34:12 2020  87 s  548/605 msgs left
+msg INBOX/133 {9309}          copied to INBOX/57         6.34 msgs/s  378.100 KiB/s 3.380 MiB copied ETA: Wed Nov  4 14:34:12 2020  86 s  547/605 msgs left
+msg INBOX/135 {656}           copied to INBOX/58         6.37 msgs/s  373.850 KiB/s 3.381 MiB copied ETA: Wed Nov  4 14:34:11 2020  86 s  546/605 msgs left
+msg INBOX/142 {113151}        copied to INBOX/59         6.37 msgs/s  379.037 KiB/s 3.489 MiB copied ETA: Wed Nov  4 14:34:11 2020  86 s  545/605 msgs left
+msg INBOX/143 {107563}        copied to INBOX/60         6.37 msgs/s  384.306 KiB/s 3.592 MiB copied ETA: Wed Nov  4 14:34:11 2020  85 s  544/605 msgs left
+msg INBOX/145 {104667}        copied to INBOX/61         6.37 msgs/s  388.560 KiB/s 3.691 MiB copied ETA: Wed Nov  4 14:34:11 2020  85 s  543/605 msgs left
+msg INBOX/151 {21701}         copied to INBOX/62         6.40 msgs/s  385.950 KiB/s 3.712 MiB copied ETA: Wed Nov  4 14:34:11 2020  85 s  542/605 msgs left
+msg INBOX/165 {109416}        copied to INBOX/63         6.39 msgs/s  390.031 KiB/s 3.816 MiB copied ETA: Wed Nov  4 14:34:11 2020  85 s  541/605 msgs left
+msg INBOX/174 {102776}        copied to INBOX/64         6.40 msgs/s  394.434 KiB/s 3.914 MiB copied ETA: Wed Nov  4 14:34:11 2020  84 s  540/605 msgs left
+msg INBOX/175 {103850}        copied to INBOX/65         6.40 msgs/s  398.416 KiB/s 4.013 MiB copied ETA: Wed Nov  4 14:34:11 2020  84 s  539/605 msgs left
+msg INBOX/176 {10392}         copied to INBOX/66         6.44 msgs/s  395.916 KiB/s 4.023 MiB copied ETA: Wed Nov  4 14:34:10 2020  84 s  538/605 msgs left
+msg INBOX/177 {23103}         copied to INBOX/67         6.46 msgs/s  393.734 KiB/s 4.045 MiB copied ETA: Wed Nov  4 14:34:10 2020  83 s  537/605 msgs left
+msg INBOX/184 {109416}        copied to INBOX/68         6.47 msgs/s  398.332 KiB/s 4.150 MiB copied ETA: Wed Nov  4 14:34:10 2020  83 s  536/605 msgs left
+msg INBOX/191 {641}           copied to INBOX/69         6.51 msgs/s  394.982 KiB/s 4.150 MiB copied ETA: Wed Nov  4 14:34:09 2020  82 s  535/605 msgs left
+msg INBOX/193 {102847}        copied to INBOX/70         6.51 msgs/s  398.693 KiB/s 4.248 MiB copied ETA: Wed Nov  4 14:34:09 2020  82 s  534/605 msgs left
+msg INBOX/201 {21391}         copied to INBOX/71         6.53 msgs/s  396.241 KiB/s 4.269 MiB copied ETA: Wed Nov  4 14:34:09 2020  82 s  533/605 msgs left
+msg INBOX/203 {109424}        copied to INBOX/72         6.53 msgs/s  400.498 KiB/s 4.373 MiB copied ETA: Wed Nov  4 14:34:09 2020  81 s  532/605 msgs left
+msg INBOX/204 {8857}          copied to INBOX/73         6.56 msgs/s  397.935 KiB/s 4.382 MiB copied ETA: Wed Nov  4 14:34:09 2020  81 s  531/605 msgs left
+msg INBOX/206 {34691}         copied to INBOX/74         6.57 msgs/s  395.954 KiB/s 4.415 MiB copied ETA: Wed Nov  4 14:34:08 2020  81 s  530/605 msgs left
+msg INBOX/214 {103760}        copied to INBOX/75         6.56 msgs/s  398.687 KiB/s 4.514 MiB copied ETA: Wed Nov  4 14:34:09 2020  81 s  529/605 msgs left
+msg INBOX/216 {2904}          copied to INBOX/76         6.59 msgs/s  395.636 KiB/s 4.516 MiB copied ETA: Wed Nov  4 14:34:08 2020  80 s  528/605 msgs left
+msg INBOX/223 {111081}        copied to INBOX/77         6.59 msgs/s  399.754 KiB/s 4.622 MiB copied ETA: Wed Nov  4 14:34:08 2020  80 s  527/605 msgs left
+msg INBOX/225 {111082}        copied to INBOX/78         6.59 msgs/s  403.953 KiB/s 4.728 MiB copied ETA: Wed Nov  4 14:34:08 2020  80 s  526/605 msgs left
+msg INBOX/230 {6284}          copied to INBOX/79         6.62 msgs/s  401.259 KiB/s 4.734 MiB copied ETA: Wed Nov  4 14:34:08 2020  79 s  525/605 msgs left
+msg INBOX/232 {109405}        copied to INBOX/80         6.63 msgs/s  405.278 KiB/s 4.839 MiB copied ETA: Wed Nov  4 14:34:08 2020  79 s  524/605 msgs left
+msg INBOX/236 {3540}          copied to INBOX/81         6.66 msgs/s  402.505 KiB/s 4.842 MiB copied ETA: Wed Nov  4 14:34:07 2020  79 s  523/605 msgs left
+msg INBOX/237 {3610}          copied to INBOX/82         6.69 msgs/s  399.644 KiB/s 4.845 MiB copied ETA: Wed Nov  4 14:34:07 2020  78 s  522/605 msgs left
+msg INBOX/238 {3612}          copied to INBOX/83         6.71 msgs/s  396.776 KiB/s 4.849 MiB copied ETA: Wed Nov  4 14:34:06 2020  78 s  521/605 msgs left
+msg INBOX/239 {3542}          copied to INBOX/84         6.74 msgs/s  394.114 KiB/s 4.852 MiB copied ETA: Wed Nov  4 14:34:06 2020  77 s  520/605 msgs left
+msg INBOX/240 {3614}          copied to INBOX/85         6.77 msgs/s  391.372 KiB/s 4.856 MiB copied ETA: Wed Nov  4 14:34:06 2020  77 s  519/605 msgs left
+msg INBOX/241 {3280}          copied to INBOX/86         6.80 msgs/s  388.692 KiB/s 4.859 MiB copied ETA: Wed Nov  4 14:34:05 2020  76 s  518/605 msgs left
+msg INBOX/242 {650}           copied to INBOX/87         6.82 msgs/s  385.731 KiB/s 4.859 MiB copied ETA: Wed Nov  4 14:34:05 2020  76 s  517/605 msgs left
+msg INBOX/243 {143316}        copied to INBOX/88         6.81 msgs/s  391.235 KiB/s 4.996 MiB copied ETA: Wed Nov  4 14:34:05 2020  76 s  516/605 msgs left
+msg INBOX/244 {138599}        copied to INBOX/89         6.79 msgs/s  396.254 KiB/s 5.128 MiB copied ETA: Wed Nov  4 14:34:05 2020  76 s  515/605 msgs left
+msg INBOX/251 {103711}        copied to INBOX/90         6.79 msgs/s  399.209 KiB/s 5.227 MiB copied ETA: Wed Nov  4 14:34:05 2020  76 s  514/605 msgs left
+msg INBOX/254 {118564}        copied to INBOX/91         6.78 msgs/s  403.132 KiB/s 5.340 MiB copied ETA: Wed Nov  4 14:34:06 2020  76 s  513/605 msgs left
+msg INBOX/263 {104691}        copied to INBOX/92         6.78 msgs/s  406.263 KiB/s 5.440 MiB copied ETA: Wed Nov  4 14:34:06 2020  75 s  512/605 msgs left
+msg INBOX/265 {103769}        copied to INBOX/93         6.77 msgs/s  408.751 KiB/s 5.539 MiB copied ETA: Wed Nov  4 14:34:06 2020  75 s  511/605 msgs left
+msg INBOX/269 {103664}        copied to INBOX/94         6.77 msgs/s  411.449 KiB/s 5.638 MiB copied ETA: Wed Nov  4 14:34:06 2020  75 s  510/605 msgs left
+msg INBOX/270 {109409}        copied to INBOX/95         6.77 msgs/s  414.460 KiB/s 5.742 MiB copied ETA: Wed Nov  4 14:34:06 2020  75 s  509/605 msgs left
+msg INBOX/279 {103873}        copied to INBOX/96         6.76 msgs/s  416.593 KiB/s 5.841 MiB copied ETA: Wed Nov  4 14:34:06 2020  75 s  508/605 msgs left
+msg INBOX/291 {103712}        copied to INBOX/97         6.76 msgs/s  419.361 KiB/s 5.940 MiB copied ETA: Wed Nov  4 14:34:06 2020  75 s  507/605 msgs left
+msg INBOX/293 {109409}        copied to INBOX/98         6.76 msgs/s  422.485 KiB/s 6.045 MiB copied ETA: Wed Nov  4 14:34:06 2020  75 s  506/605 msgs left
+msg INBOX/298 {102947}        copied to INBOX/99         6.76 msgs/s  425.099 KiB/s 6.143 MiB copied ETA: Wed Nov  4 14:34:06 2020  75 s  505/605 msgs left
+msg INBOX/302 {109386}        copied to INBOX/100        6.76 msgs/s  427.904 KiB/s 6.247 MiB copied ETA: Wed Nov  4 14:34:06 2020  75 s  504/605 msgs left
+msg INBOX/312 {670}           copied to INBOX/101        6.78 msgs/s  425.371 KiB/s 6.248 MiB copied ETA: Wed Nov  4 14:34:06 2020  74 s  503/605 msgs left
+msg INBOX/313 {102846}        copied to INBOX/102        6.78 msgs/s  427.863 KiB/s 6.346 MiB copied ETA: Wed Nov  4 14:34:06 2020  74 s  502/605 msgs left
+msg INBOX/320 {109383}        copied to INBOX/103        6.77 msgs/s  429.947 KiB/s 6.450 MiB copied ETA: Wed Nov  4 14:34:06 2020  74 s  501/605 msgs left
+msg INBOX/323 {639}           copied to INBOX/104        6.79 msgs/s  427.093 KiB/s 6.451 MiB copied ETA: Wed Nov  4 14:34:05 2020  74 s  500/605 msgs left
+msg INBOX/324 {102835}        copied to INBOX/105        6.78 msgs/s  429.218 KiB/s 6.549 MiB copied ETA: Wed Nov  4 14:34:06 2020  74 s  499/605 msgs left
+msg INBOX/326 {35779}         copied to INBOX/106        6.78 msgs/s  427.013 KiB/s 6.583 MiB copied ETA: Wed Nov  4 14:34:06 2020  73 s  498/605 msgs left
+msg INBOX/336 {8017}          copied to INBOX/107        6.79 msgs/s  424.604 KiB/s 6.591 MiB copied ETA: Wed Nov  4 14:34:05 2020  73 s  497/605 msgs left
+msg INBOX/337 {102717}        copied to INBOX/108        6.79 msgs/s  426.795 KiB/s 6.689 MiB copied ETA: Wed Nov  4 14:34:05 2020  73 s  496/605 msgs left
+msg INBOX/339 {7456}          copied to INBOX/109        6.81 msgs/s  424.386 KiB/s 6.696 MiB copied ETA: Wed Nov  4 14:34:05 2020  73 s  495/605 msgs left
+msg INBOX/341 {109387}        copied to INBOX/110        6.81 msgs/s  427.229 KiB/s 6.800 MiB copied ETA: Wed Nov  4 14:34:05 2020  73 s  494/605 msgs left
+msg INBOX/345 {102945}        copied to INBOX/111        6.82 msgs/s  430.024 KiB/s 6.898 MiB copied ETA: Wed Nov  4 14:34:05 2020  72 s  493/605 msgs left
+msg INBOX/347 {1167}          copied to INBOX/112        6.83 msgs/s  427.289 KiB/s 6.899 MiB copied ETA: Wed Nov  4 14:34:05 2020  72 s  492/605 msgs left
+msg INBOX/348 {1159}          copied to INBOX/113        6.85 msgs/s  424.558 KiB/s 6.900 MiB copied ETA: Wed Nov  4 14:34:05 2020  72 s  491/605 msgs left
+msg INBOX/349 {740}           copied to INBOX/114        6.87 msgs/s  422.182 KiB/s 6.901 MiB copied ETA: Wed Nov  4 14:34:04 2020  71 s  490/605 msgs left
+msg INBOX/350 {6759}          copied to INBOX/115        6.89 msgs/s  420.317 KiB/s 6.908 MiB copied ETA: Wed Nov  4 14:34:04 2020  71 s  489/605 msgs left
+msg INBOX/354 {102779}        copied to INBOX/116        6.89 msgs/s  422.415 KiB/s 7.006 MiB copied ETA: Wed Nov  4 14:34:04 2020  71 s  488/605 msgs left
+msg INBOX/356 {111063}        copied to INBOX/117        6.88 msgs/s  424.875 KiB/s 7.111 MiB copied ETA: Wed Nov  4 14:34:04 2020  71 s  487/605 msgs left
+msg INBOX/368 {6896}          copied to INBOX/118        6.91 msgs/s  423.032 KiB/s 7.118 MiB copied ETA: Wed Nov  4 14:34:04 2020  70 s  486/605 msgs left
+msg INBOX/371 {102822}        copied to INBOX/119        6.91 msgs/s  425.279 KiB/s 7.216 MiB copied ETA: Wed Nov  4 14:34:04 2020  70 s  485/605 msgs left
+msg INBOX/372 {103591}        copied to INBOX/120        6.91 msgs/s  427.491 KiB/s 7.315 MiB copied ETA: Wed Nov  4 14:34:04 2020  70 s  484/605 msgs left
+msg INBOX/374 {103808}        copied to INBOX/121        6.91 msgs/s  429.723 KiB/s 7.414 MiB copied ETA: Wed Nov  4 14:34:04 2020  70 s  483/605 msgs left
+msg INBOX/375 {13966}         copied to INBOX/122        6.93 msgs/s  428.324 KiB/s 7.427 MiB copied ETA: Wed Nov  4 14:34:04 2020  70 s  482/605 msgs left
+msg INBOX/379 {35715}         copied to INBOX/123        6.93 msgs/s  426.847 KiB/s 7.461 MiB copied ETA: Wed Nov  4 14:34:04 2020  69 s  481/605 msgs left
+msg INBOX/380 {6738}          copied to INBOX/124        6.95 msgs/s  424.932 KiB/s 7.468 MiB copied ETA: Wed Nov  4 14:34:03 2020  69 s  480/605 msgs left
+msg INBOX/381 {647}           copied to INBOX/125        6.97 msgs/s  422.874 KiB/s 7.468 MiB copied ETA: Wed Nov  4 14:34:03 2020  69 s  479/605 msgs left
+msg INBOX/383 {103929}        copied to INBOX/126        6.97 msgs/s  425.083 KiB/s 7.567 MiB copied ETA: Wed Nov  4 14:34:03 2020  69 s  478/605 msgs left
+msg INBOX/389 {103905}        copied to INBOX/127        6.96 msgs/s  427.046 KiB/s 7.667 MiB copied ETA: Wed Nov  4 14:34:03 2020  69 s  477/605 msgs left
+msg INBOX/391 {103771}        copied to INBOX/128        6.96 msgs/s  429.026 KiB/s 7.765 MiB copied ETA: Wed Nov  4 14:34:03 2020  68 s  476/605 msgs left
+msg INBOX/428 {102822}        copied to INBOX/129        6.96 msgs/s  431.070 KiB/s 7.864 MiB copied ETA: Wed Nov  4 14:34:03 2020  68 s  475/605 msgs left
+msg INBOX/482 {102816}        copied to INBOX/130        6.96 msgs/s  433.399 KiB/s 7.962 MiB copied ETA: Wed Nov  4 14:34:03 2020  68 s  474/605 msgs left
+msg INBOX/483 {103061}        copied to INBOX/131        6.97 msgs/s  435.646 KiB/s 8.060 MiB copied ETA: Wed Nov  4 14:34:03 2020  68 s  473/605 msgs left
+msg INBOX/486 {107566}        copied to INBOX/132        6.97 msgs/s  438.273 KiB/s 8.162 MiB copied ETA: Wed Nov  4 14:34:03 2020  68 s  472/605 msgs left
+msg INBOX/489 {16293}         copied to INBOX/133        6.99 msgs/s  436.626 KiB/s 8.178 MiB copied ETA: Wed Nov  4 14:34:03 2020  67 s  471/605 msgs left
+msg INBOX/494 {109238}        copied to INBOX/134        6.99 msgs/s  439.147 KiB/s 8.282 MiB copied ETA: Wed Nov  4 14:34:03 2020  67 s  470/605 msgs left
+msg INBOX/497 {16801}         copied to INBOX/135        6.99 msgs/s  436.977 KiB/s 8.298 MiB copied ETA: Wed Nov  4 14:34:03 2020  67 s  469/605 msgs left
+msg INBOX/500 {640}           copied to INBOX/136        7.01 msgs/s  434.778 KiB/s 8.299 MiB copied ETA: Wed Nov  4 14:34:03 2020  67 s  468/605 msgs left
+msg INBOX/501 {103953}        copied to INBOX/137        7.01 msgs/s  436.918 KiB/s 8.398 MiB copied ETA: Wed Nov  4 14:34:03 2020  67 s  467/605 msgs left
+msg INBOX/509 {102889}        copied to INBOX/138        7.02 msgs/s  439.257 KiB/s 8.496 MiB copied ETA: Wed Nov  4 14:34:03 2020  66 s  466/605 msgs left
+msg INBOX/517 {605179}        copied to INBOX/139        6.95 msgs/s  460.932 KiB/s 9.073 MiB copied ETA: Wed Nov  4 14:34:03 2020  67 s  465/605 msgs left
+msg INBOX/520 {109408}        copied to INBOX/140        6.95 msgs/s  463.111 KiB/s 9.178 MiB copied ETA: Wed Nov  4 14:34:03 2020  67 s  464/605 msgs left
+msg INBOX/521 {690}           copied to INBOX/141        6.96 msgs/s  460.795 KiB/s 9.178 MiB copied ETA: Wed Nov  4 14:34:03 2020  67 s  463/605 msgs left
+msg INBOX/522 {690}           copied to INBOX/142        6.98 msgs/s  458.554 KiB/s 9.179 MiB copied ETA: Wed Nov  4 14:34:03 2020  66 s  462/605 msgs left
+msg INBOX/524 {651}           copied to INBOX/143        6.99 msgs/s  456.533 KiB/s 9.179 MiB copied ETA: Wed Nov  4 14:34:03 2020  66 s  461/605 msgs left
+msg INBOX/526 {2846}          copied to INBOX/144        7.00 msgs/s  454.217 KiB/s 9.182 MiB copied ETA: Wed Nov  4 14:34:03 2020  66 s  460/605 msgs left
+msg INBOX/529 {102924}        copied to INBOX/145        7.01 msgs/s  456.158 KiB/s 9.280 MiB copied ETA: Wed Nov  4 14:34:03 2020  65 s  459/605 msgs left
+msg INBOX/538 {8970}          copied to INBOX/146        7.02 msgs/s  454.461 KiB/s 9.289 MiB copied ETA: Wed Nov  4 14:34:02 2020  65 s  458/605 msgs left
+msg INBOX/542 {108455}        copied to INBOX/147        7.03 msgs/s  456.755 KiB/s 9.392 MiB copied ETA: Wed Nov  4 14:34:02 2020  65 s  457/605 msgs left
+msg INBOX/577 {7524}          copied to INBOX/148        7.04 msgs/s  454.825 KiB/s 9.400 MiB copied ETA: Wed Nov  4 14:34:02 2020  65 s  456/605 msgs left
+msg INBOX/578 {109386}        copied to INBOX/149        7.04 msgs/s  456.925 KiB/s 9.504 MiB copied ETA: Wed Nov  4 14:34:02 2020  65 s  455/605 msgs left
+msg INBOX/580 {12147}         copied to INBOX/150        7.06 msgs/s  455.377 KiB/s 9.515 MiB copied ETA: Wed Nov  4 14:34:02 2020  64 s  454/605 msgs left
+msg INBOX/581 {102818}        copied to INBOX/151        7.06 msgs/s  457.021 KiB/s 9.613 MiB copied ETA: Wed Nov  4 14:34:02 2020  64 s  453/605 msgs left
+msg INBOX/586 {103736}        copied to INBOX/152        7.06 msgs/s  458.913 KiB/s 9.712 MiB copied ETA: Wed Nov  4 14:34:02 2020  64 s  452/605 msgs left
+msg INBOX/588 {102846}        copied to INBOX/153        7.06 msgs/s  460.776 KiB/s 9.810 MiB copied ETA: Wed Nov  4 14:34:02 2020  64 s  451/605 msgs left
+msg INBOX/589 {103769}        copied to INBOX/154        7.07 msgs/s  462.854 KiB/s 9.909 MiB copied ETA: Wed Nov  4 14:34:02 2020  64 s  450/605 msgs left
+msg INBOX/590 {3990}          copied to INBOX/155        7.08 msgs/s  460.916 KiB/s 9.913 MiB copied ETA: Wed Nov  4 14:34:02 2020  63 s  449/605 msgs left
+msg INBOX/596 {102869}        copied to INBOX/156        7.09 msgs/s  462.637 KiB/s 10.011 MiB copied ETA: Wed Nov  4 14:34:02 2020  63 s  448/605 msgs left
+msg INBOX/605 {123847}        copied to INBOX/157        7.09 msgs/s  465.211 KiB/s 10.129 MiB copied ETA: Wed Nov  4 14:34:02 2020  63 s  447/605 msgs left
+msg INBOX/606 {103770}        copied to INBOX/158        7.09 msgs/s  466.929 KiB/s 10.228 MiB copied ETA: Wed Nov  4 14:34:02 2020  63 s  446/605 msgs left
+msg INBOX/608 {639}           copied to INBOX/159        7.10 msgs/s  464.961 KiB/s 10.229 MiB copied ETA: Wed Nov  4 14:34:02 2020  63 s  445/605 msgs left
+msg INBOX/609 {102831}        copied to INBOX/160        7.11 msgs/s  466.883 KiB/s 10.327 MiB copied ETA: Wed Nov  4 14:34:01 2020  62 s  444/605 msgs left
+msg INBOX/613 {109382}        copied to INBOX/161        7.11 msgs/s  469.028 KiB/s 10.431 MiB copied ETA: Wed Nov  4 14:34:01 2020  62 s  443/605 msgs left
+msg INBOX/626 {102853}        copied to INBOX/162        7.12 msgs/s  470.774 KiB/s 10.530 MiB copied ETA: Wed Nov  4 14:34:01 2020  62 s  442/605 msgs left
+msg INBOX/634 {82338}         copied to INBOX/163        7.12 msgs/s  471.726 KiB/s 10.608 MiB copied ETA: Wed Nov  4 14:34:01 2020  62 s  441/605 msgs left
+msg INBOX/639 {95496}         copied to INBOX/164        7.13 msgs/s  473.115 KiB/s 10.699 MiB copied ETA: Wed Nov  4 14:34:01 2020  62 s  440/605 msgs left
+msg INBOX/641 {4162}          copied to INBOX/165        7.13 msgs/s  470.933 KiB/s 10.703 MiB copied ETA: Wed Nov  4 14:34:01 2020  62 s  439/605 msgs left
+msg INBOX/642 {642}           copied to INBOX/166        7.14 msgs/s  468.834 KiB/s 10.704 MiB copied ETA: Wed Nov  4 14:34:01 2020  61 s  438/605 msgs left
+msg INBOX/643 {103799}        copied to INBOX/167        7.14 msgs/s  470.387 KiB/s 10.803 MiB copied ETA: Wed Nov  4 14:34:01 2020  61 s  437/605 msgs left
+msg INBOX/644 {5948}          copied to INBOX/168        7.15 msgs/s  468.542 KiB/s 10.808 MiB copied ETA: Wed Nov  4 14:34:01 2020  61 s  436/605 msgs left
+msg INBOX/649 {652}           copied to INBOX/169        7.17 msgs/s  466.610 KiB/s 10.809 MiB copied ETA: Wed Nov  4 14:34:01 2020  61 s  435/605 msgs left
+msg INBOX/656 {664}           copied to INBOX/170        7.18 msgs/s  464.603 KiB/s 10.810 MiB copied ETA: Wed Nov  4 14:34:01 2020  60 s  434/605 msgs left
+msg INBOX/660 {7245}          copied to INBOX/171        7.19 msgs/s  463.094 KiB/s 10.817 MiB copied ETA: Wed Nov  4 14:34:00 2020  60 s  433/605 msgs left
+msg INBOX/661 {95499}         copied to INBOX/172        7.19 msgs/s  464.498 KiB/s 10.908 MiB copied ETA: Wed Nov  4 14:34:00 2020  60 s  432/605 msgs left
+msg INBOX/662 {644}           copied to INBOX/173        7.20 msgs/s  462.448 KiB/s 10.908 MiB copied ETA: Wed Nov  4 14:34:00 2020  60 s  431/605 msgs left
+msg INBOX/664 {5086}          copied to INBOX/174        7.21 msgs/s  460.612 KiB/s 10.913 MiB copied ETA: Wed Nov  4 14:34:00 2020  60 s  430/605 msgs left
+msg INBOX/665 {150297}        copied to INBOX/175        7.21 msgs/s  463.926 KiB/s 11.056 MiB copied ETA: Wed Nov  4 14:34:00 2020  59 s  429/605 msgs left
+msg INBOX/668 {6408}          copied to INBOX/176        7.22 msgs/s  461.775 KiB/s 11.063 MiB copied ETA: Wed Nov  4 14:34:00 2020  59 s  428/605 msgs left
+msg INBOX/669 {9769}          copied to INBOX/177        7.22 msgs/s  459.854 KiB/s 11.072 MiB copied ETA: Wed Nov  4 14:34:00 2020  59 s  427/605 msgs left
+msg INBOX/671 {107525}        copied to INBOX/178        7.22 msgs/s  461.625 KiB/s 11.174 MiB copied ETA: Wed Nov  4 14:34:00 2020  59 s  426/605 msgs left
+msg INBOX/683 {110477}        copied to INBOX/179        7.22 msgs/s  463.293 KiB/s 11.280 MiB copied ETA: Wed Nov  4 14:34:00 2020  59 s  425/605 msgs left
+msg INBOX/689 {107529}        copied to INBOX/180        7.22 msgs/s  464.783 KiB/s 11.382 MiB copied ETA: Wed Nov  4 14:34:00 2020  59 s  424/605 msgs left
+msg INBOX/690 {103779}        copied to INBOX/181        7.21 msgs/s  465.978 KiB/s 11.481 MiB copied ETA: Wed Nov  4 14:34:00 2020  59 s  423/605 msgs left
+msg INBOX/691 {645}           copied to INBOX/182        7.22 msgs/s  463.980 KiB/s 11.482 MiB copied ETA: Wed Nov  4 14:34:00 2020  58 s  422/605 msgs left
+msg INBOX/694 {103698}        copied to INBOX/183        7.22 msgs/s  465.219 KiB/s 11.581 MiB copied ETA: Wed Nov  4 14:34:00 2020  58 s  421/605 msgs left
+msg INBOX/695 {5389}          copied to INBOX/184        7.23 msgs/s  463.772 KiB/s 11.586 MiB copied ETA: Wed Nov  4 14:34:00 2020  58 s  420/605 msgs left
+msg INBOX/697 {104578}        copied to INBOX/185        7.24 msgs/s  465.502 KiB/s 11.686 MiB copied ETA: Wed Nov  4 14:34:00 2020  58 s  419/605 msgs left
+msg INBOX/698 {109395}        copied to INBOX/186        7.24 msgs/s  467.176 KiB/s 11.790 MiB copied ETA: Wed Nov  4 14:34:00 2020  58 s  418/605 msgs left
+msg INBOX/699 {7324}          copied to INBOX/187        7.24 msgs/s  465.522 KiB/s 11.797 MiB copied ETA: Wed Nov  4 14:34:00 2020  58 s  417/605 msgs left
+msg INBOX/707 {103763}        copied to INBOX/188        7.25 msgs/s  466.958 KiB/s 11.896 MiB copied ETA: Wed Nov  4 14:34:00 2020  57 s  416/605 msgs left
+msg INBOX/718 {103757}        copied to INBOX/189        7.25 msgs/s  468.371 KiB/s 11.995 MiB copied ETA: Wed Nov  4 14:34:00 2020  57 s  415/605 msgs left
+msg INBOX/720 {679}           copied to INBOX/190        7.26 msgs/s  466.694 KiB/s 11.995 MiB copied ETA: Wed Nov  4 14:34:00 2020  57 s  414/605 msgs left
+msg INBOX/723 {108451}        copied to INBOX/191        7.25 msgs/s  468.099 KiB/s 12.099 MiB copied ETA: Wed Nov  4 14:34:00 2020  57 s  413/605 msgs left
+msg INBOX/725 {102812}        copied to INBOX/192        7.25 msgs/s  469.474 KiB/s 12.197 MiB copied ETA: Wed Nov  4 14:34:00 2020  57 s  412/605 msgs left
+msg INBOX/726 {102840}        copied to INBOX/193        7.26 msgs/s  470.861 KiB/s 12.295 MiB copied ETA: Wed Nov  4 14:34:00 2020  57 s  411/605 msgs left
+msg INBOX/735 {7453}          copied to INBOX/194        7.26 msgs/s  469.032 KiB/s 12.302 MiB copied ETA: Wed Nov  4 14:34:00 2020  56 s  410/605 msgs left
+msg INBOX/737 {15938}         copied to INBOX/195        7.27 msgs/s  467.940 KiB/s 12.317 MiB copied ETA: Wed Nov  4 14:34:00 2020  56 s  409/605 msgs left
+msg INBOX/740 {102805}        copied to INBOX/196        7.27 msgs/s  469.360 KiB/s 12.415 MiB copied ETA: Wed Nov  4 14:34:00 2020  56 s  408/605 msgs left
+msg INBOX/741 {109976}        copied to INBOX/197        7.27 msgs/s  471.020 KiB/s 12.520 MiB copied ETA: Wed Nov  4 14:34:00 2020  56 s  407/605 msgs left
+msg INBOX/743 {115599}        copied to INBOX/198        7.26 msgs/s  471.941 KiB/s 12.631 MiB copied ETA: Wed Nov  4 14:34:00 2020  56 s  406/605 msgs left
+msg INBOX/744 {17880}         copied to INBOX/199        7.26 msgs/s  470.245 KiB/s 12.648 MiB copied ETA: Wed Nov  4 14:34:00 2020  56 s  405/605 msgs left
+msg INBOX/745 {103780}        copied to INBOX/200        7.26 msgs/s  471.513 KiB/s 12.747 MiB copied ETA: Wed Nov  4 14:34:00 2020  56 s  404/605 msgs left
+msg INBOX/751 {1481}          copied to INBOX/201        7.27 msgs/s  469.866 KiB/s 12.748 MiB copied ETA: Wed Nov  4 14:34:00 2020  55 s  403/605 msgs left
+msg INBOX/753 {34124}         copied to INBOX/202        7.27 msgs/s  468.567 KiB/s 12.781 MiB copied ETA: Wed Nov  4 14:34:00 2020  55 s  402/605 msgs left
+msg INBOX/757 {199508}        copied to INBOX/203        7.26 msgs/s  472.691 KiB/s 12.971 MiB copied ETA: Wed Nov  4 14:34:00 2020  55 s  401/605 msgs left
+msg INBOX/759 {102847}        copied to INBOX/204        7.26 msgs/s  473.708 KiB/s 13.069 MiB copied ETA: Wed Nov  4 14:34:00 2020  55 s  400/605 msgs left
+msg INBOX/764 {3577}          copied to INBOX/205        7.27 msgs/s  472.206 KiB/s 13.072 MiB copied ETA: Wed Nov  4 14:34:00 2020  55 s  399/605 msgs left
+msg INBOX/765 {111986}        copied to INBOX/206        7.27 msgs/s  473.836 KiB/s 13.179 MiB copied ETA: Wed Nov  4 14:34:00 2020  55 s  398/605 msgs left
+msg INBOX/766 {103071}        copied to INBOX/207        7.27 msgs/s  474.992 KiB/s 13.277 MiB copied ETA: Wed Nov  4 14:34:00 2020  55 s  397/605 msgs left
+msg INBOX/768 {103742}        copied to INBOX/208        7.27 msgs/s  476.338 KiB/s 13.376 MiB copied ETA: Wed Nov  4 14:34:00 2020  54 s  396/605 msgs left
+msg INBOX/785 {102833}        copied to INBOX/209        7.27 msgs/s  477.381 KiB/s 13.474 MiB copied ETA: Wed Nov  4 14:34:00 2020  54 s  395/605 msgs left
+msg INBOX/787 {103805}        copied to INBOX/210        7.27 msgs/s  478.615 KiB/s 13.573 MiB copied ETA: Wed Nov  4 14:34:00 2020  54 s  394/605 msgs left
+msg INBOX/790 {102891}        copied to INBOX/211        7.27 msgs/s  479.845 KiB/s 13.671 MiB copied ETA: Wed Nov  4 14:34:00 2020  54 s  393/605 msgs left
+msg INBOX/791 {21105}         copied to INBOX/212        7.27 msgs/s  478.359 KiB/s 13.692 MiB copied ETA: Wed Nov  4 14:34:00 2020  54 s  392/605 msgs left
+msg INBOX/798 {102821}        copied to INBOX/213        7.27 msgs/s  479.704 KiB/s 13.790 MiB copied ETA: Wed Nov  4 14:34:00 2020  54 s  391/605 msgs left
+msg INBOX/799 {16874}         copied to INBOX/214        7.27 msgs/s  478.158 KiB/s 13.806 MiB copied ETA: Wed Nov  4 14:34:00 2020  54 s  390/605 msgs left
+msg INBOX/800 {103779}        copied to INBOX/215        7.28 msgs/s  479.614 KiB/s 13.905 MiB copied ETA: Wed Nov  4 14:33:59 2020  53 s  389/605 msgs left
+msg INBOX/824 {114138}        copied to INBOX/216        7.28 msgs/s  481.101 KiB/s 14.014 MiB copied ETA: Wed Nov  4 14:33:59 2020  53 s  388/605 msgs left
+msg INBOX/826 {30088}         copied to INBOX/217        7.28 msgs/s  480.062 KiB/s 14.042 MiB copied ETA: Wed Nov  4 14:33:59 2020  53 s  387/605 msgs left
+msg INBOX/834 {947}           copied to INBOX/218        7.29 msgs/s  478.534 KiB/s 14.043 MiB copied ETA: Wed Nov  4 14:33:59 2020  53 s  386/605 msgs left
+msg INBOX/836 {648}           copied to INBOX/219        7.30 msgs/s  476.997 KiB/s 14.044 MiB copied ETA: Wed Nov  4 14:33:59 2020  53 s  385/605 msgs left
+msg INBOX/837 {1015}          copied to INBOX/220        7.31 msgs/s  475.424 KiB/s 14.045 MiB copied ETA: Wed Nov  4 14:33:59 2020  53 s  384/605 msgs left
+msg INBOX/840 {557993}        copied to INBOX/221        7.28 msgs/s  489.395 KiB/s 14.577 MiB copied ETA: Wed Nov  4 14:33:59 2020  53 s  383/605 msgs left
+msg INBOX/841 {102845}        copied to INBOX/222        7.25 msgs/s  488.511 KiB/s 14.675 MiB copied ETA: Wed Nov  4 14:34:00 2020  53 s  382/605 msgs left
+msg INBOX/842 {2322}          copied to INBOX/223        7.22 msgs/s  484.381 KiB/s 14.677 MiB copied ETA: Wed Nov  4 14:34:00 2020  53 s  381/605 msgs left
+msg INBOX/844 {107589}        copied to INBOX/224        7.19 msgs/s  483.759 KiB/s 14.780 MiB copied ETA: Wed Nov  4 14:34:00 2020  53 s  380/605 msgs left
+msg INBOX/845 {650}           copied to INBOX/225        7.19 msgs/s  481.413 KiB/s 14.780 MiB copied ETA: Wed Nov  4 14:34:01 2020  53 s  379/605 msgs left
+msg INBOX/846 {25810}         copied to INBOX/226        7.19 msgs/s  480.103 KiB/s 14.805 MiB copied ETA: Wed Nov  4 14:34:00 2020  53 s  378/605 msgs left
+msg INBOX/851 {648}           copied to INBOX/227        7.13 msgs/s  474.370 KiB/s 14.806 MiB copied ETA: Wed Nov  4 14:34:01 2020  53 s  377/605 msgs left
+msg INBOX/853 {648}           copied to INBOX/228        7.06 msgs/s  467.431 KiB/s 14.806 MiB copied ETA: Wed Nov  4 14:34:02 2020  53 s  376/605 msgs left
+msg INBOX/855 {110171}        copied to INBOX/229        7.00 msgs/s  464.689 KiB/s 14.911 MiB copied ETA: Wed Nov  4 14:34:03 2020  54 s  375/605 msgs left
+msg INBOX/865 {103828}        copied to INBOX/230        6.99 msgs/s  464.814 KiB/s 15.010 MiB copied ETA: Wed Nov  4 14:34:03 2020  54 s  374/605 msgs left
+msg INBOX/866 {1217}          copied to INBOX/231        7.00 msgs/s  463.521 KiB/s 15.012 MiB copied ETA: Wed Nov  4 14:34:03 2020  53 s  373/605 msgs left
+msg INBOX/868 {14440}         copied to INBOX/232        7.00 msgs/s  462.560 KiB/s 15.025 MiB copied ETA: Wed Nov  4 14:34:03 2020  53 s  372/605 msgs left
+msg INBOX/871 {102932}        copied to INBOX/233        7.01 msgs/s  463.885 KiB/s 15.123 MiB copied ETA: Wed Nov  4 14:34:03 2020  53 s  371/605 msgs left
+msg INBOX/890 {107665}        copied to INBOX/234        7.01 msgs/s  465.252 KiB/s 15.226 MiB copied ETA: Wed Nov  4 14:34:03 2020  53 s  370/605 msgs left
+msg INBOX/892 {106594}        copied to INBOX/235        7.00 msgs/s  465.570 KiB/s 15.328 MiB copied ETA: Wed Nov  4 14:34:03 2020  53 s  369/605 msgs left
+msg INBOX/893 {960}           copied to INBOX/236        7.01 msgs/s  464.082 KiB/s 15.329 MiB copied ETA: Wed Nov  4 14:34:03 2020  53 s  368/605 msgs left
+msg INBOX/897 {17193}         copied to INBOX/237        7.01 msgs/s  462.661 KiB/s 15.345 MiB copied ETA: Wed Nov  4 14:34:03 2020  52 s  367/605 msgs left
+msg INBOX/898 {7316}          copied to INBOX/238        7.01 msgs/s  461.405 KiB/s 15.352 MiB copied ETA: Wed Nov  4 14:34:03 2020  52 s  366/605 msgs left
+msg INBOX/904 {640}           copied to INBOX/239        7.02 msgs/s  460.010 KiB/s 15.353 MiB copied ETA: Wed Nov  4 14:34:02 2020  52 s  365/605 msgs left
+msg INBOX/905 {102829}        copied to INBOX/240        7.02 msgs/s  461.006 KiB/s 15.451 MiB copied ETA: Wed Nov  4 14:34:02 2020  52 s  364/605 msgs left
+msg INBOX/906 {103774}        copied to INBOX/241        7.02 msgs/s  462.063 KiB/s 15.550 MiB copied ETA: Wed Nov  4 14:34:02 2020  52 s  363/605 msgs left
+msg INBOX/907 {1054}          copied to INBOX/242        7.03 msgs/s  460.709 KiB/s 15.551 MiB copied ETA: Wed Nov  4 14:34:02 2020  51 s  362/605 msgs left
+msg INBOX/908 {1172}          copied to INBOX/243        7.04 msgs/s  459.405 KiB/s 15.552 MiB copied ETA: Wed Nov  4 14:34:02 2020  51 s  361/605 msgs left
+msg INBOX/909 {103802}        copied to INBOX/244        7.04 msgs/s  460.648 KiB/s 15.651 MiB copied ETA: Wed Nov  4 14:34:02 2020  51 s  360/605 msgs left
+msg INBOX/910 {1344}          copied to INBOX/245        7.05 msgs/s  459.258 KiB/s 15.652 MiB copied ETA: Wed Nov  4 14:34:02 2020  51 s  359/605 msgs left
+msg INBOX/911 {7098}          copied to INBOX/246        7.05 msgs/s  457.988 KiB/s 15.659 MiB copied ETA: Wed Nov  4 14:34:02 2020  51 s  358/605 msgs left
+msg INBOX/912 {107476}        copied to INBOX/247        7.06 msgs/s  459.168 KiB/s 15.761 MiB copied ETA: Wed Nov  4 14:34:02 2020  51 s  357/605 msgs left
+msg INBOX/913 {2435}          copied to INBOX/248        7.06 msgs/s  457.885 KiB/s 15.764 MiB copied ETA: Wed Nov  4 14:34:02 2020  50 s  356/605 msgs left
+msg INBOX/914 {19834}         copied to INBOX/249        7.06 msgs/s  456.667 KiB/s 15.783 MiB copied ETA: Wed Nov  4 14:34:02 2020  50 s  355/605 msgs left
+msg INBOX/917 {103720}        copied to INBOX/250        7.07 msgs/s  457.942 KiB/s 15.882 MiB copied ETA: Wed Nov  4 14:34:02 2020  50 s  354/605 msgs left
+msg INBOX/919 {4077}          copied to INBOX/251        7.08 msgs/s  456.788 KiB/s 15.885 MiB copied ETA: Wed Nov  4 14:34:02 2020  50 s  353/605 msgs left
+msg INBOX/920 {676}           copied to INBOX/252        7.08 msgs/s  455.540 KiB/s 15.886 MiB copied ETA: Wed Nov  4 14:34:02 2020  50 s  352/605 msgs left
+msg INBOX/921 {103785}        copied to INBOX/253        7.09 msgs/s  456.641 KiB/s 15.985 MiB copied ETA: Wed Nov  4 14:34:02 2020  50 s  351/605 msgs left
+msg INBOX/928 {4215}          copied to INBOX/254        7.10 msgs/s  455.558 KiB/s 15.989 MiB copied ETA: Wed Nov  4 14:34:02 2020  49 s  350/605 msgs left
+msg INBOX/939 {1343}          copied to INBOX/255        7.10 msgs/s  454.285 KiB/s 15.990 MiB copied ETA: Wed Nov  4 14:34:02 2020  49 s  349/605 msgs left
+msg INBOX/940 {102836}        copied to INBOX/256        7.10 msgs/s  455.255 KiB/s 16.088 MiB copied ETA: Wed Nov  4 14:34:02 2020  49 s  348/605 msgs left
+msg INBOX/941 {103759}        copied to INBOX/257        7.10 msgs/s  456.328 KiB/s 16.187 MiB copied ETA: Wed Nov  4 14:34:02 2020  49 s  347/605 msgs left
+msg INBOX/942 {102845}        copied to INBOX/258        7.10 msgs/s  457.290 KiB/s 16.285 MiB copied ETA: Wed Nov  4 14:34:02 2020  49 s  346/605 msgs left
+msg INBOX/943 {1556}          copied to INBOX/259        7.11 msgs/s  455.977 KiB/s 16.287 MiB copied ETA: Wed Nov  4 14:34:01 2020  49 s  345/605 msgs left
+msg INBOX/944 {1278}          copied to INBOX/260        7.11 msgs/s  454.604 KiB/s 16.288 MiB copied ETA: Wed Nov  4 14:34:01 2020  48 s  344/605 msgs left
+msg INBOX/945 {103777}        copied to INBOX/261        7.11 msgs/s  455.601 KiB/s 16.387 MiB copied ETA: Wed Nov  4 14:34:01 2020  48 s  343/605 msgs left
+msg INBOX/952 {15995}         copied to INBOX/262        7.12 msgs/s  454.687 KiB/s 16.402 MiB copied ETA: Wed Nov  4 14:34:01 2020  48 s  342/605 msgs left
+msg INBOX/953 {2723952}       copied to INBOX/263        6.95 msgs/s  512.043 KiB/s 19.000 MiB copied ETA: Wed Nov  4 14:34:03 2020  49 s  341/605 msgs left
+msg INBOX/954 {6717}          copied to INBOX/264        6.96 msgs/s  510.952 KiB/s 19.007 MiB copied ETA: Wed Nov  4 14:34:03 2020  49 s  340/605 msgs left
+msg INBOX/955 {103673}        copied to INBOX/265        6.96 msgs/s  511.642 KiB/s 19.105 MiB copied ETA: Wed Nov  4 14:34:03 2020  49 s  339/605 msgs left
+msg INBOX/956 {104555}        copied to INBOX/266        6.96 msgs/s  512.671 KiB/s 19.205 MiB copied ETA: Wed Nov  4 14:34:03 2020  49 s  338/605 msgs left
+msg INBOX/957 {103648}        copied to INBOX/267        6.96 msgs/s  513.628 KiB/s 19.304 MiB copied ETA: Wed Nov  4 14:34:03 2020  48 s  337/605 msgs left
+msg INBOX/958 {102750}        copied to INBOX/268        6.97 msgs/s  514.603 KiB/s 19.402 MiB copied ETA: Wed Nov  4 14:34:03 2020  48 s  336/605 msgs left
+msg INBOX/959 {103692}        copied to INBOX/269        6.97 msgs/s  515.586 KiB/s 19.501 MiB copied ETA: Wed Nov  4 14:34:03 2020  48 s  335/605 msgs left
+msg INBOX/960 {103639}        copied to INBOX/270        6.97 msgs/s  516.414 KiB/s 19.600 MiB copied ETA: Wed Nov  4 14:34:03 2020  48 s  334/605 msgs left
+msg INBOX/961 {931}           copied to INBOX/271        6.98 msgs/s  515.087 KiB/s 19.601 MiB copied ETA: Wed Nov  4 14:34:03 2020  48 s  333/605 msgs left
+msg INBOX/962 {1583}          copied to INBOX/272        6.99 msgs/s  513.767 KiB/s 19.602 MiB copied ETA: Wed Nov  4 14:34:03 2020  48 s  332/605 msgs left
+msg INBOX/963 {1577}          copied to INBOX/273        7.00 msgs/s  512.616 KiB/s 19.604 MiB copied ETA: Wed Nov  4 14:34:03 2020  47 s  331/605 msgs left
+msg INBOX/964 {6352}          copied to INBOX/274        7.01 msgs/s  511.530 KiB/s 19.610 MiB copied ETA: Wed Nov  4 14:34:03 2020  47 s  330/605 msgs left
+msg INBOX/965 {932}           copied to INBOX/275        7.01 msgs/s  510.356 KiB/s 19.611 MiB copied ETA: Wed Nov  4 14:34:03 2020  47 s  329/605 msgs left
+msg INBOX/966 {38128}         copied to INBOX/276        7.01 msgs/s  509.402 KiB/s 19.647 MiB copied ETA: Wed Nov  4 14:34:03 2020  47 s  328/605 msgs left
+msg INBOX/967 {102931}        copied to INBOX/277        7.02 msgs/s  510.364 KiB/s 19.745 MiB copied ETA: Wed Nov  4 14:34:03 2020  47 s  327/605 msgs left
+msg INBOX/968 {17129}         copied to INBOX/278        7.02 msgs/s  509.203 KiB/s 19.761 MiB copied ETA: Wed Nov  4 14:34:03 2020  46 s  326/605 msgs left
+msg INBOX/969 {1738}          copied to INBOX/279        7.03 msgs/s  507.914 KiB/s 19.763 MiB copied ETA: Wed Nov  4 14:34:02 2020  46 s  325/605 msgs left
+msg INBOX/970 {103574}        copied to INBOX/280        7.03 msgs/s  508.600 KiB/s 19.862 MiB copied ETA: Wed Nov  4 14:34:02 2020  46 s  324/605 msgs left
+msg INBOX/971 {2908}          copied to INBOX/281        7.04 msgs/s  507.488 KiB/s 19.865 MiB copied ETA: Wed Nov  4 14:34:02 2020  46 s  323/605 msgs left
+msg INBOX/972 {4131}          copied to INBOX/282        7.04 msgs/s  506.240 KiB/s 19.869 MiB copied ETA: Wed Nov  4 14:34:02 2020  46 s  322/605 msgs left
+msg INBOX/974 {43592}         copied to INBOX/283        7.04 msgs/s  505.594 KiB/s 19.910 MiB copied ETA: Wed Nov  4 14:34:02 2020  46 s  321/605 msgs left
+msg INBOX/975 {2653}          copied to INBOX/284        7.05 msgs/s  504.316 KiB/s 19.913 MiB copied ETA: Wed Nov  4 14:34:02 2020  45 s  320/605 msgs left
+msg INBOX/976 {83389}         copied to INBOX/285        7.05 msgs/s  504.617 KiB/s 19.992 MiB copied ETA: Wed Nov  4 14:34:02 2020  45 s  319/605 msgs left
+msg INBOX/985 {7967}          copied to INBOX/286        7.06 msgs/s  503.493 KiB/s 20.000 MiB copied ETA: Wed Nov  4 14:34:02 2020  45 s  318/605 msgs left
+msg INBOX/986 {925}           copied to INBOX/287        7.06 msgs/s  502.233 KiB/s 20.001 MiB copied ETA: Wed Nov  4 14:34:02 2020  45 s  317/605 msgs left
+msg INBOX/987 {925}           copied to INBOX/288        7.07 msgs/s  500.925 KiB/s 20.002 MiB copied ETA: Wed Nov  4 14:34:02 2020  45 s  316/605 msgs left
+msg INBOX/988 {19956}         copied to INBOX/289        7.07 msgs/s  499.953 KiB/s 20.021 MiB copied ETA: Wed Nov  4 14:34:02 2020  45 s  315/605 msgs left
+msg INBOX/989 {1951}          copied to INBOX/290        7.08 msgs/s  498.596 KiB/s 20.022 MiB copied ETA: Wed Nov  4 14:34:02 2020  44 s  314/605 msgs left
+msg INBOX/990 {102746}        copied to INBOX/291        7.08 msgs/s  499.523 KiB/s 20.120 MiB copied ETA: Wed Nov  4 14:34:02 2020  44 s  313/605 msgs left
+msg INBOX/991 {35212}         copied to INBOX/292        7.08 msgs/s  498.538 KiB/s 20.154 MiB copied ETA: Wed Nov  4 14:34:02 2020  44 s  312/605 msgs left
+msg INBOX/992 {3080}          copied to INBOX/293        7.09 msgs/s  497.430 KiB/s 20.157 MiB copied ETA: Wed Nov  4 14:34:02 2020  44 s  311/605 msgs left
+msg INBOX/993 {1288}          copied to INBOX/294        7.09 msgs/s  496.235 KiB/s 20.158 MiB copied ETA: Wed Nov  4 14:34:02 2020  44 s  310/605 msgs left
+msg INBOX/994 {7516}          copied to INBOX/295        7.10 msgs/s  495.318 KiB/s 20.165 MiB copied ETA: Wed Nov  4 14:34:02 2020  44 s  309/605 msgs left
+msg INBOX/995 {102785}        copied to INBOX/296        7.10 msgs/s  496.201 KiB/s 20.263 MiB copied ETA: Wed Nov  4 14:34:02 2020  43 s  308/605 msgs left
+msg INBOX/996 {886}           copied to INBOX/297        7.11 msgs/s  494.968 KiB/s 20.264 MiB copied ETA: Wed Nov  4 14:34:01 2020  43 s  307/605 msgs left
+msg INBOX/997 {574}           copied to INBOX/298        7.11 msgs/s  493.598 KiB/s 20.265 MiB copied ETA: Wed Nov  4 14:34:01 2020  43 s  306/605 msgs left
+msg INBOX/998 {103490}        copied to INBOX/299        7.11 msgs/s  494.370 KiB/s 20.363 MiB copied ETA: Wed Nov  4 14:34:01 2020  43 s  305/605 msgs left
+msg INBOX/999 {2834}          copied to INBOX/300        7.12 msgs/s  493.268 KiB/s 20.366 MiB copied ETA: Wed Nov  4 14:34:01 2020  43 s  304/605 msgs left
+msg INBOX/1000 {569}          copied to INBOX/301        7.13 msgs/s  492.066 KiB/s 20.367 MiB copied ETA: Wed Nov  4 14:34:01 2020  43 s  303/605 msgs left
+msg INBOX/1001 {103759}       copied to INBOX/302        7.13 msgs/s  492.833 KiB/s 20.466 MiB copied ETA: Wed Nov  4 14:34:01 2020  42 s  302/605 msgs left
+msg INBOX/1004 {571}          copied to INBOX/303        7.13 msgs/s  491.799 KiB/s 20.466 MiB copied ETA: Wed Nov  4 14:34:01 2020  42 s  301/605 msgs left
+msg INBOX/1005 {923}          copied to INBOX/304        7.14 msgs/s  490.782 KiB/s 20.467 MiB copied ETA: Wed Nov  4 14:34:01 2020  42 s  300/605 msgs left
+msg INBOX/1006 {103517}       copied to INBOX/305        7.15 msgs/s  491.774 KiB/s 20.566 MiB copied ETA: Wed Nov  4 14:34:01 2020  42 s  299/605 msgs left
+msg INBOX/1007 {103555}       copied to INBOX/306        7.15 msgs/s  492.719 KiB/s 20.665 MiB copied ETA: Wed Nov  4 14:34:01 2020  42 s  298/605 msgs left
+msg INBOX/1008 {103560}       copied to INBOX/307        7.15 msgs/s  493.630 KiB/s 20.763 MiB copied ETA: Wed Nov  4 14:34:01 2020  42 s  297/605 msgs left
+msg INBOX/1011 {14198}        copied to INBOX/308        7.16 msgs/s  492.761 KiB/s 20.777 MiB copied ETA: Wed Nov  4 14:34:01 2020  41 s  296/605 msgs left
+msg INBOX/1014 {943}          copied to INBOX/309        7.16 msgs/s  491.652 KiB/s 20.778 MiB copied ETA: Wed Nov  4 14:34:01 2020  41 s  295/605 msgs left
+msg INBOX/1015 {3853}         copied to INBOX/310        7.17 msgs/s  490.593 KiB/s 20.781 MiB copied ETA: Wed Nov  4 14:34:01 2020  41 s  294/605 msgs left
+msg INBOX/1016 {2580}         copied to INBOX/311        7.18 msgs/s  489.618 KiB/s 20.784 MiB copied ETA: Wed Nov  4 14:34:01 2020  41 s  293/605 msgs left
+ETA: Wed Nov  4 14:34:01 2020  41 s  293/605 msgs left
+Folder     3/6 [Junk]                              -> [Junk]                             
+Host1: folder [Junk] has 0 messages in total (mentioned by SELECT)
+Host1: skipping empty host1 folder [Junk]
+ETA: Wed Nov  4 14:34:01 2020  41 s  293/605 msgs left
+Folder     4/6 [Sent]                              -> [Sent]                             
+Host1: folder [Sent] has 197 messages in total (mentioned by SELECT)
+Host2: folder [Sent] has 0 messages in total (mentioned by SELECT)
+Host2: folder [Sent] permanentflags: 
+Host1: folder [Sent] considering 197 messages
+Host2: folder [Sent] considering 0 messages
+Host1: folder [Sent] selected 197 messages, duplicates 0
+Host2: folder [Sent] selected 0 messages, duplicates 0
+msg Sent/1 {1152231}         copied to Sent/1          6.89 msgs/s  493.220 KiB/s 21.883 MiB copied ETA: Wed Nov  4 14:34:04 2020  42 s  292/605 msgs left
+msg Sent/2 {103844}          copied to Sent/2          6.89 msgs/s  493.866 KiB/s 21.982 MiB copied ETA: Wed Nov  4 14:34:04 2020  42 s  291/605 msgs left
+msg Sent/3 {103713}          copied to Sent/3          6.89 msgs/s  494.436 KiB/s 22.081 MiB copied ETA: Wed Nov  4 14:34:04 2020  42 s  290/605 msgs left
+msg Sent/4 {10517}           copied to Sent/4          6.90 msgs/s  493.691 KiB/s 22.091 MiB copied ETA: Wed Nov  4 14:34:04 2020  42 s  289/605 msgs left
+msg Sent/5 {104636}          copied to Sent/5          6.90 msgs/s  494.307 KiB/s 22.190 MiB copied ETA: Wed Nov  4 14:34:04 2020  42 s  288/605 msgs left
+msg Sent/6 {104375}          copied to Sent/6          6.89 msgs/s  494.868 KiB/s 22.290 MiB copied ETA: Wed Nov  4 14:34:04 2020  42 s  287/605 msgs left
+msg Sent/8 {102744}          copied to Sent/7          6.89 msgs/s  495.505 KiB/s 22.388 MiB copied ETA: Wed Nov  4 14:34:04 2020  41 s  286/605 msgs left
+msg Sent/9 {102623}          copied to Sent/8          6.89 msgs/s  496.060 KiB/s 22.486 MiB copied ETA: Wed Nov  4 14:34:04 2020  41 s  285/605 msgs left
+msg Sent/10 {3200}           copied to Sent/9          6.90 msgs/s  495.166 KiB/s 22.489 MiB copied ETA: Wed Nov  4 14:34:04 2020  41 s  284/605 msgs left
+msg Sent/11 {104742}         copied to Sent/10         6.89 msgs/s  495.001 KiB/s 22.589 MiB copied ETA: Wed Nov  4 14:34:04 2020  41 s  283/605 msgs left
+msg Sent/12 {104874}         copied to Sent/11         6.89 msgs/s  495.308 KiB/s 22.689 MiB copied ETA: Wed Nov  4 14:34:04 2020  41 s  282/605 msgs left
+msg Sent/13 {104657}         copied to Sent/12         6.89 msgs/s  495.924 KiB/s 22.789 MiB copied ETA: Wed Nov  4 14:34:04 2020  41 s  281/605 msgs left
+msg Sent/14 {103719}         copied to Sent/13         6.88 msgs/s  496.407 KiB/s 22.888 MiB copied ETA: Wed Nov  4 14:34:04 2020  41 s  280/605 msgs left
+msg Sent/15 {106534}         copied to Sent/14         6.88 msgs/s  496.965 KiB/s 22.989 MiB copied ETA: Wed Nov  4 14:34:04 2020  41 s  279/605 msgs left
+msg Sent/16 {103762}         copied to Sent/15         6.88 msgs/s  497.556 KiB/s 23.088 MiB copied ETA: Wed Nov  4 14:34:04 2020  40 s  278/605 msgs left
+msg Sent/17 {103827}         copied to Sent/16         6.88 msgs/s  498.136 KiB/s 23.187 MiB copied ETA: Wed Nov  4 14:34:04 2020  40 s  277/605 msgs left
+msg Sent/18 {109291}         copied to Sent/17         6.88 msgs/s  498.784 KiB/s 23.291 MiB copied ETA: Wed Nov  4 14:34:04 2020  40 s  276/605 msgs left
+msg Sent/19 {107773}         copied to Sent/18         6.88 msgs/s  499.340 KiB/s 23.394 MiB copied ETA: Wed Nov  4 14:34:04 2020  40 s  275/605 msgs left
+msg Sent/20 {125545}         copied to Sent/19         6.88 msgs/s  500.294 KiB/s 23.514 MiB copied ETA: Wed Nov  4 14:34:04 2020  40 s  274/605 msgs left
+msg Sent/21 {103715}         copied to Sent/20         6.88 msgs/s  500.874 KiB/s 23.613 MiB copied ETA: Wed Nov  4 14:34:04 2020  40 s  273/605 msgs left
+msg Sent/22 {108687}         copied to Sent/21         6.88 msgs/s  501.515 KiB/s 23.716 MiB copied ETA: Wed Nov  4 14:34:04 2020  40 s  272/605 msgs left
+msg Sent/23 {103809}         copied to Sent/22         6.88 msgs/s  502.097 KiB/s 23.815 MiB copied ETA: Wed Nov  4 14:34:04 2020  39 s  271/605 msgs left
+msg Sent/24 {10874}          copied to Sent/23         6.88 msgs/s  501.345 KiB/s 23.826 MiB copied ETA: Wed Nov  4 14:34:04 2020  39 s  270/605 msgs left
+msg Sent/25 {104762}         copied to Sent/24         6.88 msgs/s  501.812 KiB/s 23.926 MiB copied ETA: Wed Nov  4 14:34:04 2020  39 s  269/605 msgs left
+msg Sent/26 {112410}         copied to Sent/25         6.88 msgs/s  502.540 KiB/s 24.033 MiB copied ETA: Wed Nov  4 14:34:04 2020  39 s  268/605 msgs left
+msg Sent/27 {104874}         copied to Sent/26         6.88 msgs/s  503.082 KiB/s 24.133 MiB copied ETA: Wed Nov  4 14:34:04 2020  39 s  267/605 msgs left
+msg Sent/28 {14505}          copied to Sent/27         6.89 msgs/s  502.338 KiB/s 24.147 MiB copied ETA: Wed Nov  4 14:34:04 2020  39 s  266/605 msgs left
+msg Sent/29 {113587}         copied to Sent/28         6.89 msgs/s  503.025 KiB/s 24.255 MiB copied ETA: Wed Nov  4 14:34:04 2020  38 s  265/605 msgs left
+msg Sent/30 {39527}          copied to Sent/29         6.89 msgs/s  502.309 KiB/s 24.293 MiB copied ETA: Wed Nov  4 14:34:04 2020  38 s  264/605 msgs left
+msg Sent/31 {42386}          copied to Sent/30         6.89 msgs/s  501.647 KiB/s 24.333 MiB copied ETA: Wed Nov  4 14:34:04 2020  38 s  263/605 msgs left
+msg Sent/32 {113565}         copied to Sent/31         6.89 msgs/s  502.409 KiB/s 24.442 MiB copied ETA: Wed Nov  4 14:34:04 2020  38 s  262/605 msgs left
+msg Sent/33 {107628}         copied to Sent/32         6.88 msgs/s  503.026 KiB/s 24.544 MiB copied ETA: Wed Nov  4 14:34:04 2020  38 s  261/605 msgs left
+msg Sent/34 {104686}         copied to Sent/33         6.88 msgs/s  503.582 KiB/s 24.644 MiB copied ETA: Wed Nov  4 14:34:04 2020  38 s  260/605 msgs left
+msg Sent/35 {11580}          copied to Sent/34         6.89 msgs/s  502.867 KiB/s 24.655 MiB copied ETA: Wed Nov  4 14:34:04 2020  38 s  259/605 msgs left
+msg Sent/36 {1946}           copied to Sent/35         6.90 msgs/s  502.011 KiB/s 24.657 MiB copied ETA: Wed Nov  4 14:34:04 2020  37 s  258/605 msgs left
+msg Sent/37 {3298}           copied to Sent/36         6.91 msgs/s  501.100 KiB/s 24.660 MiB copied ETA: Wed Nov  4 14:34:04 2020  37 s  257/605 msgs left
+msg Sent/38 {109670}         copied to Sent/37         6.90 msgs/s  501.702 KiB/s 24.765 MiB copied ETA: Wed Nov  4 14:34:04 2020  37 s  256/605 msgs left
+msg Sent/39 {102670}         copied to Sent/38         6.90 msgs/s  502.223 KiB/s 24.863 MiB copied ETA: Wed Nov  4 14:34:04 2020  37 s  255/605 msgs left
+msg Sent/40 {103840}         copied to Sent/39         6.90 msgs/s  502.723 KiB/s 24.962 MiB copied ETA: Wed Nov  4 14:34:04 2020  37 s  254/605 msgs left
+msg Sent/41 {109670}         copied to Sent/40         6.90 msgs/s  503.318 KiB/s 25.066 MiB copied ETA: Wed Nov  4 14:34:04 2020  37 s  253/605 msgs left
+msg Sent/42 {101602}         copied to Sent/41         6.90 msgs/s  503.753 KiB/s 25.163 MiB copied ETA: Wed Nov  4 14:34:04 2020  37 s  252/605 msgs left
+msg Sent/43 {9807}           copied to Sent/42         6.91 msgs/s  502.983 KiB/s 25.172 MiB copied ETA: Wed Nov  4 14:34:04 2020  36 s  251/605 msgs left
+msg Sent/44 {109680}         copied to Sent/43         6.91 msgs/s  503.625 KiB/s 25.277 MiB copied ETA: Wed Nov  4 14:34:04 2020  36 s  250/605 msgs left
+msg Sent/45 {103678}         copied to Sent/44         6.91 msgs/s  504.148 KiB/s 25.376 MiB copied ETA: Wed Nov  4 14:34:04 2020  36 s  249/605 msgs left
+msg Sent/46 {3548}           copied to Sent/45         6.91 msgs/s  503.347 KiB/s 25.379 MiB copied ETA: Wed Nov  4 14:34:04 2020  36 s  248/605 msgs left
+msg Sent/47 {2293}           copied to Sent/46         6.92 msgs/s  502.491 KiB/s 25.381 MiB copied ETA: Wed Nov  4 14:34:04 2020  36 s  247/605 msgs left
+msg Sent/48 {111284}         copied to Sent/47         6.92 msgs/s  503.169 KiB/s 25.488 MiB copied ETA: Wed Nov  4 14:34:04 2020  36 s  246/605 msgs left
+msg Sent/49 {111288}         copied to Sent/48         6.92 msgs/s  503.847 KiB/s 25.594 MiB copied ETA: Wed Nov  4 14:34:04 2020  35 s  245/605 msgs left
+msg Sent/50 {109658}         copied to Sent/49         6.92 msgs/s  504.471 KiB/s 25.698 MiB copied ETA: Wed Nov  4 14:34:04 2020  35 s  244/605 msgs left
+msg Sent/51 {144883}         copied to Sent/50         6.92 msgs/s  505.779 KiB/s 25.836 MiB copied ETA: Wed Nov  4 14:34:04 2020  35 s  243/605 msgs left
+msg Sent/52 {140010}         copied to Sent/51         6.92 msgs/s  506.939 KiB/s 25.970 MiB copied ETA: Wed Nov  4 14:34:04 2020  35 s  242/605 msgs left
+msg Sent/53 {103629}         copied to Sent/52         6.92 msgs/s  507.437 KiB/s 26.069 MiB copied ETA: Wed Nov  4 14:34:04 2020  35 s  241/605 msgs left
+msg Sent/54 {118996}         copied to Sent/53         6.92 msgs/s  508.159 KiB/s 26.182 MiB copied ETA: Wed Nov  4 14:34:04 2020  35 s  240/605 msgs left
+msg Sent/55 {104623}         copied to Sent/54         6.92 msgs/s  508.674 KiB/s 26.282 MiB copied ETA: Wed Nov  4 14:34:04 2020  35 s  239/605 msgs left
+msg Sent/56 {103703}         copied to Sent/55         6.92 msgs/s  509.111 KiB/s 26.381 MiB copied ETA: Wed Nov  4 14:34:04 2020  34 s  238/605 msgs left
+msg Sent/57 {103516}         copied to Sent/56         6.92 msgs/s  509.576 KiB/s 26.480 MiB copied ETA: Wed Nov  4 14:34:04 2020  34 s  237/605 msgs left
+msg Sent/58 {109662}         copied to Sent/57         6.91 msgs/s  510.093 KiB/s 26.584 MiB copied ETA: Wed Nov  4 14:34:04 2020  34 s  236/605 msgs left
+msg Sent/59 {9701}           copied to Sent/58         6.92 msgs/s  509.355 KiB/s 26.594 MiB copied ETA: Wed Nov  4 14:34:04 2020  34 s  235/605 msgs left
+msg Sent/60 {103870}         copied to Sent/59         6.92 msgs/s  509.811 KiB/s 26.693 MiB copied ETA: Wed Nov  4 14:34:04 2020  34 s  234/605 msgs left
+msg Sent/61 {103600}         copied to Sent/60         6.92 msgs/s  510.273 KiB/s 26.791 MiB copied ETA: Wed Nov  4 14:34:04 2020  34 s  233/605 msgs left
+msg Sent/62 {109662}         copied to Sent/61         6.92 msgs/s  510.878 KiB/s 26.896 MiB copied ETA: Wed Nov  4 14:34:04 2020  34 s  232/605 msgs left
+msg Sent/63 {102888}         copied to Sent/62         6.92 msgs/s  511.326 KiB/s 26.994 MiB copied ETA: Wed Nov  4 14:34:04 2020  33 s  231/605 msgs left
+msg Sent/64 {109638}         copied to Sent/63         6.92 msgs/s  511.927 KiB/s 27.099 MiB copied ETA: Wed Nov  4 14:34:04 2020  33 s  230/605 msgs left
+msg Sent/65 {102796}         copied to Sent/64         6.92 msgs/s  512.379 KiB/s 27.197 MiB copied ETA: Wed Nov  4 14:34:04 2020  33 s  229/605 msgs left
+msg Sent/66 {109658}         copied to Sent/65         6.92 msgs/s  512.926 KiB/s 27.301 MiB copied ETA: Wed Nov  4 14:34:04 2020  33 s  228/605 msgs left
+msg Sent/67 {109634}         copied to Sent/66         6.92 msgs/s  513.468 KiB/s 27.406 MiB copied ETA: Wed Nov  4 14:34:04 2020  33 s  227/605 msgs left
+msg Sent/68 {3197}           copied to Sent/67         6.92 msgs/s  512.672 KiB/s 27.409 MiB copied ETA: Wed Nov  4 14:34:04 2020  33 s  226/605 msgs left
+msg Sent/69 {102729}         copied to Sent/68         6.92 msgs/s  513.164 KiB/s 27.507 MiB copied ETA: Wed Nov  4 14:34:04 2020  33 s  225/605 msgs left
+msg Sent/70 {102550}         copied to Sent/69         6.92 msgs/s  513.634 KiB/s 27.605 MiB copied ETA: Wed Nov  4 14:34:04 2020  32 s  224/605 msgs left
+msg Sent/71 {109638}         copied to Sent/70         6.92 msgs/s  514.163 KiB/s 27.709 MiB copied ETA: Wed Nov  4 14:34:04 2020  32 s  223/605 msgs left
+msg Sent/72 {102996}         copied to Sent/71         6.92 msgs/s  514.622 KiB/s 27.807 MiB copied ETA: Wed Nov  4 14:34:04 2020  32 s  222/605 msgs left
+msg Sent/73 {102634}         copied to Sent/72         6.92 msgs/s  515.065 KiB/s 27.905 MiB copied ETA: Wed Nov  4 14:34:04 2020  32 s  221/605 msgs left
+msg Sent/74 {111290}         copied to Sent/73         6.92 msgs/s  515.614 KiB/s 28.011 MiB copied ETA: Wed Nov  4 14:34:04 2020  32 s  220/605 msgs left
+msg Sent/75 {102724}         copied to Sent/74         6.92 msgs/s  516.080 KiB/s 28.109 MiB copied ETA: Wed Nov  4 14:34:04 2020  32 s  219/605 msgs left
+msg Sent/76 {103763}         copied to Sent/75         6.92 msgs/s  516.399 KiB/s 28.208 MiB copied ETA: Wed Nov  4 14:34:04 2020  32 s  218/605 msgs left
+msg Sent/77 {9734}           copied to Sent/76         6.92 msgs/s  515.654 KiB/s 28.218 MiB copied ETA: Wed Nov  4 14:34:04 2020  31 s  217/605 msgs left
+msg Sent/78 {103869}         copied to Sent/77         6.92 msgs/s  516.109 KiB/s 28.317 MiB copied ETA: Wed Nov  4 14:34:04 2020  31 s  216/605 msgs left
+msg Sent/79 {103859}         copied to Sent/78         6.92 msgs/s  516.077 KiB/s 28.416 MiB copied ETA: Wed Nov  4 14:34:04 2020  31 s  215/605 msgs left
+msg Sent/80 {103707}         copied to Sent/79         6.92 msgs/s  516.461 KiB/s 28.515 MiB copied ETA: Wed Nov  4 14:34:04 2020  31 s  214/605 msgs left
+msg Sent/81 {102724}         copied to Sent/80         6.91 msgs/s  516.828 KiB/s 28.613 MiB copied ETA: Wed Nov  4 14:34:04 2020  31 s  213/605 msgs left
+msg Sent/82 {109462}         copied to Sent/81         6.91 msgs/s  517.321 KiB/s 28.717 MiB copied ETA: Wed Nov  4 14:34:04 2020  31 s  212/605 msgs left
+msg Sent/83 {102730}         copied to Sent/82         6.91 msgs/s  517.757 KiB/s 28.815 MiB copied ETA: Wed Nov  4 14:34:04 2020  31 s  211/605 msgs left
+msg Sent/84 {103025}         copied to Sent/83         6.91 msgs/s  518.186 KiB/s 28.913 MiB copied ETA: Wed Nov  4 14:34:04 2020  30 s  210/605 msgs left
+msg Sent/85 {107638}         copied to Sent/84         6.91 msgs/s  518.608 KiB/s 29.016 MiB copied ETA: Wed Nov  4 14:34:04 2020  30 s  209/605 msgs left
+msg Sent/86 {13394}          copied to Sent/85         6.92 msgs/s  517.994 KiB/s 29.029 MiB copied ETA: Wed Nov  4 14:34:04 2020  30 s  208/605 msgs left
+msg Sent/87 {9963}           copied to Sent/86         6.92 msgs/s  517.333 KiB/s 29.038 MiB copied ETA: Wed Nov  4 14:34:04 2020  30 s  207/605 msgs left
+msg Sent/88 {9773}           copied to Sent/87         6.93 msgs/s  516.622 KiB/s 29.047 MiB copied ETA: Wed Nov  4 14:34:04 2020  30 s  206/605 msgs left
+msg Sent/89 {103986}         copied to Sent/88         6.93 msgs/s  517.089 KiB/s 29.147 MiB copied ETA: Wed Nov  4 14:34:04 2020  30 s  205/605 msgs left
+msg Sent/90 {102861}         copied to Sent/89         6.93 msgs/s  517.538 KiB/s 29.245 MiB copied ETA: Wed Nov  4 14:34:04 2020  29 s  204/605 msgs left
+msg Sent/91 {109662}         copied to Sent/90         6.93 msgs/s  518.059 KiB/s 29.349 MiB copied ETA: Wed Nov  4 14:34:04 2020  29 s  203/605 msgs left
+msg Sent/92 {102884}         copied to Sent/91         6.93 msgs/s  518.488 KiB/s 29.447 MiB copied ETA: Wed Nov  4 14:34:04 2020  29 s  202/605 msgs left
+msg Sent/93 {108548}         copied to Sent/92         6.93 msgs/s  519.030 KiB/s 29.551 MiB copied ETA: Wed Nov  4 14:34:04 2020  29 s  201/605 msgs left
+msg Sent/94 {109638}         copied to Sent/93         6.93 msgs/s  519.412 KiB/s 29.656 MiB copied ETA: Wed Nov  4 14:34:04 2020  29 s  200/605 msgs left
+msg Sent/95 {102720}         copied to Sent/94         6.93 msgs/s  519.776 KiB/s 29.753 MiB copied ETA: Wed Nov  4 14:34:04 2020  29 s  199/605 msgs left
+msg Sent/96 {103661}         copied to Sent/95         6.93 msgs/s  520.174 KiB/s 29.852 MiB copied ETA: Wed Nov  4 14:34:04 2020  29 s  198/605 msgs left
+msg Sent/97 {2425}           copied to Sent/96         6.93 msgs/s  519.364 KiB/s 29.855 MiB copied ETA: Wed Nov  4 14:34:04 2020  28 s  197/605 msgs left
+msg Sent/98 {102763}         copied to Sent/97         6.93 msgs/s  519.719 KiB/s 29.953 MiB copied ETA: Wed Nov  4 14:34:04 2020  28 s  196/605 msgs left
+msg Sent/99 {103693}         copied to Sent/98         6.93 msgs/s  520.168 KiB/s 30.052 MiB copied ETA: Wed Nov  4 14:34:04 2020  28 s  195/605 msgs left
+msg Sent/100 {102801}        copied to Sent/99         6.93 msgs/s  520.575 KiB/s 30.150 MiB copied ETA: Wed Nov  4 14:34:04 2020  28 s  194/605 msgs left
+msg Sent/102 {124688}        copied to Sent/100        6.93 msgs/s  521.244 KiB/s 30.268 MiB copied ETA: Wed Nov  4 14:34:04 2020  28 s  193/605 msgs left
+msg Sent/103 {103732}        copied to Sent/101        6.93 msgs/s  521.679 KiB/s 30.367 MiB copied ETA: Wed Nov  4 14:34:04 2020  28 s  192/605 msgs left
+msg Sent/104 {124692}        copied to Sent/102        6.93 msgs/s  522.362 KiB/s 30.486 MiB copied ETA: Wed Nov  4 14:34:04 2020  28 s  191/605 msgs left
+msg Sent/105 {103736}        copied to Sent/103        6.93 msgs/s  522.693 KiB/s 30.585 MiB copied ETA: Wed Nov  4 14:34:04 2020  27 s  190/605 msgs left
+msg Sent/106 {102734}        copied to Sent/104        6.93 msgs/s  523.070 KiB/s 30.683 MiB copied ETA: Wed Nov  4 14:34:04 2020  27 s  189/605 msgs left
+msg Sent/107 {102738}        copied to Sent/105        6.92 msgs/s  523.437 KiB/s 30.781 MiB copied ETA: Wed Nov  4 14:34:04 2020  27 s  188/605 msgs left
+msg Sent/108 {109634}        copied to Sent/106        6.92 msgs/s  523.884 KiB/s 30.886 MiB copied ETA: Wed Nov  4 14:34:04 2020  27 s  187/605 msgs left
+msg Sent/109 {2464}          copied to Sent/107        6.93 msgs/s  523.074 KiB/s 30.888 MiB copied ETA: Wed Nov  4 14:34:04 2020  27 s  186/605 msgs left
+msg Sent/110 {2468}          copied to Sent/108        6.93 msgs/s  522.262 KiB/s 30.890 MiB copied ETA: Wed Nov  4 14:34:04 2020  27 s  185/605 msgs left
+msg Sent/111 {102738}        copied to Sent/109        6.93 msgs/s  522.675 KiB/s 30.988 MiB copied ETA: Wed Nov  4 14:34:04 2020  27 s  184/605 msgs left
+msg Sent/112 {102789}        copied to Sent/110        6.93 msgs/s  523.070 KiB/s 31.086 MiB copied ETA: Wed Nov  4 14:34:04 2020  26 s  183/605 msgs left
+msg Sent/113 {102793}        copied to Sent/111        6.93 msgs/s  523.429 KiB/s 31.185 MiB copied ETA: Wed Nov  4 14:34:04 2020  26 s  182/605 msgs left
+msg Sent/114 {2385}          copied to Sent/112        6.94 msgs/s  522.644 KiB/s 31.187 MiB copied ETA: Wed Nov  4 14:34:04 2020  26 s  181/605 msgs left
+msg Sent/115 {103857}        copied to Sent/113        6.94 msgs/s  522.979 KiB/s 31.286 MiB copied ETA: Wed Nov  4 14:34:04 2020  26 s  180/605 msgs left
+msg Sent/116 {103861}        copied to Sent/114        6.94 msgs/s  523.353 KiB/s 31.385 MiB copied ETA: Wed Nov  4 14:34:04 2020  26 s  179/605 msgs left
+msg Sent/117 {2454}          copied to Sent/115        6.94 msgs/s  522.518 KiB/s 31.387 MiB copied ETA: Wed Nov  4 14:34:03 2020  26 s  178/605 msgs left
+msg Sent/118 {152204}        copied to Sent/116        6.94 msgs/s  523.677 KiB/s 31.532 MiB copied ETA: Wed Nov  4 14:34:03 2020  25 s  177/605 msgs left
+msg Sent/119 {2562}          copied to Sent/117        6.95 msgs/s  522.883 KiB/s 31.535 MiB copied ETA: Wed Nov  4 14:34:03 2020  25 s  176/605 msgs left
+msg Sent/120 {2604}          copied to Sent/118        6.95 msgs/s  522.126 KiB/s 31.537 MiB copied ETA: Wed Nov  4 14:34:03 2020  25 s  175/605 msgs left
+msg Sent/121 {107595}        copied to Sent/119        6.95 msgs/s  522.553 KiB/s 31.640 MiB copied ETA: Wed Nov  4 14:34:03 2020  25 s  174/605 msgs left
+msg Sent/122 {107591}        copied to Sent/120        6.95 msgs/s  523.022 KiB/s 31.743 MiB copied ETA: Wed Nov  4 14:34:03 2020  25 s  173/605 msgs left
+msg Sent/123 {270464}        copied to Sent/121        6.95 msgs/s  525.802 KiB/s 32.000 MiB copied ETA: Wed Nov  4 14:34:03 2020  25 s  172/605 msgs left
+msg Sent/124 {111200}        copied to Sent/122        6.95 msgs/s  526.318 KiB/s 32.107 MiB copied ETA: Wed Nov  4 14:34:03 2020  25 s  171/605 msgs left
+msg Sent/125 {111204}        copied to Sent/123        6.95 msgs/s  526.812 KiB/s 32.213 MiB copied ETA: Wed Nov  4 14:34:03 2020  24 s  170/605 msgs left
+msg Sent/126 {107598}        copied to Sent/124        6.95 msgs/s  527.201 KiB/s 32.315 MiB copied ETA: Wed Nov  4 14:34:03 2020  24 s  169/605 msgs left
+msg Sent/127 {107602}        copied to Sent/125        6.95 msgs/s  527.670 KiB/s 32.418 MiB copied ETA: Wed Nov  4 14:34:03 2020  24 s  168/605 msgs left
+msg Sent/128 {103729}        copied to Sent/126        6.95 msgs/s  528.077 KiB/s 32.517 MiB copied ETA: Wed Nov  4 14:34:03 2020  24 s  167/605 msgs left
+msg Sent/129 {103733}        copied to Sent/127        6.95 msgs/s  528.413 KiB/s 32.616 MiB copied ETA: Wed Nov  4 14:34:03 2020  24 s  166/605 msgs left
+msg Sent/130 {103603}        copied to Sent/128        6.94 msgs/s  528.749 KiB/s 32.714 MiB copied ETA: Wed Nov  4 14:34:03 2020  24 s  165/605 msgs left
+msg Sent/131 {103607}        copied to Sent/129        6.94 msgs/s  528.993 KiB/s 32.813 MiB copied ETA: Wed Nov  4 14:34:03 2020  24 s  164/605 msgs left
+msg Sent/132 {104582}        copied to Sent/130        6.94 msgs/s  529.329 KiB/s 32.913 MiB copied ETA: Wed Nov  4 14:34:03 2020  23 s  163/605 msgs left
+msg Sent/133 {109646}        copied to Sent/131        6.94 msgs/s  529.807 KiB/s 33.018 MiB copied ETA: Wed Nov  4 14:34:03 2020  23 s  162/605 msgs left
+msg Sent/134 {2628}          copied to Sent/132        6.95 msgs/s  529.036 KiB/s 33.020 MiB copied ETA: Wed Nov  4 14:34:03 2020  23 s  161/605 msgs left
+msg Sent/135 {103693}        copied to Sent/133        6.95 msgs/s  529.618 KiB/s 33.119 MiB copied ETA: Wed Nov  4 14:34:03 2020  23 s  160/605 msgs left
+msg Sent/136 {103697}        copied to Sent/134        6.95 msgs/s  529.946 KiB/s 33.218 MiB copied ETA: Wed Nov  4 14:34:03 2020  23 s  159/605 msgs left
+msg Sent/137 {103668}        copied to Sent/135        6.95 msgs/s  530.325 KiB/s 33.317 MiB copied ETA: Wed Nov  4 14:34:03 2020  23 s  158/605 msgs left
+msg Sent/138 {108491}        copied to Sent/136        6.95 msgs/s  530.718 KiB/s 33.420 MiB copied ETA: Wed Nov  4 14:34:03 2020  23 s  157/605 msgs left
+msg Sent/139 {103672}        copied to Sent/137        6.95 msgs/s  531.098 KiB/s 33.519 MiB copied ETA: Wed Nov  4 14:34:03 2020  22 s  156/605 msgs left
+msg Sent/140 {108495}        copied to Sent/138        6.95 msgs/s  531.553 KiB/s 33.623 MiB copied ETA: Wed Nov  4 14:34:03 2020  22 s  155/605 msgs left
+msg Sent/141 {102725}        copied to Sent/139        6.95 msgs/s  531.847 KiB/s 33.720 MiB copied ETA: Wed Nov  4 14:34:03 2020  22 s  154/605 msgs left
+msg Sent/142 {102729}        copied to Sent/140        6.95 msgs/s  532.145 KiB/s 33.818 MiB copied ETA: Wed Nov  4 14:34:03 2020  22 s  153/605 msgs left
+msg Sent/143 {102740}        copied to Sent/141        6.95 msgs/s  532.516 KiB/s 33.916 MiB copied ETA: Wed Nov  4 14:34:03 2020  22 s  152/605 msgs left
+msg Sent/144 {102744}        copied to Sent/142        6.94 msgs/s  532.802 KiB/s 34.014 MiB copied ETA: Wed Nov  4 14:34:03 2020  22 s  151/605 msgs left
+msg Sent/145 {102699}        copied to Sent/143        6.94 msgs/s  533.105 KiB/s 34.112 MiB copied ETA: Wed Nov  4 14:34:03 2020  22 s  150/605 msgs left
+msg Sent/146 {106155}        copied to Sent/144        6.94 msgs/s  533.495 KiB/s 34.214 MiB copied ETA: Wed Nov  4 14:34:03 2020  21 s  149/605 msgs left
+msg Sent/147 {13377}         copied to Sent/145        6.95 msgs/s  532.892 KiB/s 34.226 MiB copied ETA: Wed Nov  4 14:34:03 2020  21 s  148/605 msgs left
+msg Sent/148 {116012}        copied to Sent/146        6.95 msgs/s  533.447 KiB/s 34.337 MiB copied ETA: Wed Nov  4 14:34:03 2020  21 s  147/605 msgs left
+msg Sent/149 {103835}        copied to Sent/147        6.95 msgs/s  533.795 KiB/s 34.436 MiB copied ETA: Wed Nov  4 14:34:03 2020  21 s  146/605 msgs left
+msg Sent/150 {17449}         copied to Sent/148        6.95 msgs/s  533.054 KiB/s 34.453 MiB copied ETA: Wed Nov  4 14:34:03 2020  21 s  145/605 msgs left
+msg Sent/151 {17172}         copied to Sent/149        6.95 msgs/s  532.352 KiB/s 34.469 MiB copied ETA: Wed Nov  4 14:34:03 2020  21 s  144/605 msgs left
+msg Sent/152 {102746}        copied to Sent/150        6.95 msgs/s  532.647 KiB/s 34.567 MiB copied ETA: Wed Nov  4 14:34:03 2020  21 s  143/605 msgs left
+msg Sent/153 {1761}          copied to Sent/151        6.96 msgs/s  531.896 KiB/s 34.569 MiB copied ETA: Wed Nov  4 14:34:03 2020  20 s  142/605 msgs left
+msg Sent/154 {112188}        copied to Sent/152        6.96 msgs/s  532.346 KiB/s 34.676 MiB copied ETA: Wed Nov  4 14:34:03 2020  20 s  141/605 msgs left
+msg Sent/155 {103187}        copied to Sent/153        6.96 msgs/s  532.679 KiB/s 34.774 MiB copied ETA: Wed Nov  4 14:34:03 2020  20 s  140/605 msgs left
+msg Sent/156 {103649}        copied to Sent/154        6.96 msgs/s  533.022 KiB/s 34.873 MiB copied ETA: Wed Nov  4 14:34:03 2020  20 s  139/605 msgs left
+msg Sent/157 {102780}        copied to Sent/155        6.95 msgs/s  533.316 KiB/s 34.971 MiB copied ETA: Wed Nov  4 14:34:03 2020  20 s  138/605 msgs left
+msg Sent/158 {103792}        copied to Sent/156        6.95 msgs/s  533.652 KiB/s 35.070 MiB copied ETA: Wed Nov  4 14:34:03 2020  20 s  137/605 msgs left
+msg Sent/159 {102842}        copied to Sent/157        6.95 msgs/s  533.937 KiB/s 35.168 MiB copied ETA: Wed Nov  4 14:34:03 2020  20 s  136/605 msgs left
+msg Sent/160 {2357}          copied to Sent/158        6.96 msgs/s  533.248 KiB/s 35.170 MiB copied ETA: Wed Nov  4 14:34:03 2020  19 s  135/605 msgs left
+msg Sent/161 {102699}        copied to Sent/159        6.96 msgs/s  533.492 KiB/s 35.268 MiB copied ETA: Wed Nov  4 14:34:03 2020  19 s  134/605 msgs left
+msg Sent/162 {13163}         copied to Sent/160        6.96 msgs/s  532.901 KiB/s 35.281 MiB copied ETA: Wed Nov  4 14:34:03 2020  19 s  133/605 msgs left
+msg Sent/163 {103712}        copied to Sent/161        6.96 msgs/s  533.189 KiB/s 35.380 MiB copied ETA: Wed Nov  4 14:34:03 2020  19 s  132/605 msgs left
+msg Sent/164 {2417}          copied to Sent/162        6.96 msgs/s  532.348 KiB/s 35.382 MiB copied ETA: Wed Nov  4 14:34:03 2020  19 s  131/605 msgs left
+msg Sent/165 {114583}        copied to Sent/163        6.96 msgs/s  532.799 KiB/s 35.491 MiB copied ETA: Wed Nov  4 14:34:03 2020  19 s  130/605 msgs left
+msg Sent/166 {102787}        copied to Sent/164        6.96 msgs/s  533.078 KiB/s 35.589 MiB copied ETA: Wed Nov  4 14:34:03 2020  19 s  129/605 msgs left
+msg Sent/167 {107654}        copied to Sent/165        6.96 msgs/s  533.468 KiB/s 35.692 MiB copied ETA: Wed Nov  4 14:34:03 2020  18 s  128/605 msgs left
+msg Sent/168 {110399}        copied to Sent/166        6.96 msgs/s  533.914 KiB/s 35.797 MiB copied ETA: Wed Nov  4 14:34:03 2020  18 s  127/605 msgs left
+msg Sent/169 {103776}        copied to Sent/167        6.96 msgs/s  534.251 KiB/s 35.896 MiB copied ETA: Wed Nov  4 14:34:03 2020  18 s  126/605 msgs left
+msg Sent/170 {2866}          copied to Sent/168        6.97 msgs/s  533.560 KiB/s 35.899 MiB copied ETA: Wed Nov  4 14:34:03 2020  18 s  125/605 msgs left
+msg Sent/171 {11467}         copied to Sent/169        6.97 msgs/s  533.007 KiB/s 35.910 MiB copied ETA: Wed Nov  4 14:34:03 2020  18 s  124/605 msgs left
+msg Sent/172 {102915}        copied to Sent/170        6.97 msgs/s  533.308 KiB/s 36.008 MiB copied ETA: Wed Nov  4 14:34:03 2020  18 s  123/605 msgs left
+msg Sent/173 {107843}        copied to Sent/171        6.97 msgs/s  533.714 KiB/s 36.111 MiB copied ETA: Wed Nov  4 14:34:03 2020  18 s  122/605 msgs left
+msg Sent/174 {106654}        copied to Sent/172        6.97 msgs/s  534.021 KiB/s 36.213 MiB copied ETA: Wed Nov  4 14:34:03 2020  17 s  121/605 msgs left
+msg Sent/175 {2326}          copied to Sent/173        6.98 msgs/s  533.331 KiB/s 36.215 MiB copied ETA: Wed Nov  4 14:34:03 2020  17 s  120/605 msgs left
+msg Sent/176 {13281}         copied to Sent/174        6.98 msgs/s  532.796 KiB/s 36.227 MiB copied ETA: Wed Nov  4 14:34:03 2020  17 s  119/605 msgs left
+msg Sent/177 {102721}        copied to Sent/175        6.98 msgs/s  533.106 KiB/s 36.325 MiB copied ETA: Wed Nov  4 14:34:03 2020  17 s  118/605 msgs left
+msg Sent/178 {103701}        copied to Sent/176        6.98 msgs/s  533.543 KiB/s 36.424 MiB copied ETA: Wed Nov  4 14:34:03 2020  17 s  117/605 msgs left
+msg Sent/179 {3352}          copied to Sent/177        6.98 msgs/s  532.746 KiB/s 36.428 MiB copied ETA: Wed Nov  4 14:34:03 2020  17 s  116/605 msgs left
+msg Sent/180 {4094}          copied to Sent/178        6.99 msgs/s  531.977 KiB/s 36.431 MiB copied ETA: Wed Nov  4 14:34:03 2020  16 s  115/605 msgs left
+msg Sent/181 {2779}          copied to Sent/179        6.99 msgs/s  531.147 KiB/s 36.434 MiB copied ETA: Wed Nov  4 14:34:03 2020  16 s  114/605 msgs left
+msg Sent/182 {103739}        copied to Sent/180        6.99 msgs/s  531.511 KiB/s 36.533 MiB copied ETA: Wed Nov  4 14:34:03 2020  16 s  113/605 msgs left
+msg Sent/183 {4827}          copied to Sent/181        6.99 msgs/s  530.653 KiB/s 36.538 MiB copied ETA: Wed Nov  4 14:34:03 2020  16 s  112/605 msgs left
+msg Sent/184 {107635}        copied to Sent/182        6.99 msgs/s  531.087 KiB/s 36.640 MiB copied ETA: Wed Nov  4 14:34:03 2020  16 s  111/605 msgs left
+msg Sent/185 {103631}        copied to Sent/183        6.99 msgs/s  531.470 KiB/s 36.739 MiB copied ETA: Wed Nov  4 14:34:03 2020  16 s  110/605 msgs left
+msg Sent/186 {103720}        copied to Sent/184        6.99 msgs/s  531.879 KiB/s 36.838 MiB copied ETA: Wed Nov  4 14:34:03 2020  16 s  109/605 msgs left
+msg Sent/187 {102736}        copied to Sent/185        6.99 msgs/s  532.274 KiB/s 36.936 MiB copied ETA: Wed Nov  4 14:34:03 2020  15 s  108/605 msgs left
+msg Sent/188 {103694}        copied to Sent/186        6.99 msgs/s  532.637 KiB/s 37.035 MiB copied ETA: Wed Nov  4 14:34:03 2020  15 s  107/605 msgs left
+msg Sent/189 {102784}        copied to Sent/187        7.00 msgs/s  533.072 KiB/s 37.133 MiB copied ETA: Wed Nov  4 14:34:03 2020  15 s  106/605 msgs left
+msg Sent/190 {103831}        copied to Sent/188        7.00 msgs/s  533.530 KiB/s 37.232 MiB copied ETA: Wed Nov  4 14:34:03 2020  15 s  105/605 msgs left
+msg Sent/191 {815}           copied to Sent/189        7.00 msgs/s  532.831 KiB/s 37.233 MiB copied ETA: Wed Nov  4 14:34:03 2020  15 s  104/605 msgs left
+msg Sent/192 {102812}        copied to Sent/190        7.00 msgs/s  533.316 KiB/s 37.331 MiB copied ETA: Wed Nov  4 14:34:03 2020  15 s  103/605 msgs left
+msg Sent/193 {810}           copied to Sent/191        7.01 msgs/s  532.548 KiB/s 37.332 MiB copied ETA: Wed Nov  4 14:34:03 2020  15 s  102/605 msgs left
+msg Sent/194 {4218}          copied to Sent/192        7.01 msgs/s  531.923 KiB/s 37.336 MiB copied ETA: Wed Nov  4 14:34:03 2020  14 s  101/605 msgs left
+msg Sent/195 {16329}         copied to Sent/193        7.02 msgs/s  531.384 KiB/s 37.351 MiB copied ETA: Wed Nov  4 14:34:03 2020  14 s  100/605 msgs left
+msg Sent/196 {45220}         copied to Sent/194        7.02 msgs/s  530.933 KiB/s 37.394 MiB copied ETA: Wed Nov  4 14:34:03 2020  14 s  99/605 msgs left
+msg Sent/197 {102704}        copied to Sent/195        7.02 msgs/s  531.294 KiB/s 37.492 MiB copied ETA: Wed Nov  4 14:34:03 2020  14 s  98/605 msgs left
+msg Sent/198 {102779}        copied to Sent/196        7.02 msgs/s  531.721 KiB/s 37.590 MiB copied ETA: Wed Nov  4 14:34:03 2020  14 s  97/605 msgs left
+msg Sent/199 {103775}        copied to Sent/197        7.02 msgs/s  531.987 KiB/s 37.689 MiB copied ETA: Wed Nov  4 14:34:03 2020  14 s  96/605 msgs left
+ETA: Wed Nov  4 14:34:03 2020  14 s  96/605 msgs left
+Folder     5/6 [Spam]                              -> [Spam]                             
+Host1: folder [Spam] has 0 messages in total (mentioned by SELECT)
+Host1: skipping empty host1 folder [Spam]
+ETA: Wed Nov  4 14:34:03 2020  14 s  96/605 msgs left
+Folder     6/6 [Trash]                             -> [Trash]                            
+Host1: folder [Trash] has 96 messages in total (mentioned by SELECT)
+Host2: folder [Trash] has 0 messages in total (mentioned by SELECT)
+Host2: folder [Trash] permanentflags: 
+Host1: folder [Trash] considering 96 messages
+Host2: folder [Trash] considering 0 messages
+Host1: folder [Trash] selected 96 messages, duplicates 0
+Host2: folder [Trash] selected 0 messages, duplicates 0
+msg Trash/619 {884}           copied to Trash/1          6.97 msgs/s  527.836 KiB/s 37.690 MiB copied ETA: Wed Nov  4 14:34:03 2020  14 s  95/605 msgs left
+msg Trash/620 {884}           copied to Trash/2          6.98 msgs/s  527.045 KiB/s 37.691 MiB copied ETA: Wed Nov  4 14:34:03 2020  13 s  94/605 msgs left
+msg Trash/621 {882}           copied to Trash/3          6.98 msgs/s  526.333 KiB/s 37.692 MiB copied ETA: Wed Nov  4 14:34:03 2020  13 s  93/605 msgs left
+msg Trash/622 {894}           copied to Trash/4          6.99 msgs/s  525.623 KiB/s 37.693 MiB copied ETA: Wed Nov  4 14:34:03 2020  13 s  92/605 msgs left
+msg Trash/623 {932}           copied to Trash/5          6.99 msgs/s  524.861 KiB/s 37.693 MiB copied ETA: Wed Nov  4 14:34:03 2020  13 s  91/605 msgs left
+msg Trash/624 {7237}          copied to Trash/6          6.99 msgs/s  524.271 KiB/s 37.700 MiB copied ETA: Wed Nov  4 14:34:03 2020  13 s  90/605 msgs left
+msg Trash/625 {917}           copied to Trash/7          7.00 msgs/s  523.517 KiB/s 37.701 MiB copied ETA: Wed Nov  4 14:34:03 2020  13 s  89/605 msgs left
+msg Trash/626 {937}           copied to Trash/8          7.00 msgs/s  522.762 KiB/s 37.702 MiB copied ETA: Wed Nov  4 14:34:03 2020  13 s  88/605 msgs left
+msg Trash/627 {949}           copied to Trash/9          7.00 msgs/s  521.976 KiB/s 37.703 MiB copied ETA: Wed Nov  4 14:34:03 2020  12 s  87/605 msgs left
+msg Trash/628 {34890}         copied to Trash/10         7.00 msgs/s  521.413 KiB/s 37.736 MiB copied ETA: Wed Nov  4 14:34:03 2020  12 s  86/605 msgs left
+msg Trash/629 {929}           copied to Trash/11         7.01 msgs/s  520.685 KiB/s 37.737 MiB copied ETA: Wed Nov  4 14:34:03 2020  12 s  85/605 msgs left
+msg Trash/630 {1314}          copied to Trash/12         7.01 msgs/s  519.966 KiB/s 37.738 MiB copied ETA: Wed Nov  4 14:34:03 2020  12 s  84/605 msgs left
+msg Trash/631 {1123}          copied to Trash/13         7.01 msgs/s  519.201 KiB/s 37.739 MiB copied ETA: Wed Nov  4 14:34:03 2020  12 s  83/605 msgs left
+msg Trash/632 {1111}          copied to Trash/14         7.02 msgs/s  518.438 KiB/s 37.741 MiB copied ETA: Wed Nov  4 14:34:03 2020  12 s  82/605 msgs left
+msg Trash/633 {1115}          copied to Trash/15         7.02 msgs/s  517.727 KiB/s 37.742 MiB copied ETA: Wed Nov  4 14:34:03 2020  12 s  81/605 msgs left
+msg Trash/634 {1100}          copied to Trash/16         7.02 msgs/s  517.041 KiB/s 37.743 MiB copied ETA: Wed Nov  4 14:34:02 2020  11 s  80/605 msgs left
+msg Trash/635 {1015}          copied to Trash/17         7.03 msgs/s  516.339 KiB/s 37.744 MiB copied ETA: Wed Nov  4 14:34:02 2020  11 s  79/605 msgs left
+msg Trash/636 {1015}          copied to Trash/18         7.03 msgs/s  515.526 KiB/s 37.745 MiB copied ETA: Wed Nov  4 14:34:02 2020  11 s  78/605 msgs left
+msg Trash/637 {3282}          copied to Trash/19         7.03 msgs/s  514.866 KiB/s 37.748 MiB copied ETA: Wed Nov  4 14:34:02 2020  11 s  77/605 msgs left
+msg Trash/638 {2220}          copied to Trash/20         7.04 msgs/s  514.098 KiB/s 37.750 MiB copied ETA: Wed Nov  4 14:34:02 2020  11 s  76/605 msgs left
+msg Trash/639 {1103}          copied to Trash/21         7.04 msgs/s  513.420 KiB/s 37.751 MiB copied ETA: Wed Nov  4 14:34:02 2020  11 s  75/605 msgs left
+msg Trash/640 {1106}          copied to Trash/22         7.04 msgs/s  512.728 KiB/s 37.752 MiB copied ETA: Wed Nov  4 14:34:02 2020  11 s  74/605 msgs left
+msg Trash/641 {1951}          copied to Trash/23         7.05 msgs/s  512.023 KiB/s 37.754 MiB copied ETA: Wed Nov  4 14:34:02 2020  10 s  73/605 msgs left
+msg Trash/642 {2326}          copied to Trash/24         7.05 msgs/s  511.356 KiB/s 37.756 MiB copied ETA: Wed Nov  4 14:34:02 2020  10 s  72/605 msgs left
+msg Trash/643 {1850}          copied to Trash/25         7.05 msgs/s  510.636 KiB/s 37.758 MiB copied ETA: Wed Nov  4 14:34:02 2020  10 s  71/605 msgs left
+msg Trash/644 {918}           copied to Trash/26         7.06 msgs/s  509.997 KiB/s 37.759 MiB copied ETA: Wed Nov  4 14:34:02 2020  10 s  70/605 msgs left
+msg Trash/645 {2496}          copied to Trash/27         7.06 msgs/s  509.378 KiB/s 37.761 MiB copied ETA: Wed Nov  4 14:34:02 2020  10 s  69/605 msgs left
+msg Trash/646 {1114}          copied to Trash/28         7.07 msgs/s  508.747 KiB/s 37.762 MiB copied ETA: Wed Nov  4 14:34:02 2020  10 s  68/605 msgs left
+msg Trash/647 {1127}          copied to Trash/29         7.07 msgs/s  508.019 KiB/s 37.763 MiB copied ETA: Wed Nov  4 14:34:02 2020  9 s  67/605 msgs left
+msg Trash/648 {1127}          copied to Trash/30         7.07 msgs/s  507.345 KiB/s 37.764 MiB copied ETA: Wed Nov  4 14:34:02 2020  9 s  66/605 msgs left
+msg Trash/649 {1110}          copied to Trash/31         7.08 msgs/s  506.758 KiB/s 37.765 MiB copied ETA: Wed Nov  4 14:34:02 2020  9 s  65/605 msgs left
+msg Trash/650 {934}           copied to Trash/32         7.08 msgs/s  506.117 KiB/s 37.766 MiB copied ETA: Wed Nov  4 14:34:02 2020  9 s  64/605 msgs left
+msg Trash/651 {1149}          copied to Trash/33         7.08 msgs/s  505.423 KiB/s 37.767 MiB copied ETA: Wed Nov  4 14:34:02 2020  9 s  63/605 msgs left
+msg Trash/652 {3186}          copied to Trash/34         7.09 msgs/s  504.753 KiB/s 37.770 MiB copied ETA: Wed Nov  4 14:34:02 2020  9 s  62/605 msgs left
+msg Trash/653 {1688}          copied to Trash/35         7.09 msgs/s  504.100 KiB/s 37.772 MiB copied ETA: Wed Nov  4 14:34:02 2020  9 s  61/605 msgs left
+msg Trash/654 {2443}          copied to Trash/36         7.09 msgs/s  503.531 KiB/s 37.774 MiB copied ETA: Wed Nov  4 14:34:02 2020  8 s  60/605 msgs left
+msg Trash/655 {3168}          copied to Trash/37         7.10 msgs/s  502.952 KiB/s 37.777 MiB copied ETA: Wed Nov  4 14:34:02 2020  8 s  59/605 msgs left
+msg Trash/656 {907}           copied to Trash/38         7.10 msgs/s  502.357 KiB/s 37.778 MiB copied ETA: Wed Nov  4 14:34:02 2020  8 s  58/605 msgs left
+msg Trash/657 {1212}          copied to Trash/39         7.11 msgs/s  501.680 KiB/s 37.779 MiB copied ETA: Wed Nov  4 14:34:01 2020  8 s  57/605 msgs left
+msg Trash/658 {1342}          copied to Trash/40         7.11 msgs/s  500.977 KiB/s 37.781 MiB copied ETA: Wed Nov  4 14:34:01 2020  8 s  56/605 msgs left
+msg Trash/659 {1230}          copied to Trash/41         7.11 msgs/s  500.308 KiB/s 37.782 MiB copied ETA: Wed Nov  4 14:34:01 2020  8 s  55/605 msgs left
+msg Trash/660 {954}           copied to Trash/42         7.12 msgs/s  499.673 KiB/s 37.783 MiB copied ETA: Wed Nov  4 14:34:01 2020  8 s  54/605 msgs left
+msg Trash/661 {1768}          copied to Trash/43         7.12 msgs/s  499.055 KiB/s 37.784 MiB copied ETA: Wed Nov  4 14:34:01 2020  7 s  53/605 msgs left
+msg Trash/662 {982}           copied to Trash/44         7.12 msgs/s  498.310 KiB/s 37.785 MiB copied ETA: Wed Nov  4 14:34:01 2020  7 s  52/605 msgs left
+msg Trash/663 {2026}          copied to Trash/45         7.12 msgs/s  497.612 KiB/s 37.787 MiB copied ETA: Wed Nov  4 14:34:01 2020  7 s  51/605 msgs left
+msg Trash/664 {1323}          copied to Trash/46         7.13 msgs/s  497.030 KiB/s 37.788 MiB copied ETA: Wed Nov  4 14:34:01 2020  7 s  50/605 msgs left
+msg Trash/665 {1414}          copied to Trash/47         7.13 msgs/s  496.364 KiB/s 37.790 MiB copied ETA: Wed Nov  4 14:34:01 2020  7 s  49/605 msgs left
+msg Trash/666 {1116}          copied to Trash/48         7.14 msgs/s  495.793 KiB/s 37.791 MiB copied ETA: Wed Nov  4 14:34:01 2020  7 s  48/605 msgs left
+msg Trash/667 {3855}          copied to Trash/49         7.14 msgs/s  495.203 KiB/s 37.795 MiB copied ETA: Wed Nov  4 14:34:01 2020  7 s  47/605 msgs left
+msg Trash/668 {1236}          copied to Trash/50         7.14 msgs/s  494.612 KiB/s 37.796 MiB copied ETA: Wed Nov  4 14:34:01 2020  6 s  46/605 msgs left
+msg Trash/669 {2612}          copied to Trash/51         7.15 msgs/s  494.042 KiB/s 37.798 MiB copied ETA: Wed Nov  4 14:34:01 2020  6 s  45/605 msgs left
+msg Trash/670 {1177}          copied to Trash/52         7.15 msgs/s  493.413 KiB/s 37.799 MiB copied ETA: Wed Nov  4 14:34:01 2020  6 s  44/605 msgs left
+msg Trash/671 {1899}          copied to Trash/53         7.15 msgs/s  492.797 KiB/s 37.801 MiB copied ETA: Wed Nov  4 14:34:01 2020  6 s  43/605 msgs left
+msg Trash/672 {913}           copied to Trash/54         7.16 msgs/s  492.233 KiB/s 37.802 MiB copied ETA: Wed Nov  4 14:34:01 2020  6 s  42/605 msgs left
+msg Trash/673 {931}           copied to Trash/55         7.16 msgs/s  491.598 KiB/s 37.803 MiB copied ETA: Wed Nov  4 14:34:01 2020  6 s  41/605 msgs left
+msg Trash/674 {2250}          copied to Trash/56         7.17 msgs/s  490.990 KiB/s 37.805 MiB copied ETA: Wed Nov  4 14:34:01 2020  6 s  40/605 msgs left
+msg Trash/675 {945}           copied to Trash/57         7.17 msgs/s  490.394 KiB/s 37.806 MiB copied ETA: Wed Nov  4 14:34:01 2020  5 s  39/605 msgs left
+msg Trash/676 {921}           copied to Trash/58         7.17 msgs/s  489.687 KiB/s 37.807 MiB copied ETA: Wed Nov  4 14:34:01 2020  5 s  38/605 msgs left
+msg Trash/677 {921}           copied to Trash/59         7.18 msgs/s  489.055 KiB/s 37.808 MiB copied ETA: Wed Nov  4 14:34:01 2020  5 s  37/605 msgs left
+msg Trash/678 {1018}          copied to Trash/60         7.18 msgs/s  488.461 KiB/s 37.809 MiB copied ETA: Wed Nov  4 14:34:01 2020  5 s  36/605 msgs left
+msg Trash/679 {5054}          copied to Trash/61         7.18 msgs/s  487.871 KiB/s 37.814 MiB copied ETA: Wed Nov  4 14:34:01 2020  5 s  35/605 msgs left
+msg Trash/680 {923}           copied to Trash/62         7.18 msgs/s  487.227 KiB/s 37.814 MiB copied ETA: Wed Nov  4 14:34:01 2020  5 s  34/605 msgs left
+msg Trash/681 {1750}          copied to Trash/63         7.19 msgs/s  486.675 KiB/s 37.816 MiB copied ETA: Wed Nov  4 14:34:00 2020  5 s  33/605 msgs left
+msg Trash/682 {1068}          copied to Trash/64         7.19 msgs/s  485.997 KiB/s 37.817 MiB copied ETA: Wed Nov  4 14:34:00 2020  4 s  32/605 msgs left
+msg Trash/683 {2631}          copied to Trash/65         7.19 msgs/s  485.374 KiB/s 37.820 MiB copied ETA: Wed Nov  4 14:34:00 2020  4 s  31/605 msgs left
+msg Trash/684 {2376}          copied to Trash/66         7.20 msgs/s  484.801 KiB/s 37.822 MiB copied ETA: Wed Nov  4 14:34:00 2020  4 s  30/605 msgs left
+msg Trash/685 {1032}          copied to Trash/67         7.20 msgs/s  484.155 KiB/s 37.823 MiB copied ETA: Wed Nov  4 14:34:00 2020  4 s  29/605 msgs left
+msg Trash/686 {937}           copied to Trash/68         7.20 msgs/s  483.592 KiB/s 37.824 MiB copied ETA: Wed Nov  4 14:34:00 2020  4 s  28/605 msgs left
+msg Trash/687 {1089}          copied to Trash/69         7.21 msgs/s  482.940 KiB/s 37.825 MiB copied ETA: Wed Nov  4 14:34:00 2020  4 s  27/605 msgs left
+msg Trash/688 {1099}          copied to Trash/70         7.21 msgs/s  482.274 KiB/s 37.826 MiB copied ETA: Wed Nov  4 14:34:00 2020  4 s  26/605 msgs left
+msg Trash/689 {1111}          copied to Trash/71         7.21 msgs/s  481.698 KiB/s 37.827 MiB copied ETA: Wed Nov  4 14:34:00 2020  3 s  25/605 msgs left
+msg Trash/690 {1108}          copied to Trash/72         7.22 msgs/s  481.100 KiB/s 37.828 MiB copied ETA: Wed Nov  4 14:34:00 2020  3 s  24/605 msgs left
+msg Trash/691 {1106}          copied to Trash/73         7.22 msgs/s  480.499 KiB/s 37.829 MiB copied ETA: Wed Nov  4 14:34:00 2020  3 s  23/605 msgs left
+msg Trash/692 {5487}          copied to Trash/74         7.22 msgs/s  480.003 KiB/s 37.834 MiB copied ETA: Wed Nov  4 14:34:00 2020  3 s  22/605 msgs left
+msg Trash/693 {1072}          copied to Trash/75         7.23 msgs/s  479.448 KiB/s 37.835 MiB copied ETA: Wed Nov  4 14:34:00 2020  3 s  21/605 msgs left
+msg Trash/694 {1286}          copied to Trash/76         7.23 msgs/s  478.918 KiB/s 37.837 MiB copied ETA: Wed Nov  4 14:34:00 2020  3 s  20/605 msgs left
+msg Trash/695 {25951}         copied to Trash/77         7.23 msgs/s  478.431 KiB/s 37.861 MiB copied ETA: Wed Nov  4 14:34:00 2020  3 s  19/605 msgs left
+msg Trash/696 {1402}          copied to Trash/78         7.23 msgs/s  477.840 KiB/s 37.863 MiB copied ETA: Wed Nov  4 14:34:00 2020  2 s  18/605 msgs left
+msg Trash/697 {1166}          copied to Trash/79         7.24 msgs/s  477.316 KiB/s 37.864 MiB copied ETA: Wed Nov  4 14:34:00 2020  2 s  17/605 msgs left
+msg Trash/698 {3065}          copied to Trash/80         7.24 msgs/s  476.764 KiB/s 37.867 MiB copied ETA: Wed Nov  4 14:34:00 2020  2 s  16/605 msgs left
+msg Trash/699 {1757}          copied to Trash/81         7.25 msgs/s  476.170 KiB/s 37.868 MiB copied ETA: Wed Nov  4 14:34:00 2020  2 s  15/605 msgs left
+msg Trash/700 {905}           copied to Trash/82         7.25 msgs/s  475.616 KiB/s 37.869 MiB copied ETA: Wed Nov  4 14:34:00 2020  2 s  14/605 msgs left
+msg Trash/701 {1103}          copied to Trash/83         7.25 msgs/s  475.035 KiB/s 37.870 MiB copied ETA: Wed Nov  4 14:34:00 2020  2 s  13/605 msgs left
+msg Trash/702 {1082}          copied to Trash/84         7.26 msgs/s  474.472 KiB/s 37.871 MiB copied ETA: Wed Nov  4 14:34:00 2020  2 s  12/605 msgs left
+msg Trash/703 {1127}          copied to Trash/85         7.26 msgs/s  473.927 KiB/s 37.872 MiB copied ETA: Wed Nov  4 14:34:00 2020  2 s  11/605 msgs left
+msg Trash/704 {1081}          copied to Trash/86         7.26 msgs/s  473.382 KiB/s 37.873 MiB copied ETA: Wed Nov  4 14:34:00 2020  1 s  10/605 msgs left
+msg Trash/705 {1128}          copied to Trash/87         7.27 msgs/s  472.841 KiB/s 37.874 MiB copied ETA: Wed Nov  4 14:34:00 2020  1 s  9/605 msgs left
+msg Trash/706 {1110}          copied to Trash/88         7.27 msgs/s  472.296 KiB/s 37.875 MiB copied ETA: Wed Nov  4 14:34:00 2020  1 s  8/605 msgs left
+msg Trash/707 {1108}          copied to Trash/89         7.27 msgs/s  471.738 KiB/s 37.877 MiB copied ETA: Wed Nov  4 14:34:00 2020  1 s  7/605 msgs left
+msg Trash/708 {1123}          copied to Trash/90         7.28 msgs/s  471.167 KiB/s 37.878 MiB copied ETA: Wed Nov  4 14:33:59 2020  1 s  6/605 msgs left
+msg Trash/709 {1127}          copied to Trash/91         7.28 msgs/s  470.588 KiB/s 37.879 MiB copied ETA: Wed Nov  4 14:33:59 2020  1 s  5/605 msgs left
+msg Trash/710 {1126}          copied to Trash/92         7.28 msgs/s  470.012 KiB/s 37.880 MiB copied ETA: Wed Nov  4 14:33:59 2020  1 s  4/605 msgs left
+msg Trash/711 {1133}          copied to Trash/93         7.29 msgs/s  469.443 KiB/s 37.881 MiB copied ETA: Wed Nov  4 14:33:59 2020  0 s  3/605 msgs left
+msg Trash/712 {1124}          copied to Trash/94         7.29 msgs/s  468.859 KiB/s 37.882 MiB copied ETA: Wed Nov  4 14:33:59 2020  0 s  2/605 msgs left
+msg Trash/713 {3839}          copied to Trash/95         7.29 msgs/s  468.323 KiB/s 37.886 MiB copied ETA: Wed Nov  4 14:33:59 2020  0 s  1/605 msgs left
+msg Trash/714 {3284}          copied to Trash/96         7.29 msgs/s  467.748 KiB/s 37.889 MiB copied ETA: Wed Nov  4 14:33:59 2020  0 s  0/605 msgs left
+ETA: Wed Nov  4 14:33:59 2020  0 s  0/605 msgs left
+++++ End looping on each folder
+
+Folders sizes after the synchronization.
+You can remove this foldersizes listing by using  "--nofoldersizesatend"
+Host1 folder     1/6 [Drafts]                            Size:       796 Messages:     1 Biggest:       796
+Host2 folder     1/6 [Drafts]                            Size:       796 Messages:     1 Biggest:       796
+Host2-Host1                                                            0               0                  0
+
+Host1 folder     2/6 [INBOX]                             Size:  21792684 Messages:   311 Biggest:   2723952
+Host2 folder     2/6 [INBOX]                             Size:  21792684 Messages:   311 Biggest:   2723952
+Host2-Host1                                                            0               0                  0
+
+Host1 folder     3/6 [Junk]                              Size:         0 Messages:     0 Biggest:         0
+Host2 folder     3/6 [Junk]                               does not exist yet
+Host2-Host1                                                            0               0                  0
+
+Host1 folder     4/6 [Sent]                              Size:  17726462 Messages:   197 Biggest:   1152231
+Host2 folder     4/6 [Sent]                              Size:  17726462 Messages:   197 Biggest:   1152231
+Host2-Host1                                                            0               0                  0
+
+Host1 folder     5/6 [Spam]                              Size:         0 Messages:     0 Biggest:         0
+Host2 folder     5/6 [Spam]                               does not exist yet
+Host2-Host1                                                            0               0                  0
+
+Host1 folder     6/6 [Trash]                             Size:    209248 Messages:    96 Biggest:     34890
+Host2 folder     6/6 [Trash]                             Size:    209248 Messages:    96 Biggest:     34890
+Host2-Host1                                                            0               0                  0
+
+Host1 Nb folders:                     6 folders
+Host2 Nb folders:                     6 folders
+
+Host1 Nb messages:                  605 messages
+Host2 Nb messages:                  605 messages
+
+Host1 Total size:              39729190 bytes (37.889 MiB)
+Host2 Total size:              39729190 bytes (37.889 MiB)
+
+Host1 Biggest message:          2723952 bytes (2.598 MiB)
+Host2 Biggest message:          2723952 bytes (2.598 MiB)
+
+Time spent on sizing:         1.0 seconds
+++++ Statistics
+Transfer started on                     : Wed Nov  4 14:32:34 2020
+Transfer ended on                       : Wed Nov  4 14:34:00 2020
+Transfer time                           : 86.8 sec
+Folders synced                          : 6/6 synced
+Messages transferred                    : 605 
+Messages skipped                        : 0
+Messages found duplicate on host1       : 0
+Messages found duplicate on host2       : 0
+Messages found crossduplicate on host2  : 0
+Messages void (noheader) on host1       : 0  
+Messages void (noheader) on host2       : 0
+Messages found in host1 not in host2    : 0 messages
+Messages found in host2 not in host1    : 0 messages
+Messages deleted on host1               : 0
+Messages deleted on host2               : 0
+Total bytes transferred                 : 39729190 (37.889 MiB)
+Total bytes skipped                     : 0 (0.000 KiB)
+Message rate                            : 7.0 messages/s
+Average bandwidth rate                  : 447.0 KiB/s
+Reconnections to host1                  : 0
+Reconnections to host2                  : 0
+Memory consumption at the end           : 172.8 MiB (started with 159.9 MiB)
+Load end is                             : 0.44 0.34 0.36 1/1199 on 2 cores
+Biggest message                         : 2723952 bytes (2.598 MiB)
+Memory/biggest message ratio            : 66.5
+Start difference host2 - host1          : -605 messages, -39729190 bytes (-37.889 MiB)
+Final difference host2 - host1          : 0 messages, 0 bytes (0.000 KiB)
+The sync looks good, all 603 identified messages in host1 are on host2.
+There is no unidentified message
+The sync is strict, all 603 identified messages in host2 are on host1.
+Detected 0 errors
+
+Check if a new imapsync release is available by adding --releasecheck
+Homepage: https://imapsync.lamiral.info/
+Exiting with return value 0 (EX_OK: successful termination) 0/20 nb_errors/max_errors
+Log file is LOG_imapsync/2020_11_04_14_32_34_024_info@petco.rs_info@petco.rs.txt ( to change it, use --logfile filepath ; or use --nolog to turn off logging )

LOG_imapsync/2020_11_05_00_18_42_956_admin123_.txt

@@ -0,0 +1,34 @@
+Here is imapsync 1.977 on host privremena, a linux system with 18.9/31.3 free GiB of RAM
+with Perl 5.28.1 and Mail::IMAPClient 3.42
+Transfer started at Thu Nov  5 00:18:42 2020
+PID is 16611 my PPID is 16610
+Log file is LOG_imapsync/2020_11_05_00_18_42_956_admin123_.txt ( to change it, use --logfile path ; or use --nolog to turn off logging )
+Load is 0.34 0.26 0.37 1/1184 on 2 cores
+Current directory is /root/imapsync-master
+Real user id is root (uid 0)
+Effective user id is root (euid 0)
+$RCSfile: imapsync,v $ $Revision: 1.977 $ $Date: 2019/12/23 20:18:02 $ 
+Command line used, run by /usr/bin/perl:
+./imapsync --addheader --automap --user1 admin123
+Temp directory is . ( to change it use --tmpdir dirpath )
+Under cgi context
+Umask set with 0077 (was 0022)
+REMOTE_ADDR is ::ffff:194.166.59.157
+HTTP_REFERER is http://148.251.112.220:8080/
+HTTP_USER_AGENT is Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/86.0.4240.183 Safari/537.36
+SERVER_SOFTWARE is ./webserver
+SERVER_PORT is 8080
+kill -QUIT 16611 # special behavior: call to sub catch_exit
+kill -TERM 16611 # special behavior: call to sub catch_exit
+kill -INT 16611 # special behavior: call to sub catch_reconnect
+kill -HUP 16611 # special behavior: call to sub catch_print
+kill -USR1 16611 # special behavior: call to sub toggle_sleep
+File ./imapsync__admin123__.pid does not exist
+Error reading file ./imapsync__admin123__.pid : No such file or directory
+PID file is ./imapsync__admin123__.pid ( to change it, use --pidfile filepath ; to avoid it use --pidfile "" )
+Writing my PID 16611 in ./imapsync__admin123__.pid
+Writing also my logfile name in ./imapsync__admin123__.pid : LOG_imapsync/2020_11_05_00_18_42_956_admin123_.txt
+Info: will resync flags for already transferred messages. Use --noresyncflags to not resync flags.
+Exiting after a justconnect on host(s):  
+Exiting with return value 0 (EX_OK: successful termination) 0/20 nb_errors/max_errors
+Log file is LOG_imapsync/2020_11_05_00_18_42_956_admin123_.txt ( to change it, use --logfile filepath ; or use --nolog to turn off logging )

LOG_imapsync/2020_11_07_15_03_14_511_helpzona@helpzona.com_helpzona@helpzona.com.txt

@@ -0,0 +1,54 @@
+Here is imapsync 1.977 on host privremena, a linux system with 19.3/31.3 free GiB of RAM
+with Perl 5.28.1 and Mail::IMAPClient 3.42
+Transfer started at Sat Nov  7 15:03:14 2020
+PID is 24650 my PPID is 24649
+Log file is LOG_imapsync/2020_11_07_15_03_14_511_helpzona@helpzona.com_helpzona@helpzona.com.txt ( to change it, use --logfile path ; or use --nolog to turn off logging )
+Load is 0.75 0.70 0.55 1/1191 on 2 cores
+Current directory is /root/imapsync-master
+Real user id is root (uid 0)
+Effective user id is root (euid 0)
+$RCSfile: imapsync,v $ $Revision: 1.977 $ $Date: 2019/12/23 20:18:02 $ 
+Command line used, run by /usr/bin/perl:
+./imapsync --addheader --automap --host1 cp8.ulimitserver.com --host2 91.134.230.68 --password1 MASKED --password2 MASKED --user1 helpzona@helpzona.com --user2 helpzona@helpzona.com
+Temp directory is . ( to change it use --tmpdir dirpath )
+Under cgi context
+Umask set with 0077 (was 0022)
+REMOTE_ADDR is ::ffff:89.164.15.130
+HTTP_REFERER is http://148.251.112.220:8080/
+HTTP_USER_AGENT is Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:82.0) Gecko/20100101 Firefox/82.0
+SERVER_SOFTWARE is ./webserver
+SERVER_PORT is 8080
+kill -QUIT 24650 # special behavior: call to sub catch_exit
+kill -TERM 24650 # special behavior: call to sub catch_exit
+kill -INT 24650 # special behavior: call to sub catch_reconnect
+kill -HUP 24650 # special behavior: call to sub catch_print
+kill -USR1 24650 # special behavior: call to sub toggle_sleep
+File ./imapsync_cp8.ulimitserver.com_helpzona@helpzona.com_91.134.230.68_helpzona@helpzona.com.pid does not exist
+Error reading file ./imapsync_cp8.ulimitserver.com_helpzona@helpzona.com_91.134.230.68_helpzona@helpzona.com.pid : No such file or directory
+PID file is ./imapsync_cp8.ulimitserver.com_helpzona@helpzona.com_91.134.230.68_helpzona@helpzona.com.pid ( to change it, use --pidfile filepath ; to avoid it use --pidfile "" )
+Writing my PID 24650 in ./imapsync_cp8.ulimitserver.com_helpzona@helpzona.com_91.134.230.68_helpzona@helpzona.com.pid
+Writing also my logfile name in ./imapsync_cp8.ulimitserver.com_helpzona@helpzona.com_91.134.230.68_helpzona@helpzona.com.pid : LOG_imapsync/2020_11_07_15_03_14_511_helpzona@helpzona.com_helpzona@helpzona.com.txt
+Info: will resync flags for already transferred messages. Use --noresyncflags to not resync flags.
+Host1: probing ssl on port 993 ( use --nosslcheck to avoid this ssl probe ) 
+Host1: sslcheck detected open ssl port 993 so turning ssl on (use --nossl1 --notls1 to turn off SSL and TLS wizardry)
+Host2: probing ssl on port 993 ( use --nosslcheck to avoid this ssl probe ) 
+Host2: sslcheck did not detected open ssl port 993. Will use standard 143 port.
+SSL debug mode level is --debugssl 1 (can be set from 0 meaning no debug to 4 meaning max debug)
+Host1: SSL default mode is like --sslargs1 "SSL_verify_mode=0", meaning for host1 SSL_VERIFY_NONE, ie, do not check the certificate server.
+Host1: Use --sslargs1 SSL_verify_mode=1 to have SSL_VERIFY_PEER, ie, check the certificate server of host1
+Info: turned ON syncinternaldates, will set the internal dates (arrival dates) on host2 same as host1.
+Host1: will try to use LOGIN authentication on host1
+Host2: will try to use LOGIN authentication on host2
+Host1: imap connection timeout is 120 seconds
+Host2: imap connection timeout is 120 seconds
+Host1: IMAP server [cp8.ulimitserver.com] port [993] user [helpzona@helpzona.com]
+Host2: IMAP server [91.134.230.68] port [143] user [helpzona@helpzona.com]
+Host1: connecting and login on host1 [cp8.ulimitserver.com] port [993] with user [helpzona@helpzona.com]
+Host1 IP address: 194.146.59.72
+Host1 banner: * OK [CAPABILITY IMAP4rev1 SASL-IR LOGIN-REFERRALS ID ENABLE IDLE NAMESPACE LITERAL+ AUTH=PLAIN AUTH=LOGIN] Dovecot ready.
+Host1 capability before authentication: IMAP4rev1 SASL-IR LOGIN-REFERRALS ID ENABLE IDLE NAMESPACE LITERAL+ AUTH=PLAIN AUTH=LOGIN AUTH
+Host1: cp8.ulimitserver.com says it has CAPABILITY for AUTHENTICATE LOGIN
+Host1 info: authmech [LOGIN] user [helpzona@helpzona.com] authuser [] IsUnconnected []
+Host1 failure: Error login on [cp8.ulimitserver.com] with user [helpzona@helpzona.com] auth [LOGIN]: 2 NO [AUTHENTICATIONFAILED] Authentication failed.
+Exiting with return value 16 (EXIT_AUTHENTICATION_FAILURE) 1/20 nb_errors/max_errors
+Log file is LOG_imapsync/2020_11_07_15_03_14_511_helpzona@helpzona.com_helpzona@helpzona.com.txt ( to change it, use --logfile filepath ; or use --nolog to turn off logging )

LOG_imapsync/2020_11_07_15_03_38_038_helpzona@helpzona.com_helpzona@helpzona.com.txt

@@ -0,0 +1,55 @@
+Here is imapsync 1.977 on host privremena, a linux system with 19.3/31.3 free GiB of RAM
+with Perl 5.28.1 and Mail::IMAPClient 3.42
+Transfer started at Sat Nov  7 15:03:38 2020
+PID is 24681 my PPID is 24680
+Log file is LOG_imapsync/2020_11_07_15_03_38_038_helpzona@helpzona.com_helpzona@helpzona.com.txt ( to change it, use --logfile path ; or use --nolog to turn off logging )
+Load is 0.49 0.65 0.54 1/1195 on 2 cores
+Current directory is /root/imapsync-master
+Real user id is root (uid 0)
+Effective user id is root (euid 0)
+$RCSfile: imapsync,v $ $Revision: 1.977 $ $Date: 2019/12/23 20:18:02 $ 
+Command line used, run by /usr/bin/perl:
+./imapsync --addheader --automap --host1 cp8.ulimitserver.com --host2 91.134.230.68 --password1 MASKED --password2 MASKED --user1 helpzona@helpzona.com --user2 helpzona@helpzona.com
+Temp directory is . ( to change it use --tmpdir dirpath )
+Under cgi context
+Umask set with 0077 (was 0022)
+REMOTE_ADDR is ::ffff:89.164.15.130
+HTTP_REFERER is http://148.251.112.220:8080/
+HTTP_USER_AGENT is Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:82.0) Gecko/20100101 Firefox/82.0
+SERVER_SOFTWARE is ./webserver
+SERVER_PORT is 8080
+HTTP_COOKIE is imapsync_runs=1
+kill -QUIT 24681 # special behavior: call to sub catch_exit
+kill -TERM 24681 # special behavior: call to sub catch_exit
+kill -INT 24681 # special behavior: call to sub catch_reconnect
+kill -HUP 24681 # special behavior: call to sub catch_print
+kill -USR1 24681 # special behavior: call to sub toggle_sleep
+File ./imapsync_cp8.ulimitserver.com_helpzona@helpzona.com_91.134.230.68_helpzona@helpzona.com.pid does not exist
+Error reading file ./imapsync_cp8.ulimitserver.com_helpzona@helpzona.com_91.134.230.68_helpzona@helpzona.com.pid : No such file or directory
+PID file is ./imapsync_cp8.ulimitserver.com_helpzona@helpzona.com_91.134.230.68_helpzona@helpzona.com.pid ( to change it, use --pidfile filepath ; to avoid it use --pidfile "" )
+Writing my PID 24681 in ./imapsync_cp8.ulimitserver.com_helpzona@helpzona.com_91.134.230.68_helpzona@helpzona.com.pid
+Writing also my logfile name in ./imapsync_cp8.ulimitserver.com_helpzona@helpzona.com_91.134.230.68_helpzona@helpzona.com.pid : LOG_imapsync/2020_11_07_15_03_38_038_helpzona@helpzona.com_helpzona@helpzona.com.txt
+Info: will resync flags for already transferred messages. Use --noresyncflags to not resync flags.
+Host1: probing ssl on port 993 ( use --nosslcheck to avoid this ssl probe ) 
+Host1: sslcheck detected open ssl port 993 so turning ssl on (use --nossl1 --notls1 to turn off SSL and TLS wizardry)
+Host2: probing ssl on port 993 ( use --nosslcheck to avoid this ssl probe ) 
+Host2: sslcheck did not detected open ssl port 993. Will use standard 143 port.
+SSL debug mode level is --debugssl 1 (can be set from 0 meaning no debug to 4 meaning max debug)
+Host1: SSL default mode is like --sslargs1 "SSL_verify_mode=0", meaning for host1 SSL_VERIFY_NONE, ie, do not check the certificate server.
+Host1: Use --sslargs1 SSL_verify_mode=1 to have SSL_VERIFY_PEER, ie, check the certificate server of host1
+Info: turned ON syncinternaldates, will set the internal dates (arrival dates) on host2 same as host1.
+Host1: will try to use LOGIN authentication on host1
+Host2: will try to use LOGIN authentication on host2
+Host1: imap connection timeout is 120 seconds
+Host2: imap connection timeout is 120 seconds
+Host1: IMAP server [cp8.ulimitserver.com] port [993] user [helpzona@helpzona.com]
+Host2: IMAP server [91.134.230.68] port [143] user [helpzona@helpzona.com]
+Host1: connecting and login on host1 [cp8.ulimitserver.com] port [993] with user [helpzona@helpzona.com]
+Host1 IP address: 194.146.59.72
+Host1 banner: * OK [CAPABILITY IMAP4rev1 SASL-IR LOGIN-REFERRALS ID ENABLE IDLE NAMESPACE LITERAL+ AUTH=PLAIN AUTH=LOGIN] Dovecot ready.
+Host1 capability before authentication: IMAP4rev1 SASL-IR LOGIN-REFERRALS ID ENABLE IDLE NAMESPACE LITERAL+ AUTH=PLAIN AUTH=LOGIN AUTH
+Host1: cp8.ulimitserver.com says it has CAPABILITY for AUTHENTICATE LOGIN
+Host1 info: authmech [LOGIN] user [helpzona@helpzona.com] authuser [] IsUnconnected []
+Host1 failure: Error login on [cp8.ulimitserver.com] with user [helpzona@helpzona.com] auth [LOGIN]: 2 NO [AUTHENTICATIONFAILED] Authentication failed.
+Exiting with return value 16 (EXIT_AUTHENTICATION_FAILURE) 1/20 nb_errors/max_errors
+Log file is LOG_imapsync/2020_11_07_15_03_38_038_helpzona@helpzona.com_helpzona@helpzona.com.txt ( to change it, use --logfile filepath ; or use --nolog to turn off logging )

LOG_imapsync/2020_11_07_15_04_42_382_helpzona@helpzona.com_helpzona@helpzona.com.txt

@@ -0,0 +1,63 @@
+Here is imapsync 1.977 on host privremena, a linux system with 19.3/31.3 free GiB of RAM
+with Perl 5.28.1 and Mail::IMAPClient 3.42
+Transfer started at Sat Nov  7 15:04:42 2020
+PID is 24705 my PPID is 24704
+Log file is LOG_imapsync/2020_11_07_15_04_42_382_helpzona@helpzona.com_helpzona@helpzona.com.txt ( to change it, use --logfile path ; or use --nolog to turn off logging )
+Load is 0.46 0.61 0.53 1/1191 on 2 cores
+Current directory is /root/imapsync-master
+Real user id is root (uid 0)
+Effective user id is root (euid 0)
+$RCSfile: imapsync,v $ $Revision: 1.977 $ $Date: 2019/12/23 20:18:02 $ 
+Command line used, run by /usr/bin/perl:
+./imapsync --addheader --automap --host1 cp8.ulimitserver.com --host2 91.134.230.68 --password1 MASKED --password2 MASKED --user1 helpzona@helpzona.com --user2 helpzona@helpzona.com
+Temp directory is . ( to change it use --tmpdir dirpath )
+Under cgi context
+Umask set with 0077 (was 0022)
+REMOTE_ADDR is ::ffff:89.164.15.130
+HTTP_REFERER is http://148.251.112.220:8080/
+HTTP_USER_AGENT is Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:82.0) Gecko/20100101 Firefox/82.0
+SERVER_SOFTWARE is ./webserver
+SERVER_PORT is 8080
+HTTP_COOKIE is imapsync_runs=2
+kill -QUIT 24705 # special behavior: call to sub catch_exit
+kill -TERM 24705 # special behavior: call to sub catch_exit
+kill -INT 24705 # special behavior: call to sub catch_reconnect
+kill -HUP 24705 # special behavior: call to sub catch_print
+kill -USR1 24705 # special behavior: call to sub toggle_sleep
+File ./imapsync_cp8.ulimitserver.com_helpzona@helpzona.com_91.134.230.68_helpzona@helpzona.com.pid does not exist
+Error reading file ./imapsync_cp8.ulimitserver.com_helpzona@helpzona.com_91.134.230.68_helpzona@helpzona.com.pid : No such file or directory
+PID file is ./imapsync_cp8.ulimitserver.com_helpzona@helpzona.com_91.134.230.68_helpzona@helpzona.com.pid ( to change it, use --pidfile filepath ; to avoid it use --pidfile "" )
+Writing my PID 24705 in ./imapsync_cp8.ulimitserver.com_helpzona@helpzona.com_91.134.230.68_helpzona@helpzona.com.pid
+Writing also my logfile name in ./imapsync_cp8.ulimitserver.com_helpzona@helpzona.com_91.134.230.68_helpzona@helpzona.com.pid : LOG_imapsync/2020_11_07_15_04_42_382_helpzona@helpzona.com_helpzona@helpzona.com.txt
+Info: will resync flags for already transferred messages. Use --noresyncflags to not resync flags.
+Host1: probing ssl on port 993 ( use --nosslcheck to avoid this ssl probe ) 
+Host1: sslcheck detected open ssl port 993 so turning ssl on (use --nossl1 --notls1 to turn off SSL and TLS wizardry)
+Host2: probing ssl on port 993 ( use --nosslcheck to avoid this ssl probe ) 
+Host2: sslcheck did not detected open ssl port 993. Will use standard 143 port.
+SSL debug mode level is --debugssl 1 (can be set from 0 meaning no debug to 4 meaning max debug)
+Host1: SSL default mode is like --sslargs1 "SSL_verify_mode=0", meaning for host1 SSL_VERIFY_NONE, ie, do not check the certificate server.
+Host1: Use --sslargs1 SSL_verify_mode=1 to have SSL_VERIFY_PEER, ie, check the certificate server of host1
+Info: turned ON syncinternaldates, will set the internal dates (arrival dates) on host2 same as host1.
+Host1: will try to use LOGIN authentication on host1
+Host2: will try to use LOGIN authentication on host2
+Host1: imap connection timeout is 120 seconds
+Host2: imap connection timeout is 120 seconds
+Host1: IMAP server [cp8.ulimitserver.com] port [993] user [helpzona@helpzona.com]
+Host2: IMAP server [91.134.230.68] port [143] user [helpzona@helpzona.com]
+Host1: connecting and login on host1 [cp8.ulimitserver.com] port [993] with user [helpzona@helpzona.com]
+Host1 IP address: 194.146.59.72
+Host1 banner: * OK [CAPABILITY IMAP4rev1 SASL-IR LOGIN-REFERRALS ID ENABLE IDLE NAMESPACE LITERAL+ AUTH=PLAIN AUTH=LOGIN] Dovecot ready.
+Host1 capability before authentication: IMAP4rev1 SASL-IR LOGIN-REFERRALS ID ENABLE IDLE NAMESPACE LITERAL+ AUTH=PLAIN AUTH=LOGIN AUTH
+Host1: cp8.ulimitserver.com says it has CAPABILITY for AUTHENTICATE LOGIN
+Host1: success login on [cp8.ulimitserver.com] with user [helpzona@helpzona.com] auth [LOGIN]
+Host2: connecting and login on host2 [91.134.230.68] port [143] with user [helpzona@helpzona.com]
+Host2 IP address: 91.134.230.68
+Host2 banner: * OK [CAPABILITY IMAP4rev1 SASL-IR LOGIN-REFERRALS ID ENABLE IDLE LITERAL+ STARTTLS AUTH=PLAIN AUTH=LOGIN AUTH=DIGEST-MD5 AUTH=CRAM-MD5] Dovecot (Ubuntu) ready.
+Host2 capability before authentication: IMAP4rev1 SASL-IR LOGIN-REFERRALS ID ENABLE IDLE LITERAL+ STARTTLS AUTH=PLAIN AUTH=LOGIN AUTH=DIGEST-MD5 AUTH=CRAM-MD5 AUTH
+Host2: going to ssl because STARTTLS is in CAPABILITY. Use --notls1 or --notls2 to avoid that behavior
+DEBUG: .../IO/Socket/SSL.pm:825: local error: SSL connect attempt failed error:1408F10B:SSL routines:ssl3_get_record:wrong version number
+DEBUG: .../IO/Socket/SSL.pm:828: fatal SSL error: SSL connect attempt failed error:1408F10B:SSL routines:ssl3_get_record:wrong version number
+Host2 failure: Can not go to tls encryption on host2 [91.134.230.68]:Unable to start TLS: SSL connect attempt failed error:1408F10B:SSL routines:ssl3_get_record:wrong version number
+Exiting with return value 12 (EXIT_TLS_FAILURE) 1/20 nb_errors/max_errors
+Disconnecting from host1 cp8.ulimitserver.com user1 helpzona@helpzona.com
+Log file is LOG_imapsync/2020_11_07_15_04_42_382_helpzona@helpzona.com_helpzona@helpzona.com.txt ( to change it, use --logfile filepath ; or use --nolog to turn off logging )

LOG_imapsync/2020_11_07_15_06_42_533_helpzona@helpzona.com_helpzona@helpzona.com.txt

@@ -0,0 +1,63 @@
+Here is imapsync 1.977 on host privremena, a linux system with 19.3/31.3 free GiB of RAM
+with Perl 5.28.1 and Mail::IMAPClient 3.42
+Transfer started at Sat Nov  7 15:06:42 2020
+PID is 24766 my PPID is 24765
+Log file is LOG_imapsync/2020_11_07_15_06_42_533_helpzona@helpzona.com_helpzona@helpzona.com.txt ( to change it, use --logfile path ; or use --nolog to turn off logging )
+Load is 0.39 0.57 0.53 1/1187 on 2 cores
+Current directory is /root/imapsync-master
+Real user id is root (uid 0)
+Effective user id is root (euid 0)
+$RCSfile: imapsync,v $ $Revision: 1.977 $ $Date: 2019/12/23 20:18:02 $ 
+Command line used, run by /usr/bin/perl:
+./imapsync --addheader --automap --host1 cp8.ulimitserver.com --host2 91.134.230.68 --password1 MASKED --password2 MASKED --user1 helpzona@helpzona.com --user2 helpzona@helpzona.com
+Temp directory is . ( to change it use --tmpdir dirpath )
+Under cgi context
+Umask set with 0077 (was 0022)
+REMOTE_ADDR is ::ffff:89.164.15.130
+HTTP_REFERER is http://148.251.112.220:8080/
+HTTP_USER_AGENT is Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:82.0) Gecko/20100101 Firefox/82.0
+SERVER_SOFTWARE is ./webserver
+SERVER_PORT is 8080
+HTTP_COOKIE is imapsync_runs=3
+kill -QUIT 24766 # special behavior: call to sub catch_exit
+kill -TERM 24766 # special behavior: call to sub catch_exit
+kill -INT 24766 # special behavior: call to sub catch_reconnect
+kill -HUP 24766 # special behavior: call to sub catch_print
+kill -USR1 24766 # special behavior: call to sub toggle_sleep
+File ./imapsync_cp8.ulimitserver.com_helpzona@helpzona.com_91.134.230.68_helpzona@helpzona.com.pid does not exist
+Error reading file ./imapsync_cp8.ulimitserver.com_helpzona@helpzona.com_91.134.230.68_helpzona@helpzona.com.pid : No such file or directory
+PID file is ./imapsync_cp8.ulimitserver.com_helpzona@helpzona.com_91.134.230.68_helpzona@helpzona.com.pid ( to change it, use --pidfile filepath ; to avoid it use --pidfile "" )
+Writing my PID 24766 in ./imapsync_cp8.ulimitserver.com_helpzona@helpzona.com_91.134.230.68_helpzona@helpzona.com.pid
+Writing also my logfile name in ./imapsync_cp8.ulimitserver.com_helpzona@helpzona.com_91.134.230.68_helpzona@helpzona.com.pid : LOG_imapsync/2020_11_07_15_06_42_533_helpzona@helpzona.com_helpzona@helpzona.com.txt
+Info: will resync flags for already transferred messages. Use --noresyncflags to not resync flags.
+Host1: probing ssl on port 993 ( use --nosslcheck to avoid this ssl probe ) 
+Host1: sslcheck detected open ssl port 993 so turning ssl on (use --nossl1 --notls1 to turn off SSL and TLS wizardry)
+Host2: probing ssl on port 993 ( use --nosslcheck to avoid this ssl probe ) 
+Host2: sslcheck did not detected open ssl port 993. Will use standard 143 port.
+SSL debug mode level is --debugssl 1 (can be set from 0 meaning no debug to 4 meaning max debug)
+Host1: SSL default mode is like --sslargs1 "SSL_verify_mode=0", meaning for host1 SSL_VERIFY_NONE, ie, do not check the certificate server.
+Host1: Use --sslargs1 SSL_verify_mode=1 to have SSL_VERIFY_PEER, ie, check the certificate server of host1
+Info: turned ON syncinternaldates, will set the internal dates (arrival dates) on host2 same as host1.
+Host1: will try to use LOGIN authentication on host1
+Host2: will try to use LOGIN authentication on host2
+Host1: imap connection timeout is 120 seconds
+Host2: imap connection timeout is 120 seconds
+Host1: IMAP server [cp8.ulimitserver.com] port [993] user [helpzona@helpzona.com]
+Host2: IMAP server [91.134.230.68] port [143] user [helpzona@helpzona.com]
+Host1: connecting and login on host1 [cp8.ulimitserver.com] port [993] with user [helpzona@helpzona.com]
+Host1 IP address: 194.146.59.72
+Host1 banner: * OK [CAPABILITY IMAP4rev1 SASL-IR LOGIN-REFERRALS ID ENABLE IDLE NAMESPACE LITERAL+ AUTH=PLAIN AUTH=LOGIN] Dovecot ready.
+Host1 capability before authentication: IMAP4rev1 SASL-IR LOGIN-REFERRALS ID ENABLE IDLE NAMESPACE LITERAL+ AUTH=PLAIN AUTH=LOGIN AUTH
+Host1: cp8.ulimitserver.com says it has CAPABILITY for AUTHENTICATE LOGIN
+Host1: success login on [cp8.ulimitserver.com] with user [helpzona@helpzona.com] auth [LOGIN]
+Host2: connecting and login on host2 [91.134.230.68] port [143] with user [helpzona@helpzona.com]
+Host2 IP address: 91.134.230.68
+Host2 banner: * OK [CAPABILITY IMAP4rev1 SASL-IR LOGIN-REFERRALS ID ENABLE IDLE LITERAL+ STARTTLS AUTH=PLAIN AUTH=LOGIN AUTH=DIGEST-MD5 AUTH=CRAM-MD5] Dovecot (Ubuntu) ready.
+Host2 capability before authentication: IMAP4rev1 SASL-IR LOGIN-REFERRALS ID ENABLE IDLE LITERAL+ STARTTLS AUTH=PLAIN AUTH=LOGIN AUTH=DIGEST-MD5 AUTH=CRAM-MD5 AUTH
+Host2: going to ssl because STARTTLS is in CAPABILITY. Use --notls1 or --notls2 to avoid that behavior
+DEBUG: .../IO/Socket/SSL.pm:825: local error: SSL connect attempt failed error:1408F10B:SSL routines:ssl3_get_record:wrong version number
+DEBUG: .../IO/Socket/SSL.pm:828: fatal SSL error: SSL connect attempt failed error:1408F10B:SSL routines:ssl3_get_record:wrong version number
+Host2 failure: Can not go to tls encryption on host2 [91.134.230.68]:Unable to start TLS: SSL connect attempt failed error:1408F10B:SSL routines:ssl3_get_record:wrong version number
+Exiting with return value 12 (EXIT_TLS_FAILURE) 1/20 nb_errors/max_errors
+Disconnecting from host1 cp8.ulimitserver.com user1 helpzona@helpzona.com
+Log file is LOG_imapsync/2020_11_07_15_06_42_533_helpzona@helpzona.com_helpzona@helpzona.com.txt ( to change it, use --logfile filepath ; or use --nolog to turn off logging )

LOG_imapsync/2020_11_07_15_06_49_786_helpzona@helpzona.com_helpzona@helpzona.com.txt

@@ -0,0 +1,55 @@
+Here is imapsync 1.977 on host privremena, a linux system with 19.3/31.3 free GiB of RAM
+with Perl 5.28.1 and Mail::IMAPClient 3.42
+Transfer started at Sat Nov  7 15:06:49 2020
+PID is 24773 my PPID is 24772
+Log file is LOG_imapsync/2020_11_07_15_06_49_786_helpzona@helpzona.com_helpzona@helpzona.com.txt ( to change it, use --logfile path ; or use --nolog to turn off logging )
+Load is 0.48 0.59 0.54 1/1189 on 2 cores
+Current directory is /root/imapsync-master
+Real user id is root (uid 0)
+Effective user id is root (euid 0)
+$RCSfile: imapsync,v $ $Revision: 1.977 $ $Date: 2019/12/23 20:18:02 $ 
+Command line used, run by /usr/bin/perl:
+./imapsync --addheader --automap --host1 cp8.ulimitserver.com --host2 91.134.230.68 --password1 MASKED --password2 MASKED --user1 helpzona@helpzona.com --user2 helpzona@helpzona.com
+Temp directory is . ( to change it use --tmpdir dirpath )
+Under cgi context
+Umask set with 0077 (was 0022)
+REMOTE_ADDR is ::ffff:89.164.15.130
+HTTP_REFERER is http://148.251.112.220:8080/
+HTTP_USER_AGENT is Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:82.0) Gecko/20100101 Firefox/82.0
+SERVER_SOFTWARE is ./webserver
+SERVER_PORT is 8080
+HTTP_COOKIE is imapsync_runs=4
+kill -QUIT 24773 # special behavior: call to sub catch_exit
+kill -TERM 24773 # special behavior: call to sub catch_exit
+kill -INT 24773 # special behavior: call to sub catch_reconnect
+kill -HUP 24773 # special behavior: call to sub catch_print
+kill -USR1 24773 # special behavior: call to sub toggle_sleep
+File ./imapsync_cp8.ulimitserver.com_helpzona@helpzona.com_91.134.230.68_helpzona@helpzona.com.pid does not exist
+Error reading file ./imapsync_cp8.ulimitserver.com_helpzona@helpzona.com_91.134.230.68_helpzona@helpzona.com.pid : No such file or directory
+PID file is ./imapsync_cp8.ulimitserver.com_helpzona@helpzona.com_91.134.230.68_helpzona@helpzona.com.pid ( to change it, use --pidfile filepath ; to avoid it use --pidfile "" )
+Writing my PID 24773 in ./imapsync_cp8.ulimitserver.com_helpzona@helpzona.com_91.134.230.68_helpzona@helpzona.com.pid
+Writing also my logfile name in ./imapsync_cp8.ulimitserver.com_helpzona@helpzona.com_91.134.230.68_helpzona@helpzona.com.pid : LOG_imapsync/2020_11_07_15_06_49_786_helpzona@helpzona.com_helpzona@helpzona.com.txt
+Info: will resync flags for already transferred messages. Use --noresyncflags to not resync flags.
+Host1: probing ssl on port 993 ( use --nosslcheck to avoid this ssl probe ) 
+Host1: sslcheck detected open ssl port 993 so turning ssl on (use --nossl1 --notls1 to turn off SSL and TLS wizardry)
+Host2: probing ssl on port 993 ( use --nosslcheck to avoid this ssl probe ) 
+Host2: sslcheck did not detected open ssl port 993. Will use standard 143 port.
+SSL debug mode level is --debugssl 1 (can be set from 0 meaning no debug to 4 meaning max debug)
+Host1: SSL default mode is like --sslargs1 "SSL_verify_mode=0", meaning for host1 SSL_VERIFY_NONE, ie, do not check the certificate server.
+Host1: Use --sslargs1 SSL_verify_mode=1 to have SSL_VERIFY_PEER, ie, check the certificate server of host1
+Info: turned ON syncinternaldates, will set the internal dates (arrival dates) on host2 same as host1.
+Host1: will try to use LOGIN authentication on host1
+Host2: will try to use LOGIN authentication on host2
+Host1: imap connection timeout is 120 seconds
+Host2: imap connection timeout is 120 seconds
+Host1: IMAP server [cp8.ulimitserver.com] port [993] user [helpzona@helpzona.com]
+Host2: IMAP server [91.134.230.68] port [143] user [helpzona@helpzona.com]
+Host1: connecting and login on host1 [cp8.ulimitserver.com] port [993] with user [helpzona@helpzona.com]
+Host1 IP address: 194.146.59.72
+Host1 banner: * OK [CAPABILITY IMAP4rev1 SASL-IR LOGIN-REFERRALS ID ENABLE IDLE NAMESPACE LITERAL+ AUTH=PLAIN AUTH=LOGIN] Dovecot ready.
+Host1 capability before authentication: IMAP4rev1 SASL-IR LOGIN-REFERRALS ID ENABLE IDLE NAMESPACE LITERAL+ AUTH=PLAIN AUTH=LOGIN AUTH
+Host1: cp8.ulimitserver.com says it has CAPABILITY for AUTHENTICATE LOGIN
+Host1 info: authmech [LOGIN] user [helpzona@helpzona.com] authuser [] IsUnconnected []
+Host1 failure: Error login on [cp8.ulimitserver.com] with user [helpzona@helpzona.com] auth [LOGIN]: 2 NO [AUTHENTICATIONFAILED] Authentication failed.
+Exiting with return value 16 (EXIT_AUTHENTICATION_FAILURE) 1/20 nb_errors/max_errors
+Log file is LOG_imapsync/2020_11_07_15_06_49_786_helpzona@helpzona.com_helpzona@helpzona.com.txt ( to change it, use --logfile filepath ; or use --nolog to turn off logging )