mirror of
https://github.com/imapsync/imapsync.git
synced 2025-06-11 23:24:30 +02:00
1.977
This commit is contained in:
Nick Bebout
parent
93b917b12b
commit
1d08afaba6
139 changed files with 27179 additions and 6213 deletions
|
|
@ -1,5 +1,5 @@
|
|||
#!/bin/cat
|
||||
$Id: FAQ.Admin_Authentication.txt,v 1.9 2019/06/26 22:16:43 gilles Exp gilles $
|
||||
$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/
|
||||
|
|
@ -13,8 +13,9 @@ https://imapsync.lamiral.info/FAQ.d/FAQ.Admin_Authentication.txt
|
|||
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 --authuser1
|
||||
sometimes not. It depends on the imap software server and its configuration.
|
||||
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
|
||||
|
|
|
|||
|
|
@ -1,5 +1,5 @@
|
|||
#!/bin/cat
|
||||
$Id: FAQ.Archiving.txt,v 1.14 2019/03/22 11:50:36 gilles Exp gilles $
|
||||
$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/
|
||||
|
|
@ -11,49 +11,82 @@ https://imapsync.lamiral.info/FAQ.d/FAQ.Archiving.txt
|
|||
|
||||
Questions answered in this FAQ are:
|
||||
|
||||
Q. Can I archive different accounts on the same destination account,
|
||||
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.
|
||||
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 a local offline copy of a
|
||||
mailbox from host1, eg for backup purposes, so that if the
|
||||
server fails, then the mailbox could be reinstated,
|
||||
ideally without requiring a second IMAP host?
|
||||
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. Can I archive different accounts on the same destination account,
|
||||
Q. How can I archive different accounts on the same destination account,
|
||||
each account on a separate folder?
|
||||
|
||||
R. Yes. Use --subfolder2
|
||||
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.)
|
||||
|
||||
Example:
|
||||
Examples:
|
||||
|
||||
imapsync ... --user1 Foo --subfolder2 FooArch
|
||||
imapsync ... --user1 Foo --subfolder2 FooArchiv
|
||||
|
||||
imapsync ... --user1 Bar --subfolder2 BarArch
|
||||
imapsync ... --user1 Bar --subfolder2 BarArchiv
|
||||
|
||||
In case you need a strict sync, add --delete2 --delete2foldersonly "FooArch"
|
||||
(or "BarArch" for the second example); it will delete on account2
|
||||
what is not on account1 but only in the right place, ie, the subfolder "foo".
|
||||
Example:
|
||||
|
||||
imapsync ... --user1 Foo --subfolder2 FooArch --delete2 --delete2foldersonly "FooArch"
|
||||
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, move all messages older than 1 year from INBOX to Archive.
|
||||
same IMAP server or a different one?
|
||||
For example, all messages older than 1 year, move from INBOX to Archive.
|
||||
|
||||
R1. Solution:
|
||||
|
||||
|
|
@ -67,12 +100,12 @@ R2. See also file FAQ.Folders_Mapping.txt
|
|||
|
||||
https://imapsync.lamiral.info/FAQ.d/FAQ.Archiving.txt
|
||||
=======================================================================
|
||||
Q. Can imapsync be used to maintain a local offline copy of a
|
||||
mailbox from host1, eg for backup purposes, so that if the
|
||||
server fails, then the mailbox could be reinstated,
|
||||
ideally without requiring a second IMAP host?
|
||||
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.
|
||||
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
|
||||
|
|
@ -88,6 +121,23 @@ R2. Imapsync can't but rick-sanders-imap-tools can!
|
|||
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
|
||||
|
||||
=======================================================================
|
||||
=======================================================================
|
||||
|
|
|
|||
|
|
@ -1,5 +1,5 @@
|
|||
#!/bin/cat
|
||||
$Id: FAQ.Big_Mailbox.txt,v 1.2 2018/07/25 10:37:30 gilles Exp gilles $
|
||||
$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/
|
||||
|
|
@ -10,24 +10,36 @@ 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?
|
||||
|
||||
R. 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 if it is doing something or just frozen, you can
|
||||
add option --debugimap. Option --debugimap will show what is
|
||||
currently done, it's quite a big output but it helps waiting,
|
||||
saying to ourself
|
||||
"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.
|
||||
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"
|
||||
|
||||
=====================================================================
|
||||
=====================================================================
|
||||
|
|
|
|||
|
|
@ -1,5 +1,5 @@
|
|||
#!/bin/cat
|
||||
$Id: FAQ.Dates.txt,v 1.10 2019/05/27 14:26:39 gilles Exp gilles $
|
||||
$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/
|
||||
|
|
@ -26,7 +26,11 @@ Q. We have found that the time and date displayed have been changed to
|
|||
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
|
||||
|
|
@ -37,9 +41,9 @@ but not with:
|
|||
First, a thing to keep in mind.
|
||||
|
||||
Imapsync does not touch any byte of messages unless told to do so by
|
||||
special options like --regexmess or --pipemess. Messages on both
|
||||
parts should be exactly identical because imapsync does a verbatim
|
||||
sync of all messages, by default.
|
||||
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.
|
||||
|
||||
|
|
|
|||
65
FAQ.d/FAQ.Docker.txt
Normal file
65
FAQ.d/FAQ.Docker.txt
Normal file
|
|
@ -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
|
||||
|
||||
|
||||
=======================================================================
|
||||
=======================================================================
|
||||
|
|
@ -1,5 +1,5 @@
|
|||
#!/bin/cat
|
||||
# $Id: FAQ.Domino.txt,v 1.10 2018/05/24 11:34:30 gilles Exp gilles $
|
||||
# $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/
|
||||
|
|
@ -10,9 +10,23 @@ 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. From Domino Notes to XXX
|
||||
Q. How to use imapsync from Domino Notes to XXX?
|
||||
|
||||
R1. Use --domino1, like this:
|
||||
|
||||
|
|
@ -30,7 +44,7 @@ On Unix use:
|
|||
imapsync ... --sep1 '\' --prefix1 '' --messageidnodomain
|
||||
|
||||
=======================================================================
|
||||
Q. From XXX to Domino Notes
|
||||
Q. How to use imapsync from XXX to Domino Notes
|
||||
|
||||
R1. Use --domino2, like this:
|
||||
|
||||
|
|
@ -89,6 +103,28 @@ For Domino 853FP6 on Linux, we used this command on Unix:
|
|||
--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!
|
||||
|
||||
=======================================================================
|
||||
|
|
|
|||
|
|
@ -1,5 +1,5 @@
|
|||
#!/bin/cat
|
||||
$Id: FAQ.Dovecot.txt,v 1.6 2018/05/24 11:34:30 gilles Exp gilles $
|
||||
$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/
|
||||
|
|
@ -11,6 +11,15 @@ https://imapsync.lamiral.info/FAQ.d/FAQ.Dovecot.txt
|
|||
=======================================================================
|
||||
|
||||
|
||||
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?
|
||||
|
||||
|
|
@ -21,5 +30,23 @@ R. Dovecot uses the same syntax as uw-imap
|
|||
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
|
||||
|
||||
|
||||
|
||||
=======================================================================
|
||||
=======================================================================
|
||||
|
|
@ -1,5 +1,5 @@
|
|||
|
||||
$Id: FAQ.Exchange.txt,v 1.50 2019/04/02 09:29:38 gilles Exp gilles $
|
||||
$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/
|
||||
|
|
@ -52,10 +52,6 @@ Q. From XXX to Exchange 2010/2013 or Office365 I get this error message
|
|||
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. Exchange and Office365 have throttle mechanisms to limit any huge
|
||||
usage. Sometimes imapsync transfers are too stressful for servers.
|
||||
How to deal with that?
|
||||
|
||||
Q. How to migrate from or to Exchange 2007/2010/2013 with an
|
||||
admin/authuser account?
|
||||
|
||||
|
|
@ -71,7 +67,10 @@ 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 Exchange2007?
|
||||
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?
|
||||
|
||||
|
|
@ -104,33 +103,37 @@ On Windows, use:
|
|||
|
||||
imapsync.exe ... --exchange2
|
||||
|
||||
or use (before imapsync release 1.836):
|
||||
which is equivalent in imapsync release 1.970 to:
|
||||
|
||||
imapsync.exe ... ^
|
||||
--maxsize 10000000 ^
|
||||
--maxsize 10_000_000 ^
|
||||
--maxmessagespersecond 4 ^
|
||||
--regexflag "s/\\Flagged//g" ^
|
||||
--disarmreadreceipts ^
|
||||
--regexmess "s,(.{9900}),$1\r\n,g"
|
||||
--regexflag "s/\\Flagged//g" ^
|
||||
--regexmess "s,(.{10239}),$1\r\n,g"
|
||||
|
||||
On Unix, use:
|
||||
|
||||
imapsync ... --exchange2
|
||||
|
||||
or use (before imapsync release 1.836):
|
||||
which is equivalent in imapsync release 1.970 to:
|
||||
|
||||
imapsync ... \
|
||||
--maxsize 10000000 \
|
||||
--maxlinelength 9900 \
|
||||
--maxsize 10_000_000 \
|
||||
--maxmessagespersecond 4 \
|
||||
--maxlinelength 10239 \
|
||||
--regexflag 's/\\Flagged//g' \
|
||||
--disarmreadreceipts \
|
||||
--maxlinelengthcmd 'reformime -r7'
|
||||
|
||||
On Linux, to get the "reformime" command, install the "maildrop" package.
|
||||
In case you don't have it you can still use
|
||||
--regexmess 's,(.{9900}),$1\r\n,g'
|
||||
instead of --maxlinelengthcmd 'reformime -r7'
|
||||
--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?
|
||||
|
|
@ -143,7 +146,12 @@ 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
|
||||
|
||||
|
|
@ -158,36 +166,27 @@ R. Here is a command line resume that solves most encountered issues when
|
|||
next Q/R sections.
|
||||
|
||||
|
||||
On Windows, use:
|
||||
|
||||
imapsync.exe ... --office2
|
||||
|
||||
or use (before imapsync release 1.836):
|
||||
imapsync.exe ... ^
|
||||
--maxsize 45000000 ^
|
||||
--maxmessagespersecond 2 ^
|
||||
--regexflag "s/\\Flagged//g" ^
|
||||
--disarmreadreceipts ^
|
||||
--regexmess "s,(.{10500}),$1\r\n,g"
|
||||
|
||||
On Unix, use:
|
||||
|
||||
imapsync ... --office2
|
||||
|
||||
or use (before imapsync release 1.836):
|
||||
which is equivalent to (in imapsync release 1.870):
|
||||
|
||||
imapsync ... \
|
||||
--host2 outlook.office365.com \
|
||||
--ssl2 \
|
||||
--maxsize 45000000 \
|
||||
--maxlinelength 10500 \
|
||||
--maxmessagespersecond 2 \
|
||||
--regexflag 's/\\Flagged//g' \
|
||||
--maxmessagespersecond 4 \
|
||||
--disarmreadreceipts \
|
||||
--maxlinelengthcmd 'reformime -r7'
|
||||
|
||||
On Linux, to get the "reformime" command, install the "maildrop" package.
|
||||
In case you don't have it you can use
|
||||
--regexmess 's,(.{10500}),$1\r\n,g'
|
||||
instead of --maxlinelengthcmd 'reformime -r7'
|
||||
--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
|
||||
|
|
@ -288,13 +287,23 @@ Q. Office365 throttles the sync and says:
|
|||
"Request is throttled. Suggested Backoff Time: 299961 milliseconds".
|
||||
What can I do with that?
|
||||
|
||||
R. To solve the throttles issues from 0365, there's two solutions:
|
||||
|
||||
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 been not enough competent to understand what you're
|
||||
talking about.
|
||||
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
|
||||
|
|
@ -308,6 +317,14 @@ R2. Play with options --maxbytespersecond or --maxmessagespersecond
|
|||
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://technet.microsoft.com/en-us/library/jj863577(v=exchg.150).aspx
|
||||
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?
|
||||
|
|
@ -323,6 +340,19 @@ 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.
|
||||
|
|
@ -455,7 +485,7 @@ 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.
|
||||
|
||||
If on Linux, there is a good Python script in the tarball that can
|
||||
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:
|
||||
|
|
@ -486,24 +516,6 @@ With STORE it sets and gets the "\Flagged" flag everywhere.
|
|||
Thanks to Dave Murray and Simon Savva for reporting and solving
|
||||
this issue.
|
||||
|
||||
======================================================================
|
||||
Q. Exchange and Office365 have throttle mechanisms to limit any huge
|
||||
usage. Sometimes imapsync transfers are too stressful for servers.
|
||||
How to deal with that?
|
||||
|
||||
R. It looks like limiting 4 messages per second is enough to avoid
|
||||
the throttle limits.
|
||||
|
||||
imapsync ... --maxmessagespersecond 4
|
||||
|
||||
In case throttle appears anyway, fix them with:
|
||||
https://technet.microsoft.com/en-us/library/jj863577(v=exchg.150).aspx
|
||||
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. How to migrate from or to Exchange 2007/2010/2013 with an
|
||||
admin/authuser account?
|
||||
|
|
@ -580,6 +592,22 @@ 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?
|
||||
|
||||
|
|
@ -690,7 +718,7 @@ 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 Exchange2007?
|
||||
Q. How to sync from any to Exchange 2007?
|
||||
|
||||
Several problems:
|
||||
- Big messages: increase the "send- and receive-connector"
|
||||
|
|
@ -701,13 +729,22 @@ 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 Exchange2007 with imapsync
|
||||
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?
|
||||
|
||||
|
|
|
|||
|
|
@ -1,5 +1,5 @@
|
|||
#!/bin/cat
|
||||
$Id: FAQ.Folders_Mapping.txt,v 1.19 2019/03/04 21:21:18 gilles Exp gilles $
|
||||
$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/
|
||||
|
|
@ -11,10 +11,24 @@ https://imapsync.lamiral.info/FAQ.d/FAQ.Folders_Mapping.txt
|
|||
Imapsync tips about changing folders names.
|
||||
=======================================================================
|
||||
|
||||
Folders names are by default reproduced identical except for
|
||||
the prefix and the separator which are automatically adapted
|
||||
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
|
||||
|
|
|
|||
|
|
@ -1,5 +1,5 @@
|
|||
#!/bin/cat
|
||||
$Id: FAQ.Folders_Selection.txt,v 1.7 2018/05/24 11:34:30 gilles Exp gilles $
|
||||
$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/
|
||||
|
|
@ -12,13 +12,17 @@ https://imapsync.lamiral.info/FAQ.d/FAQ.Folders_Selection.txt
|
|||
|
||||
By default, Imapsync syncs all folders, one by one, in alphanumeric order.
|
||||
|
||||
The IMAP protocol has a specific way to code folder names,
|
||||
when these names use non-ascii 7bit characters.
|
||||
Imapsync uses the same code as IMAP.
|
||||
In order to well specify them on the command line you will be
|
||||
helped by the complete folder list printed by imapsync at each run.
|
||||
The left column is what you have to use without the first enclosing
|
||||
square brackets, the right column is the human utf8 view.
|
||||
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.
|
||||
|
||||
|
||||
|
||||
|
|
|
|||
|
|
@ -1,5 +1,5 @@
|
|||
#!/bin/cat
|
||||
$Id: FAQ.Folders_Sizes.txt,v 1.2 2018/05/24 11:34:30 gilles Exp gilles $
|
||||
$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/
|
||||
|
|
@ -9,6 +9,15 @@ 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.
|
||||
|
||||
|
||||
=======================================================================
|
||||
|
|
@ -16,11 +25,54 @@ Q. How can I know the size of all folders before launching a sync?
|
|||
|
||||
R. Use --justfoldersizes option.
|
||||
|
||||
With --justfoldersizes option, imapsync displays the folder size
|
||||
part of a run and then exits without doing any transfer:
|
||||
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.
|
||||
|
||||
|
||||
=======================================================================
|
||||
=======================================================================
|
||||
|
||||
|
||||
65
FAQ.d/FAQ.GDPR.txt
Normal file
65
FAQ.d/FAQ.GDPR.txt
Normal file
|
|
@ -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.
|
||||
|
||||
=======================================================================
|
||||
=======================================================================
|
||||
|
|
@ -1,5 +1,5 @@
|
|||
#!/bin/cat
|
||||
# $Id: FAQ.General.txt,v 1.240 2018/11/26 11:49:56 gilles Exp gilles $
|
||||
# $Id: FAQ.General.txt,v 1.242 2019/12/11 20:28:33 gilles Exp gilles $
|
||||
|
||||
=======================================================================
|
||||
General FAQ for imapsync
|
||||
|
|
@ -57,8 +57,8 @@ 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
|
||||
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?
|
||||
|
|
@ -288,11 +288,11 @@ R. Add also --nofoldersizes since the default behavior is to compute
|
|||
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 --delete.
|
||||
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
|
||||
on host2 in a second run if you use a (silly) combination like:
|
||||
|
||||
imapsync ... --delete --noexpunge --noexpungeaftereach --expunge2
|
||||
imapsync ... --delete1 --noexpunge1 --noexpungeaftereach --expunge2
|
||||
|
||||
Notes about --useuid
|
||||
|
||||
|
|
|
|||
|
|
@ -1,5 +1,5 @@
|
|||
#!/bin/cat
|
||||
$Id: FAQ.Gmail.txt,v 1.58 2019/04/25 10:41:12 gilles Exp gilles $
|
||||
$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/
|
||||
|
|
@ -67,7 +67,18 @@ it has to be allowed in the Gmail configuration part:
|
|||
-> IMAP Access
|
||||
-> Enable IMAP
|
||||
|
||||
Also:
|
||||
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
|
||||
|
|
@ -75,6 +86,24 @@ it has to be allowed in the Gmail configuration part:
|
|||
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.
|
||||
|
|
@ -91,7 +120,7 @@ multiple messages and it doesn't match what imapsync presents.
|
|||
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 throttlers when
|
||||
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:
|
||||
|
|
@ -124,25 +153,30 @@ imapsync \
|
|||
--password2 gmailsecret2 \
|
||||
--gmail1 --gmail2
|
||||
|
||||
Or, replacing what does --gmail1 --gmail2 (values are from imapsync 1.882):
|
||||
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 \
|
||||
--maxsleep 2 \
|
||||
--automap \
|
||||
--exclude "\[Gmail\]$"
|
||||
--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
|
||||
imapsync ... --gmail1 --gmail2 --maxbytespersecond 50_000 --noautomap
|
||||
|
||||
Explanations:
|
||||
|
||||
|
|
@ -197,48 +231,40 @@ R. Use the following example:
|
|||
|
||||
imapsync --host1 mail.oldhost.com \
|
||||
--user1 my_email@oldhost.com \
|
||||
--password1 password \
|
||||
--password1 passwordold \
|
||||
--user2 my_email@gmail.com \
|
||||
--password2 password \
|
||||
--password2 gmailsecret \
|
||||
--gmail2
|
||||
|
||||
Or, replacing what does --gmail2 (values are from imapsync 1.921):
|
||||
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 password \
|
||||
--password1 passwordold \
|
||||
--host2 imap.gmail.com \
|
||||
--ssl2 \
|
||||
--user2 my_email@gmail.com \
|
||||
--password2 password \
|
||||
--password2 gmailsecret \
|
||||
--maxbytespersecond 20_000 \
|
||||
--maxbytesafter 1_000_000_000 \
|
||||
--automap \
|
||||
--expunge1 \
|
||||
--addheader \
|
||||
--maxsleep 2 \
|
||||
--maxsize 35_651_584 \
|
||||
--automap \
|
||||
--expunge1 \
|
||||
--addheader \
|
||||
--exclude "\[Gmail\]$" \
|
||||
--regextrans2 "s/['\^\"\\\\]/_/g" \
|
||||
--regextrans2 "s/[ ]+/_/g"
|
||||
--regextrans2 's,\[Gmail\].,,' \
|
||||
--regextrans2 's,^ +| +$,,g'
|
||||
--regextrans2 's,/ +| +/,/,g'
|
||||
--regextrans2 's/['"'"'\\^"]/_/g'
|
||||
--folderlast "[Gmail]/All Mail"
|
||||
|
||||
|
||||
Starting from imapsync 1.926 the last --regextrans2 replacing
|
||||
all blanks, which was:
|
||||
Starting from imapsync 1.926 a --regextrans2 replacing
|
||||
all blanks, was:
|
||||
|
||||
--regextrans2 "s/[ ]+/_/g"
|
||||
|
||||
became
|
||||
|
||||
on Winwows, like:
|
||||
|
||||
imapsync.exe ... --regexflag "s,\\Seen,," --regexflag "s,,\\Seen ,"
|
||||
|
||||
on Linux, like:
|
||||
|
||||
imapsync ... --regexflag 's,\\Seen,,' --regexflag 's,,\\Seen ,'
|
||||
|
||||
|
||||
|
||||
With --gmail2 you can override the parameters
|
||||
that are activated by them, for example:
|
||||
|
||||
|
|
@ -317,27 +343,30 @@ Q. How to synchronize from Gmail to XXX?
|
|||
R. Use this example:
|
||||
|
||||
imapsync \
|
||||
--user1 gilles.lamiral@gmail.com \
|
||||
--user1 foo@gmail.com \
|
||||
--password1 gmailsecret \
|
||||
--host2 localhost \
|
||||
--user2 tata \
|
||||
--gmail1
|
||||
|
||||
Or, replacing what does --gmail1 (values are from imapsync 1.882):
|
||||
Or, replacing what does --gmail1 (values are from imapsync 1.970):
|
||||
|
||||
imapsync \
|
||||
--host1 imap.gmail.com \
|
||||
--user1 gilles.lamiral@gmail.com \
|
||||
--ssl1 \
|
||||
--user1 foo@gmail.com \
|
||||
--password1 gmailsecret \
|
||||
--host2 localhost \
|
||||
--user2 tata \
|
||||
--password2 tatasecret \
|
||||
--maxbytespersecond 20_000 \
|
||||
--maxbytespersecond 40_000 \
|
||||
--maxbytesafter 2_500_000_000
|
||||
--automap \
|
||||
--maxsleep 2 \
|
||||
--skipcrossduplicates \
|
||||
--useheader="X-Gmail-Received" \
|
||||
--useheader "Message-Id" \
|
||||
--automap \
|
||||
--regextrans2 "s,\[Gmail\].,," \
|
||||
--skipcrossduplicates \
|
||||
--folderlast "[Gmail]/All Mail"
|
||||
|
||||
With --gmail1 you can override the parameters
|
||||
|
|
@ -347,10 +376,10 @@ imapsync ... --gmail1 --maxbytespersecond 50_000 --noskipcrossduplicates --noaut
|
|||
|
||||
Explanations:
|
||||
|
||||
--maxbytespersecond 20_000 ( 20 kBytes/s ) option is here to avoid
|
||||
--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 20_000 is not mandatory in the sense Gmail may
|
||||
--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.
|
||||
|
||||
|
|
@ -475,7 +504,7 @@ 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 bandwith and time,
|
||||
ends up with no duplicates on Gmail but a waste of bandwidth and time,
|
||||
which is the opposite goal of --usecache implied by --useuid.
|
||||
|
||||
|
||||
|
|
|
|||
|
|
@ -1,5 +1,5 @@
|
|||
#!/bin/cat
|
||||
$Id: FAQ.Kerio.txt,v 1.1 2019/06/26 22:14:50 gilles Exp gilles $
|
||||
$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/
|
||||
|
|
@ -37,4 +37,10 @@ Kerio at host2
|
|||
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
|
||||
|
||||
=======================================================================
|
||||
|
|
@ -1,5 +1,5 @@
|
|||
#!/bin/cat
|
||||
$Id: FAQ.Massive.txt,v 1.29 2019/06/18 16:38:06 gilles Exp gilles $
|
||||
$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/
|
||||
|
|
@ -45,8 +45,8 @@ R1. First you have to consider several periods. There is the global
|
|||
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 to launch the presyncs and watch until
|
||||
the round is finished.
|
||||
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
|
||||
|
|
@ -54,9 +54,11 @@ R1. First you have to consider several periods. There is the global
|
|||
|
||||
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.
|
||||
link bandwidth.
|
||||
It's a mean, measured upon various different syncs, coming from
|
||||
the online interface /X.
|
||||
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).
|
||||
|
|
@ -184,6 +186,9 @@ Here comes some measurements.
|
|||
|
||||
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,
|
||||
|
|
|
|||
|
|
@ -1,5 +1,5 @@
|
|||
#!/bin/cat
|
||||
$Id: FAQ.Messages_Selection.txt,v 1.14 2018/05/24 11:34:30 gilles Exp gilles $
|
||||
$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/
|
||||
|
|
@ -172,10 +172,34 @@ Q. What are the selection criteria available with --search option?
|
|||
|
||||
R. The list of search criteria are listed below, an excerpt from RFC3501.
|
||||
|
||||
http://www.faqs.org/rfcs/rfc3501.html
|
||||
|
||||
6.4.4. SEARCH Command
|
||||
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.
|
||||
|
|
@ -306,6 +330,89 @@ http://www.faqs.org/rfcs/rfc3501.html
|
|||
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.
|
||||
|
||||
=======================================================================
|
||||
=======================================================================
|
||||
|
||||
|
|
|
|||
56
FAQ.d/FAQ.Old_Style_Web_Design.txt
Normal file
56
FAQ.d/FAQ.Old_Style_Web_Design.txt
Normal file
|
|
@ -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)
|
||||
|
|
@ -1,5 +1,5 @@
|
|||
#!/bin/cat
|
||||
$Id: FAQ.OnlineUI.txt,v 1.19 2019/01/28 10:59:16 gilles Exp gilles $
|
||||
$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/
|
||||
|
|
@ -30,17 +30,17 @@ R0. Well, I don't know if asking the provider whether his online
|
|||
|
||||
R1. Some figures
|
||||
|
||||
Date of this report: 26 December 2018.
|
||||
Date of this report: 6 December 2019.
|
||||
|
||||
The online imapsync service /X started 9 January 2017
|
||||
(716 days of service).
|
||||
(1061 days of service).
|
||||
|
||||
In average, /X has 20 users per day lunching in mean 6
|
||||
different migrations, from one launch to many (hundreds).
|
||||
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 45 TiB in more
|
||||
than 111 thousands email imap migrations,
|
||||
157 millions email messages.
|
||||
The total volume /X transferred is around 101 TiB in more
|
||||
than 219 thousands email imap migrations,
|
||||
340 millions email messages.
|
||||
|
||||
R2. Pros & Cons
|
||||
|
||||
|
|
@ -54,23 +54,24 @@ 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.
|
||||
What is done with the source imap server host1 is independent
|
||||
of what is done with the destination imap server host2.
|
||||
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 26 December 2018, there is no security problem
|
||||
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.
|
||||
from the server side and take measure if the service suffers from
|
||||
your acts.
|
||||
|
||||
As the owner of the service, it could have been 48 000 pairs of
|
||||
credentials collected and nearly 17 terabytes of email messages.
|
||||
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 (by default)
|
||||
because too many imap servers are crappy configured regarding
|
||||
certificates.
|
||||
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
|
||||
|
|
@ -90,7 +91,7 @@ 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
|
||||
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!
|
||||
|
||||
|
|
@ -109,8 +110,8 @@ 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
|
||||
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.
|
||||
|
|
@ -126,8 +127,9 @@ 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 a same sync, it's safe, the /X will say, if any, that
|
||||
there is already a current sync running.
|
||||
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?).
|
||||
|
||||
|
||||
=====================================================================
|
||||
|
|
|
|||
|
|
@ -1,5 +1,5 @@
|
|||
#!/bin/cat
|
||||
$Id: FAQ.POP3.txt,v 1.3 2018/05/24 11:34:30 gilles Exp gilles $
|
||||
$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/
|
||||
|
|
@ -25,11 +25,12 @@ 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 (imap serves INBOX and several other folders,
|
||||
pop3 serves only INBOX).
|
||||
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.
|
||||
|
||||
=======================================================================
|
||||
|
|
@ -38,25 +39,80 @@ Q. How can I handle those terrible POP-leaving-a-copy users?
|
|||
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.
|
||||
|
||||
R. A discussion about this issue
|
||||
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.
|
||||
|
||||
Here is a better response to handle and fix this problem, I hope:
|
||||
If the pop mailboxes are known and known to be regularly fetched, then
|
||||
all the INBOX messages, or at least the "old" ones, can be moved in an
|
||||
subfolder INBOX_back. It requires to have "access" to the POP
|
||||
sessions. The POP server log file is usually enough to know which
|
||||
account opened a pop connection, and when.
|
||||
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."
|
||||
|
||||
=======================================================================
|
||||
=======================================================================
|
||||
|
|
|
|||
41
FAQ.d/FAQ.Principles.txt
Normal file
41
FAQ.d/FAQ.Principles.txt
Normal file
|
|
@ -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.
|
||||
|
||||
|
||||
=======================================================================
|
||||
=======================================================================
|
||||
|
|
@ -1,5 +1,5 @@
|
|||
#!/bin/cat
|
||||
$Id: FAQ.Release_Checklist.txt,v 1.11 2019/05/27 14:26:57 gilles Exp gilles $
|
||||
$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/
|
||||
|
|
@ -13,6 +13,7 @@ https://imapsync.lamiral.info/FAQ.d/FAQ.Release_Checklist.txt
|
|||
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.
|
||||
|
|
@ -20,15 +21,24 @@ Checklist before release a new release:
|
|||
- Read slowly README_Windows.txt
|
||||
- Read slowly the TUTORIAL_Unix file in html
|
||||
- Review the newsletter by running:
|
||||
m4 -P W/ml_announce.in
|
||||
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
|
||||
|
||||
|
|
|
|||
|
|
@ -1,5 +1,5 @@
|
|||
#!/bin/cat
|
||||
$Id: FAQ.SSL_errors.txt,v 1.7 2019/04/05 20:04:38 gilles Exp gilles $
|
||||
$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/
|
||||
|
|
@ -22,6 +22,9 @@ 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
|
||||
|
|
@ -76,7 +79,7 @@ R1. Use:
|
|||
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
|
||||
I quote the "SSL_version" section of
|
||||
https://metacpan.org/pod/IO::Socket::SSL (Module version: 2.066)
|
||||
|
||||
imapsync ... --sslargs1 SSL_version=SSLv2
|
||||
|
|
|
|||
|
|
@ -1,5 +1,5 @@
|
|||
#!/bin/cat
|
||||
$Id: FAQ.SmarterMail.txt,v 1.13 2019/06/20 10:11:21 gilles Exp gilles $
|
||||
$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/
|
||||
|
|
@ -17,12 +17,12 @@ 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 --noabletosearch1
|
||||
--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 --noabletosearch1
|
||||
--sep1 "/" --prefix1 "" --useheader Message-Id --noabletosearch
|
||||
|
||||
|
||||
=======================================================================
|
||||
|
|
@ -31,12 +31,12 @@ 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 --noabletosearch2
|
||||
--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 --noabletosearch2
|
||||
--sep2 "/" --prefix2 "" --useheader Message-Id --noabletosearch
|
||||
|
||||
|
||||
=======================================================================
|
||||
|
|
|
|||
|
|
@ -1,5 +1,5 @@
|
|||
|
||||
$Id: FAQ.Use_cache.txt,v 1.8 2018/10/22 17:30:45 gilles Exp gilles $
|
||||
$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/
|
||||
|
|
@ -12,6 +12,10 @@ https://imapsync.lamiral.info/FAQ.d/FAQ.Use_cache.txt
|
|||
|
||||
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"
|
||||
|
|
@ -19,8 +23,33 @@ Q. On Windows, with --useuid or --usecache a problem occurs with long
|
|||
Q. Inode problem with --usecache or --useuid on Linux
|
||||
|
||||
|
||||
Questions and their answers:
|
||||
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:
|
||||
|
|
|
|||
|
|
@ -1,5 +1,5 @@
|
|||
#!/bin/cat
|
||||
$Id: FAQ.Various_Software_Servers.txt,v 1.12 2019/06/26 22:17:03 gilles Exp gilles $
|
||||
$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/
|
||||
|
|
@ -85,16 +85,6 @@ R. By Jamie Neil:
|
|||
I eventually managed to get the mail to migrate without errors using the
|
||||
following options:
|
||||
|
||||
--sep1 /
|
||||
- doesn't report separator so has to be set explicitly.
|
||||
|
||||
--nosyncacls
|
||||
- doesn't support ACLs.
|
||||
|
||||
--skipheader '^Content-Type'
|
||||
- MIME separator IDs seem to change every time a mail is accessed so
|
||||
this is required to stop duplicates.
|
||||
|
||||
--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
|
||||
|
|
@ -112,16 +102,10 @@ something funny about the reported dates/sizes).
|
|||
|
||||
It think this problem has been rectified in GW6.5.
|
||||
|
||||
2) The "skipheader '^Content-Type'" directive is required to stop
|
||||
duplicate messages being created. GW seems to generate this field on
|
||||
the fly for messages that have MIME separators and so it's different
|
||||
every time.
|
||||
|
||||
3) Version 6.0.1 of the Groupwise Internet Connector sucks. I was
|
||||
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
|
||||
|
|
|
|||
|
|
@ -1,5 +1,5 @@
|
|||
|
||||
$Id: FAQ.Virus.txt,v 1.5 2018/05/24 11:34:30 gilles Exp gilles $
|
||||
$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/
|
||||
|
|
@ -14,9 +14,9 @@ https://imapsync.lamiral.info/FAQ.d/FAQ.Virus.txt
|
|||
Q. My virus scanner claims imapsync.exe is a virus/malware/trojan etc.
|
||||
What the hell?
|
||||
|
||||
R1. Yes, I found the same. Two antivirus, Baidu and Jiangmin, report that
|
||||
imapsync might have a trojan in it.
|
||||
All others virus scanner say imapsync.exe is ok.
|
||||
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/
|
||||
|
|
@ -35,12 +35,25 @@ 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. imapsync.exe release 1.836 is reported as totally clean by both
|
||||
|
||||
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
|
||||
|
||||
and https://metadefender.opswat.com/
|
||||
https://metadefender.opswat.com/results#!/file/ZTE4MDMxN1MxZTk4aGhxdEdCSlpxVTJoOVlN/regular/information
|
||||
|
||||
|
||||
|
||||
|
|
|
|||
|
|
@ -1,5 +1,5 @@
|
|||
#!/bin/cat
|
||||
$Id: FAQ.XOAUTH2.txt,v 1.15 2018/08/28 21:48:53 gilles Exp gilles $
|
||||
$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/
|
||||
|
|
@ -154,7 +154,8 @@ imapsync \
|
|||
|
||||
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?
|
||||
|
|
|
|||
26
FAQ.d/FAQ.Yandex.txt
Normal file
26
FAQ.d/FAQ.Yandex.txt
Normal file
|
|
@ -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
|
||||
|
|
@ -1,55 +1,62 @@
|
|||
|
||||
# $Id: htaccess.txt,v 1.25 2019/05/17 10:16:00 gilles Exp gilles $
|
||||
# $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>APPEND errors</b>." FAQ.Admin_Authentication.txt
|
||||
AddDescription "<b>Authenticate via an admin account</b>." FAQ.APPEND_errors.txt
|
||||
AddDescription "<b>Authentication failures</b>." FAQ.Authentication_failure.txt
|
||||
AddDescription "<b>Archiving</b> tips." FAQ.Archiving.txt
|
||||
AddDescription "<b>Big mailboxes</b> tips." FAQ.Big_Mailbox.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>." FAQ.David_Tobit.txt
|
||||
AddDescription "<b>Domino</b>." FAQ.Domino.txt
|
||||
AddDescription "<b>Dovecot</b>." 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>." FAQ.Exchange.txt
|
||||
AddDescription "<b>Changing folders names</b>." FAQ.Folders_Mapping.txt
|
||||
AddDescription "<b>Selecting folders</b>." FAQ.Folders_Selection.txt
|
||||
AddDescription "<b>Folders sizes with Imapsync</b>." FAQ.Folders_Sizes.txt
|
||||
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</b>." FAQ.Flags.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>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>Selecting messages</b>." FAQ.Messages_Selection.txt
|
||||
AddDescription "<b>How to transfer too big messages</b>." FAQ.Messages_Too_Big.txt
|
||||
AddDescription "<b>Oracle-UCS</b>." 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>." FAQ.SmarterMail.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>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>." FAQ.Yahoo.txt
|
||||
AddDescription "<b>Zimbra</b>." FAQ.Zimbra.txt
|
||||
AddDescription "<b>Where this Description column comes from</b>." htaccess.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
|
||||
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue