mirror of
https://github.com/imapsync/imapsync.git
synced 2025-06-10 22:54:33 +02:00
1.945
This commit is contained in:
Nick Bebout
parent
0797e48248
commit
275436c5a0
126 changed files with 25270 additions and 4380 deletions
|
|
@ -1,5 +1,5 @@
|
|||
#!/bin/cat
|
||||
$Id: FAQ.Admin_Authentication.txt,v 1.6 2018/09/09 10:58:16 gilles Exp gilles $
|
||||
$Id: FAQ.Admin_Authentication.txt,v 1.9 2019/06/26 22:16:43 gilles Exp gilles $
|
||||
|
||||
This documentation is also available online at
|
||||
https://imapsync.lamiral.info/FAQ.d/
|
||||
|
|
@ -11,30 +11,43 @@ 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 server software and its configuration.
|
||||
You have to figure out what is the imap software server,
|
||||
find out if it supports an admin account and how,
|
||||
if an admin account is actually configured and
|
||||
finally check an authentication via this admin account for
|
||||
a standard user.
|
||||
sometimes not. It depends on the imap software server and its configuration.
|
||||
|
||||
Known imap server software supporting imap admin authentication:
|
||||
You have to follow this road:
|
||||
* Determine what is the imap software server
|
||||
* Find out wether it supports an admin account or not
|
||||
* If no, leave this reading, take an handkerchief and cry
|
||||
* If yes, search how the imap software server supports
|
||||
an admin account (see below)
|
||||
* Figure out wether an admin account is actually configured or not,
|
||||
* If not then configure it,
|
||||
* Finally, check an imapsync authentication via this admin account for
|
||||
a standard user, option --justlogin is nice for doing this.
|
||||
* Use it for all users.
|
||||
* Next, read their email messages, enter their personnal life etc.
|
||||
I'm kidding.
|
||||
|
||||
* Exchange 2003/2007/2010/2013. See the file FAQ.Exchange.txt
|
||||
* Office365. See the file FAQ.Exchange.txt
|
||||
* Gmail. See the file FAQ.XOAUTH2.txt
|
||||
* Dovecot. See the file FAQ.Dovecot.txt
|
||||
* Zimbra. See the file FAQ.Zimbra.txt
|
||||
* UW-imap. See the file FAQ.General.txt
|
||||
Good luck!
|
||||
|
||||
Known imap software servers supporting imap admin authentication:
|
||||
|
||||
* Exchange 2003/2007/2010/2013/2016. See the file FAQ.Exchange.txt
|
||||
* Office365. See the file FAQ.Exchange.txt
|
||||
* Gmail. See the file FAQ.XOAUTH2.txt
|
||||
* Dovecot. See the file FAQ.Dovecot.txt
|
||||
* Zimbra. See the file FAQ.Zimbra.txt
|
||||
* Kerio See the file FAQ.Kerio.txt
|
||||
* UW-imap. See the file FAQ.General.txt
|
||||
* Cyrus-imap. See the file FAQ.General.txt
|
||||
* Sun Java Enterprise System/SunOne/iPlanet. See the file FAQ.General.txt
|
||||
|
||||
Known imap server software NOT supporting imap admin authentication:
|
||||
Known imap software servers NOT supporting imap admin authentication:
|
||||
|
||||
* Domino Lotus Notes.
|
||||
* SmartCloud Notes.
|
||||
* Domino Lotus Notes. See FAQ.Handkerchief.txt
|
||||
* SmartCloud Notes. Same joke.
|
||||
|
||||
=======================================================================
|
||||
=======================================================================
|
||||
|
|
|
|||
|
|
@ -1,5 +1,5 @@
|
|||
#!/bin/cat
|
||||
$Id: FAQ.Archiving.txt,v 1.13 2018/12/09 21:26:25 gilles Exp gilles $
|
||||
$Id: FAQ.Archiving.txt,v 1.14 2019/03/22 11:50:36 gilles Exp gilles $
|
||||
|
||||
This documentation is also available online at
|
||||
https://imapsync.lamiral.info/FAQ.d/
|
||||
|
|
@ -24,6 +24,8 @@ Q. Can imapsync be used to maintain a local offline copy of a
|
|||
ideally without requiring a second IMAP host?
|
||||
|
||||
|
||||
|
||||
https://imapsync.lamiral.info/FAQ.d/FAQ.Archiving.txt
|
||||
=======================================================================
|
||||
Q. Can I archive different accounts on the same destination account,
|
||||
each account on a separate folder?
|
||||
|
|
@ -37,15 +39,16 @@ R. Yes. Use --subfolder2
|
|||
|
||||
Example:
|
||||
|
||||
imapsync ... --user1 foo --subfolder2 foo
|
||||
imapsync ... --user1 Foo --subfolder2 FooArch
|
||||
|
||||
imapsync ... --user1 bar --subfolder2 bar
|
||||
imapsync ... --user1 Bar --subfolder2 BarArch
|
||||
|
||||
In case you need a strict sync, add --delete2 --delete2foldersonly "foo"
|
||||
(or "bar"), il will delete on account2 what is not on account1 but only
|
||||
in the right place, ie, the subfolder "foo".
|
||||
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 foo --delete2 --delete2foldersonly "foo"
|
||||
imapsync ... --user1 Foo --subfolder2 FooArch --delete2 --delete2foldersonly "FooArch"
|
||||
|
||||
=======================================================================
|
||||
Q. How to move emails from one IMAP folder to another either on the
|
||||
|
|
|
|||
|
|
@ -1,5 +1,5 @@
|
|||
#!/bin/cat
|
||||
$Id: FAQ.Contacts_Calendars.txt,v 1.11 2018/09/26 22:25:32 gilles Exp gilles $
|
||||
$Id: FAQ.Contacts_Calendars.txt,v 1.12 2019/04/30 13:04:18 gilles Exp gilles $
|
||||
|
||||
This documentation is also available online at
|
||||
https://imapsync.lamiral.info/FAQ.d/
|
||||
|
|
@ -26,21 +26,25 @@ R. No, Imapsync can't migrate Contacts and Calendars.
|
|||
events via IMAP. In other words, messages synced by imapsync from
|
||||
Calendars or Contacts folders are not used by email servers to set
|
||||
or get the contacts or calendars.
|
||||
No way via IMAP, no way via imapsync.
|
||||
So it's a good idea to avoid syncing contacts and calendars.
|
||||
But see the question below
|
||||
No way via IMAP, no way via imapsync.
|
||||
|
||||
So it's a good idea to avoid syncing contacts and calendars when
|
||||
using imapsync. See below
|
||||
"How can I avoid copying Calendar or Contacts folders?"
|
||||
|
||||
But see also the question at the end of this document
|
||||
"How can I copy or synchronize Calendars or Contacts?".
|
||||
|
||||
=======================================================================
|
||||
Q. Can I copy or sync Chat messages with imapsync?
|
||||
|
||||
R. No, Imapsync can't migrate Chat messages (those in GSuite for example)
|
||||
R. No, Imapsync can't migrate Chat messages (those in GSuite for example).
|
||||
The explanation is the same as with Calendars or Contacts.
|
||||
|
||||
=======================================================================
|
||||
Q. How can I avoid copying Calendar or Contacts folders?
|
||||
|
||||
R1. You can avoid synchronizing Calendar or Contacts folders with
|
||||
R. You can avoid synchronizing Calendar or Contacts folders with
|
||||
the --exclude option. First you have to search what is their
|
||||
exact name. The folders listing printed by imapsync at the
|
||||
beginning of a run will surely help to find their names.
|
||||
|
|
@ -48,6 +52,25 @@ R1. You can avoid synchronizing Calendar or Contacts folders with
|
|||
|
||||
imapsync ... --exclude "Calendar" --exclude "Contacts"
|
||||
|
||||
Be aware that this syntax will exclude all folders that have
|
||||
Calendar or Contacts in their names, as a substring,
|
||||
like "MyCalendarZ" or "TheContactsImDoneWith".
|
||||
Also, case matters: "calendar" does not match "Calendar".
|
||||
|
||||
To stritly avoid only "Calendar" or "Contacts" use
|
||||
the following
|
||||
|
||||
On windows:
|
||||
|
||||
imapsync ... --exclude "^Calendar$" --exclude "^Contacts$"
|
||||
|
||||
On Unix:
|
||||
|
||||
imapsync ... --exclude '^Calendar$' --exclude '^Contacts$'
|
||||
or
|
||||
imapsync ... --exclude "^Calendar\$" --exclude "^Contacts\$"
|
||||
|
||||
|
||||
=======================================================================
|
||||
Q. How can I copy or synchronize Calendars or Contacts?
|
||||
|
||||
|
|
|
|||
|
|
@ -1,5 +1,5 @@
|
|||
#!/bin/cat
|
||||
$Id: FAQ.Dates.txt,v 1.9 2018/11/04 09:27:17 gilles Exp gilles $
|
||||
$Id: FAQ.Dates.txt,v 1.10 2019/05/27 14:26:39 gilles Exp gilles $
|
||||
|
||||
This documentation is also available online at
|
||||
https://imapsync.lamiral.info/FAQ.d/
|
||||
|
|
@ -34,15 +34,17 @@ but not with:
|
|||
- Zimbra
|
||||
- Gmail
|
||||
|
||||
A first 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.
|
||||
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.
|
||||
|
||||
Now I explain the whole picture about dates of messages.
|
||||
|
||||
There are several different dates attached to any message.
|
||||
|
||||
First, there is the "Date:" header, which belongs to the message itself.
|
||||
You can see this "Date:" header line by asking "View->Message Source"
|
||||
in most email client software (Ctrl-u in Thunderbird).
|
||||
|
|
@ -52,37 +54,40 @@ MUA can be Outlook, Thunderbird, a webmail or Mutt etc.
|
|||
The "Date:" header is usually the date the message was written
|
||||
or sent the first time, at the writer side.
|
||||
This "Date:" header line is never changed by any transfer or copy.
|
||||
If an email reader uses the "Date:" header for displaying the date of a
|
||||
message then no problem should arise.
|
||||
|
||||
Another date is the internal date. In IMAP, the internal date is handled
|
||||
by the imap server and normally it corresponds to the arrival date in the mailbox.
|
||||
This date is not part of the email message itself, it's a metadata kept
|
||||
by the imap server.
|
||||
The IMAP protocol allows the internal date to be set by a email client
|
||||
If an email reader uses the "Date:" header for displaying the date of
|
||||
a message then no problem should arise.
|
||||
|
||||
Another date is the "internal date". In IMAP, the internal date is
|
||||
handled by the imap server and normally it corresponds to the arrival
|
||||
date in the mailbox. This date is not part of the email message
|
||||
itself, it is a metadata kept by the imap server.
|
||||
|
||||
The IMAP protocol allows the internal date to be set by an email client
|
||||
when a message is delivered by the imap APPEND command.
|
||||
Imapsync synchronizes these internal dates, by default, so internal dates
|
||||
on host2 should then be the same as the internal dates on host1.
|
||||
If an email reader uses the internal date for displaying the date of a
|
||||
message then the sync date problem only occurs when the host2 server software
|
||||
ignores the internal date given by imapsync during the APPEND imap
|
||||
command. It happens with some imap servers.
|
||||
|
||||
There are also the "Received:" header lines. Each time a message travels
|
||||
a SMTP server, this one adds a "Received:" header line. Sometimes
|
||||
some email clients use the last "Received:" header date as the date of the
|
||||
message. And some IMAP servers software add a "Received:" line after
|
||||
and imap transfer. If those both conditions are met then the date
|
||||
displayed become the transfer date even if imapsync
|
||||
If an email reader uses the internal date for displaying the date of a
|
||||
message then the sync date problem only occurs when the host2 imap
|
||||
server ignores the internal date given by imapsync during the APPEND
|
||||
imap command. It happens with some imap servers. Bad luck.
|
||||
|
||||
There are also the "Received:" header lines. Each time a message
|
||||
travels a SMTP server, this one adds a "Received:" header
|
||||
line. Sometimes some email clients use the last "Received:" header
|
||||
date as the date of the message. And some IMAP servers software add a
|
||||
"Received:" line after and imap transfer. If those both conditions are
|
||||
met then the date displayed become the transfer date even if imapsync
|
||||
has done its best to keep all the dates synchronized. Bad luck.
|
||||
|
||||
|
||||
Solutions:
|
||||
a) Use another email client or configure it in order that it sorts messages
|
||||
by sent dates, the "Date:" header line.
|
||||
by sent dates, the "Date:" header line.
|
||||
|
||||
b) Use a imap server that respects the imap RFC and accepts
|
||||
the internal date set by imapsync.
|
||||
the internal date set by imapsync.
|
||||
|
||||
c) Try to understand why the email client software shows another date
|
||||
than the "Date:" header line.
|
||||
|
|
|
|||
54
FAQ.d/FAQ.David_Tobit.txt
Normal file
54
FAQ.d/FAQ.David_Tobit.txt
Normal file
|
|
@ -0,0 +1,54 @@
|
|||
#!/bin/cat
|
||||
$Id: FAQ.David_Tobit.txt,v 1.4 2019/03/28 17:58:53 gilles Exp gilles $
|
||||
|
||||
This documentation is also available online at
|
||||
https://imapsync.lamiral.info/FAQ.d/
|
||||
https://imapsync.lamiral.info/FAQ.d/FAQ.David_Tobit.txt
|
||||
|
||||
|
||||
=======================================================================
|
||||
Imapsync tips for David Tobit imap server
|
||||
=======================================================================
|
||||
|
||||
|
||||
|
||||
=======================================================================
|
||||
Q. Migrating to David Tobit V12
|
||||
(Banner: "* OK IMAP4rev1 David.fx Mail Access Server MA-12.00a (0271)")
|
||||
|
||||
imapsync ... --sep2 / --create_folder_old
|
||||
|
||||
Thanks to Ludwig Behm
|
||||
|
||||
=======================================================================
|
||||
Q. Migrating from David Tobit V10 (DvISE Mail Access Server MA-...)
|
||||
|
||||
R. Use the following options:
|
||||
|
||||
imapsync ... --prefix1 "" --sep1 / --idatefromheader ^
|
||||
--nofoldersizes --useuid --nocheckmessageexists
|
||||
|
||||
=======================================================================
|
||||
Q. Migrating from David Tobit V8
|
||||
(Banner: "* OK IMAP4rev1 DvISE Mail Access Server MA-8.10a (0126)")
|
||||
|
||||
First try above V10 solution since improvments have been made
|
||||
to support Tobit.
|
||||
|
||||
R. Use the following options :
|
||||
|
||||
imapsync ... --prefix1 INBOX. --sep1 / --subscribe --subscribed
|
||||
|
||||
=======================================================================
|
||||
Q. Migrating from Tobit David Server 6
|
||||
(Banner: "* OK IMAP4rev1 DvISE Mail Access Server MA-6.60a (0118)")
|
||||
|
||||
First try above V10 solution since improvments have been made
|
||||
to support Tobit.
|
||||
|
||||
R. Look at the discussion:
|
||||
http://www.linux-france.org/prj/imapsync_list/msg00583.html
|
||||
http://www.linux-france.org/prj/imapsync_list/threads.html#00583
|
||||
patch saved in ./patches/imapsync-1.337_tobit_V6.patch
|
||||
|
||||
=======================================================================
|
||||
|
|
@ -1,5 +1,5 @@
|
|||
#!/bin/cat
|
||||
$Id: FAQ.Duplicates.txt,v 1.18 2019/02/14 17:22:10 gilles Exp gilles $
|
||||
$Id: FAQ.Duplicates.txt,v 1.20 2019/05/17 10:10:30 gilles Exp gilles $
|
||||
|
||||
This documentation is also available online at
|
||||
https://imapsync.lamiral.info/FAQ.d/
|
||||
|
|
@ -13,8 +13,9 @@ https://imapsync.lamiral.info/FAQ.d/FAQ.Duplicates.txt
|
|||
Q. How can I know if imapsync will generate duplicates on a second run?
|
||||
|
||||
R. To see if imapsync will generate duplicates on a second run, start
|
||||
a second run with --dry option added. imapsync will then show if it
|
||||
would mistakenly copy messages again, but without really copying them
|
||||
a second run with --dry option added. With --dry, imapsync will
|
||||
show whether it would mistakenly copy messages again, but without
|
||||
really copying them:
|
||||
|
||||
imapsync ... --dry
|
||||
|
||||
|
|
@ -35,7 +36,7 @@ Q: Multiple copies, duplicates, when I run imapsync twice ore more.
|
|||
|
||||
R0. First, some explanations to understand the issue.
|
||||
Normally and by default, imapsync doesn't generate duplicates.
|
||||
So if it does generate duplicates it means a problem occurs
|
||||
So, if it does generate duplicates it means a problem occurs
|
||||
with message identification. It happens sometimes with IMAP
|
||||
servers changing the "Message-Id" header line or one or more
|
||||
of the "Received:" header lines in the header part of messages.
|
||||
|
|
@ -66,7 +67,7 @@ don't go on, it means imapsync is still suffering to
|
|||
identify messages.
|
||||
|
||||
If you end with many messages skipped then it's very
|
||||
good and now you can safely resync the mailboxe
|
||||
good and now you can safely resync the mailbox
|
||||
and get rid of the dupplicates messages on host2 with:
|
||||
|
||||
imapsync ... --useheader "Message-Id" --delete2duplicates
|
||||
|
|
@ -80,7 +81,7 @@ to identify and compare messages in folders.
|
|||
Instead of some headers, --useuid tell imapsync to use
|
||||
the imap UIDs given by imap servers on both sides.
|
||||
To avoid duplicates on next runs, imapsync uses a local cache
|
||||
where it keeps UIDs already transfered.
|
||||
where it keeps UIDs already transferred.
|
||||
|
||||
imapsync ... --useuid
|
||||
|
||||
|
|
@ -95,11 +96,12 @@ A solution? Two solutions.
|
|||
The easiest is --delete2 if you are permitted to use it.
|
||||
Option --delete2 removes messages on host2
|
||||
that are not on host1. So, with --delete2 you go for resyncing all
|
||||
messages again but all previously transferred messages are deleted,
|
||||
but also messages previously there without imapsync.
|
||||
So --useuid --delete2 is easy to remove duplicates but not for
|
||||
all contexts. The host2 account must be considered as a strict
|
||||
replication of the host1 account, ie, not active.
|
||||
messages again. All previously transferred messages are deleted,
|
||||
but also messages previously there without imapsync.
|
||||
So --useuid --delete2 is an easy way to remove duplicates but it
|
||||
is not suitable in all contexts. The good context is that the host2
|
||||
account must be considered as a strict replication of the host1
|
||||
account, ie, host2 not active yet.
|
||||
|
||||
A second solution, better if R3 works (see R3 below), is to build
|
||||
the cache before using --useuid
|
||||
|
|
@ -191,8 +193,11 @@ R2. With option --useuid imapsync doesn't use headers to identify
|
|||
=======================================================================
|
||||
Q. How can I remove duplicates in a lone account?
|
||||
|
||||
R. Just run imapsync on the same account with option --delete2duplicates,
|
||||
ie, with host1 == host2, user1 == user2, password1 == password2
|
||||
R. In order to remove duplicates in a lone account, just run imapsync
|
||||
on the same account as source and destination, plus the
|
||||
option --delete2duplicates, ie, with
|
||||
host1 == host2, user1 == user2, password1 == password2
|
||||
|
||||
|
||||
=======================================================================
|
||||
=======================================================================
|
||||
|
|
|
|||
|
|
@ -1,9 +1,10 @@
|
|||
#!/bin/cat
|
||||
$Id: FAQ.Emptying.txt,v 1.6 2018/05/24 11:34:30 gilles Exp gilles $
|
||||
$Id: FAQ.Emptying.txt,v 1.8 2019/04/30 12:52:10 gilles Exp gilles $
|
||||
|
||||
This documentation is also available online at
|
||||
https://imapsync.lamiral.info/FAQ.d/
|
||||
https://imapsync.lamiral.info/FAQ.d/
|
||||
|
||||
https://imapsync.lamiral.info/FAQ.d/FAQ.Emptying.txt
|
||||
|
||||
=======================================================================
|
||||
Imapsync tip to empty an account.
|
||||
|
|
@ -12,27 +13,28 @@ https://imapsync.lamiral.info/FAQ.d/
|
|||
=======================================================================
|
||||
Q. How to delete all emails of all folders of an account with imapsync?
|
||||
|
||||
R. Use the same account on both sides with option --delete
|
||||
R. Use the same account on both sides with option --delete1
|
||||
--noexpungeaftereach
|
||||
|
||||
Option --noexpungeaftereach is just to speed up the deletion.
|
||||
Option --noexpungeaftereach is just to speed up the deletions.
|
||||
|
||||
Example:
|
||||
Example (real example):
|
||||
|
||||
./imapsync \
|
||||
--host1 test.lamiral.info --user1 test --password1 secret \
|
||||
--host2 test.lamiral.info --user2 test --password2 secret \
|
||||
--delete --noexpungeaftereach
|
||||
--host1 test.lamiral.info --user1 empty --password1 secret \
|
||||
--host2 test.lamiral.info --user2 empty --password2 secret \
|
||||
--delete1 --noexpungeaftereach
|
||||
|
||||
=======================================================================
|
||||
Q. How to delete all folders of an account with imapsync?
|
||||
|
||||
R. Use an already empty account as source and sync this account
|
||||
to the account you want to clear, with --delete2folders
|
||||
R. Use the same account on both sides with the options
|
||||
--delete1 --noexpungeaftereach --delete1emptyfolders
|
||||
|
||||
./imapsync ... --delete1 --noexpungeaftereach --delete1emptyfolders
|
||||
|
||||
Example:
|
||||
It won't delete the folder INBOX since INBOX is mandatory in imap.
|
||||
|
||||
./imapsync ... --delete2folders --foldersizes
|
||||
|
||||
=======================================================================
|
||||
=======================================================================
|
||||
|
|
|
|||
|
|
@ -1,5 +1,5 @@
|
|||
|
||||
$Id: FAQ.Exchange.txt,v 1.49 2018/12/03 23:09:28 gilles Exp gilles $
|
||||
$Id: FAQ.Exchange.txt,v 1.50 2019/04/02 09:29:38 gilles Exp gilles $
|
||||
|
||||
This documentation is also available online at
|
||||
https://imapsync.lamiral.info/FAQ.d/
|
||||
|
|
@ -455,6 +455,15 @@ 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
|
||||
fix several things that Exchange or O365 have issues with.
|
||||
|
||||
Use it like this:
|
||||
|
||||
./imapsync ... --pipemess W/tools/fix_email_for_exchange.py
|
||||
|
||||
It often does some miracles on messages.
|
||||
|
||||
=======================================================================
|
||||
Q. From XXX to Exchange 2010 or 2013 or Office365 the flag Flagged does
|
||||
not seem to be well synced. What can I do?
|
||||
|
|
|
|||
|
|
@ -1,5 +1,5 @@
|
|||
#!/bin/cat
|
||||
$Id: FAQ.Flags.txt,v 1.20 2019/02/14 16:01:41 gilles Exp gilles $
|
||||
$Id: FAQ.Flags.txt,v 1.21 2019/03/08 19:04:32 gilles Exp gilles $
|
||||
|
||||
This documentation is also available online at
|
||||
https://imapsync.lamiral.info/FAQ.d/
|
||||
|
|
@ -149,22 +149,22 @@ Add the \Seen flag to all messages like this:
|
|||
|
||||
On Winwows:
|
||||
|
||||
imapsync.exe ... --regexflag "s,^((?!\\Seen)).*$,$1 \\Seen,"
|
||||
imapsync.exe ... --regexflag "s,\\Seen,," --regexflag "s,,\\Seen ,"
|
||||
|
||||
On Unix:
|
||||
|
||||
imapsync ... --regexflag 's,\\Seen,,' --regexflag 's,,\\Seen ,'
|
||||
|
||||
R2. You can also filter with --search1 UNSEEN and use only one
|
||||
of the regexes:
|
||||
|
||||
On Unix:
|
||||
|
||||
imapsync ... --regexflag 's,^((?!\\Seen)).*$,$1 \\Seen,'
|
||||
|
||||
R2. You can also filter with --search1 UNSEEN and use a simpler
|
||||
regex:
|
||||
imapsync ... --search1 UNSEEN --regexflag 's,,\\Seen ,'
|
||||
|
||||
On Winwows:
|
||||
|
||||
imapsync.exe ... --search1 UNSEEN --regexflag "s/(.*)/$1 \\Seen/"
|
||||
|
||||
On Unix:
|
||||
|
||||
imapsync ... --search1 UNSEEN --regexflag 's/(.*)/$1 \\Seen/'
|
||||
imapsync.exe ... --search1 UNSEEN --regexflag "s,,\\Seen ,"
|
||||
|
||||
R3. Fix it on the server Exchange:
|
||||
Google translate:
|
||||
|
|
|
|||
|
|
@ -1,5 +1,5 @@
|
|||
#!/bin/cat
|
||||
$Id: FAQ.Folders_Mapping.txt,v 1.17 2018/11/20 10:26:18 gilles Exp gilles $
|
||||
$Id: FAQ.Folders_Mapping.txt,v 1.19 2019/03/04 21:21:18 gilles Exp gilles $
|
||||
|
||||
This documentation is also available online at
|
||||
https://imapsync.lamiral.info/FAQ.d/
|
||||
|
|
@ -39,16 +39,17 @@ Things to know and understand before playing with --regextrans2
|
|||
*) --regextrans2 is used to transform folders names.
|
||||
|
||||
*) --regextrans2 applies after the default
|
||||
inversion prefix1 <-> prefix2 and sep1 <-> sep2
|
||||
So when elaborating the regex you should focus on
|
||||
inversion prefix1 <-> prefix2 and sep1 <-> sep2.
|
||||
So, when elaborating the regex you should focus on
|
||||
the right part of the default mapping printed by
|
||||
imapsync, the part showing the host2 folder name.
|
||||
The section to look at is within the folder loop:
|
||||
The section to look at is either the folder size section
|
||||
or within the folder loop located "Here" between the lines
|
||||
++++ Looping on each folder
|
||||
Here
|
||||
++++ End looping on each folder
|
||||
|
||||
*) Several --regextrans2 is possible, they will be applied in the order
|
||||
|
||||
*) Several --regextrans2 are possible, they will be applied in the order
|
||||
of the command line, each one on the result of the previous one.
|
||||
|
||||
*) --regextrans2 uses Perl regex mechanism so it may be hard to master
|
||||
|
|
@ -61,18 +62,19 @@ Here
|
|||
|
||||
On Linux/Unix use single quotes ' around the regex string, it is
|
||||
easier to get what we want with single quotes since the shell
|
||||
won't change the inner string. Like --regextrans2 'myregex'
|
||||
won't change the inner string. Use --regextrans2 'myregex'
|
||||
|
||||
*) Good method to elaborate any --regextrans2 string
|
||||
|
||||
First, elaborate the --regextrans2 string with --dry --justfolders options.
|
||||
|
||||
imapsync ... --dry --justfolders
|
||||
imapsync ... --dry --justfolders
|
||||
|
||||
With --dry imapsync shows the transformations it will do without
|
||||
really doing them, --dry is the "do nothing" mode.
|
||||
With --justfolders imapsync will work only with folders,
|
||||
messages won't be taken into account, so it will be fast.
|
||||
messages won't be taken into account, so it will be fast
|
||||
and focused on the folders names.
|
||||
|
||||
When the output shows what you expect imapsync to do with folders
|
||||
names, you can remove the --dry option. Keep the --justfolders
|
||||
|
|
@ -106,50 +108,13 @@ Examples:
|
|||
|
||||
2b) To sync a complete account in a subfolder called FOO
|
||||
|
||||
Since imapsync release 1.641 simply use
|
||||
With imapsync release 1.641 and former, simply use
|
||||
|
||||
imapsync ... --subfolder2 FOO
|
||||
|
||||
Next examples are subfolder solutions for any release.
|
||||
Examples to this subfolder problem for any release
|
||||
can be seen below, in another Q/R section.
|
||||
|
||||
a) Separator is dot character "." and "INBOX" prefixes every folder
|
||||
|
||||
On Linux/Unix:
|
||||
|
||||
--regextrans2 's,^INBOX(.*),INBOX.FOO$1,'
|
||||
|
||||
On Windows:
|
||||
|
||||
--regextrans2 "s,^INBOX(.*),INBOX.FOO$1,"
|
||||
|
||||
or:
|
||||
|
||||
b) Separator is the slash character "/" and there is no prefix
|
||||
|
||||
On Linux/Unix:
|
||||
|
||||
--regextrans2 's,(.*),FOO/$1,'
|
||||
|
||||
On Windows:
|
||||
|
||||
--regextrans2 "s,(.*),FOO/$1,"
|
||||
|
||||
or:
|
||||
|
||||
c) Any separator, any prefix solution, FOO is the subfolder:
|
||||
|
||||
It is a complicated line because every case is taken into account.
|
||||
Type it in one line (or with the \ at the end of first line on Unix shells.
|
||||
|
||||
On Linux/Unix:
|
||||
|
||||
--regextrans2 's,${h2_prefix}(.*),${h2_prefix}FOO${h2_sep}$1,' \
|
||||
--regextrans2 's,^INBOX$,${h2_prefix}FOO${h2_sep}INBOX,'
|
||||
|
||||
On Windows:
|
||||
|
||||
--regextrans2 "s,${h2_prefix}(.*),${h2_prefix}FOO${h2_sep}$1," ^
|
||||
--regextrans2 "s,^INBOX$,${h2_prefix}FOO${h2_sep}INBOX,"
|
||||
|
||||
3) to substitute all characters dot "." by underscores "_"
|
||||
--regextrans2 "s,\.,_,g"
|
||||
|
|
@ -164,8 +129,7 @@ On Windows:
|
|||
|
||||
--regextrans2 s,\^",_,g
|
||||
|
||||
3c) to substitute all characters *%. by underscores _
|
||||
You can increase the *%. list by any unwanted character.
|
||||
3c) to substitute all characters * % . and # by underscores _
|
||||
|
||||
On Linux/Unix:
|
||||
|
||||
|
|
@ -175,11 +139,13 @@ On Windows:
|
|||
|
||||
--regextrans2 "tr,*%.#,_,"
|
||||
|
||||
You can increase the *%.# list by any unwanted character,
|
||||
plus, the order doesn't count. See 3d) for &
|
||||
|
||||
3d) It is a bad idea to substitute & characters since &
|
||||
is a character to encode non-ascii characters in IMAP folder names.
|
||||
|
||||
|
||||
|
||||
4) to change folder names like this:
|
||||
[mail/Sent Items] -> [Sent]
|
||||
[mail/Test] -> [INBOX/Test]
|
||||
|
|
@ -214,39 +180,26 @@ to folder INBOX only on host2:
|
|||
4) Remove --justfolders
|
||||
|
||||
|
||||
======================================================================
|
||||
Q. I have moved from Braunschweig to Graz, so I would like to have my
|
||||
whole Braunschweig mail sorted into a sub-folder INBOX.Braunschweig
|
||||
of my new mail account.
|
||||
|
||||
R.
|
||||
1) First try (safe mode):
|
||||
|
||||
imapsync \
|
||||
...
|
||||
--regextrans2 "s/INBOX(.*)/INBOX.Braunschweig\$1/" \
|
||||
--dry --justfolders
|
||||
|
||||
On Windows, in the previous example containing \$1 you have to
|
||||
replace the two \$1 by $1 (remove the \ before $).
|
||||
|
||||
|
||||
2) See if the output says everything you want imapsync to do,
|
||||
--dry option is safe and does nothing real.
|
||||
|
||||
3) Remove --dry
|
||||
Check the imap folder tree on the target side
|
||||
|
||||
4) Remove --justfolders
|
||||
|
||||
=======================================================================
|
||||
Q. I would like to move emails from InBox to a sub-folder called,
|
||||
say "2010-INBOX" based on the date (Like all emails received in the
|
||||
Year 2010 should be moved to the folder called "2010-INBOX").
|
||||
say "2010-INBOX" based on the date. Like all emails received in the
|
||||
year 2010 should be moved to the folder called "2010-INBOX".
|
||||
|
||||
R. 2 ways :
|
||||
|
||||
a) Manually:
|
||||
a) With imapsync:
|
||||
-----------------
|
||||
|
||||
imapsync ... \
|
||||
--search "SENTSINCE 1-Jan-2010 SENTBEFORE 31-Dec-2010"
|
||||
--f1f2 "INBOX=2010-INBOX" \
|
||||
--folder INBOX
|
||||
|
||||
See also the FAQ FAQ.Messages_Selection.txt
|
||||
https://imapsync.lamiral.info/FAQ.d/FAQ.Messages_Selection.txt
|
||||
to get more examples about how to select messages.
|
||||
|
||||
b) Manually:
|
||||
------------
|
||||
|
||||
1) You create a folder INBOX.2010-INBOX
|
||||
|
|
@ -257,13 +210,58 @@ a) Manually:
|
|||
|
||||
3) Cut/paste in INBOX.2010-INBOX
|
||||
|
||||
b) With imapsync:
|
||||
-----------------
|
||||
|
||||
imapsync ... \
|
||||
--search 'SENTSINCE 1-Jan-2010 SENTBEFORE 31-Dec-2010'
|
||||
--regextrans2 's/^INBOX$/INBOX.2010-INBOX/' \
|
||||
--folder INBOX
|
||||
|
||||
=======================================================================
|
||||
Q. How to sync a complete account in a subfolder called FOO,
|
||||
the hard way.
|
||||
|
||||
R0. See the easy above using --subfolder2
|
||||
|
||||
R1. Several ways to do it.
|
||||
|
||||
a) Separator is dot character "." and "INBOX" prefixes every folder
|
||||
|
||||
On Linux/Unix:
|
||||
|
||||
--regextrans2 's,^INBOX(.*),INBOX.FOO$1,'
|
||||
|
||||
On Windows:
|
||||
|
||||
--regextrans2 "s,^INBOX(.*),INBOX.FOO$1,"
|
||||
|
||||
or:
|
||||
|
||||
b) Separator is the slash character "/" and there is no prefix
|
||||
|
||||
On Linux/Unix:
|
||||
|
||||
--regextrans2 's,(.*),FOO/$1,'
|
||||
|
||||
or with doublequotes
|
||||
|
||||
--regextrans2 "s,(.*),FOO/\$1,"
|
||||
|
||||
On Windows:
|
||||
|
||||
--regextrans2 "s,(.*),FOO/$1,"
|
||||
|
||||
or:
|
||||
|
||||
c) Any separator, any prefix solution, FOO is the subfolder:
|
||||
|
||||
It is a complicated line because every case is taken into account.
|
||||
Type it in one line (or with the \ at the end of first line on Unix shells.
|
||||
|
||||
On Linux/Unix:
|
||||
|
||||
--regextrans2 's,${h2_prefix}(.*),${h2_prefix}FOO${h2_sep}$1,' \
|
||||
--regextrans2 's,^INBOX$,${h2_prefix}FOO${h2_sep}INBOX,'
|
||||
|
||||
On Windows:
|
||||
|
||||
--regextrans2 "s,${h2_prefix}(.*),${h2_prefix}FOO${h2_sep}$1," ^
|
||||
--regextrans2 "s,^INBOX$,${h2_prefix}FOO${h2_sep}INBOX,"
|
||||
|
||||
|
||||
=======================================================================
|
||||
=======================================================================
|
||||
|
|
|
|||
|
|
@ -1,5 +1,5 @@
|
|||
#!/bin/cat
|
||||
$Id: FAQ.Gmail.txt,v 1.51 2019/02/18 09:49:14 gilles Exp gilles $
|
||||
$Id: FAQ.Gmail.txt,v 1.58 2019/04/25 10:41:12 gilles Exp gilles $
|
||||
|
||||
This document is also available online at
|
||||
https://imapsync.lamiral.info/FAQ.d/
|
||||
|
|
@ -67,6 +67,14 @@ it has to be allowed in the Gmail configuration part:
|
|||
-> IMAP Access
|
||||
-> Enable IMAP
|
||||
|
||||
Also:
|
||||
|
||||
-> Verify 2-step verification is OFF
|
||||
https://myaccount.google.com/security?hl=en&pli=1&nlr=1#signin
|
||||
-> Turn ON "Access for less secure apps"
|
||||
https://www.google.com/settings/security/lesssecureapps
|
||||
https://support.google.com/accounts/answer/6010255?hl=en
|
||||
|
||||
=======================================================================
|
||||
Q. Even after several syncs the number of messages differs
|
||||
largely between imapsync and the Gmail web interface.
|
||||
|
|
@ -89,10 +97,10 @@ R. Basically it takes X days to transfer X GB per account.
|
|||
From the previous link:
|
||||
|
||||
* it's 2X days to upload X GB to Gmail, it's why I suggest to add
|
||||
--maxbytespersecond 10000
|
||||
--maxbytespersecond 10000 --maxbytesafter 1_000_000_000
|
||||
for uploading messages to Gmail
|
||||
* it's X/2 days to download X BG from Gmail, it's why I suggest to add
|
||||
--maxbytespersecond 20000
|
||||
--maxbytespersecond 20000 --maxbytesafter 1_000_000_000
|
||||
for downloading messages from Gmail
|
||||
|
||||
That's theoretical values that always work in practice. Try
|
||||
|
|
@ -192,9 +200,9 @@ imapsync --host1 mail.oldhost.com \
|
|||
--password1 password \
|
||||
--user2 my_email@gmail.com \
|
||||
--password2 password \
|
||||
--gmail2 --maxsize 35_651_584
|
||||
--gmail2
|
||||
|
||||
Or, replacing what does --gmail2 (values are from imapsync 1.882):
|
||||
Or, replacing what does --gmail2 (values are from imapsync 1.921):
|
||||
|
||||
imapsync --host1 mail.oldhost.com \
|
||||
--user1 my_email@oldhost.com \
|
||||
|
|
@ -209,9 +217,27 @@ imapsync --host1 mail.oldhost.com \
|
|||
--automap \
|
||||
--expunge1 \
|
||||
--addheader \
|
||||
--exclude "\[Gmail\]$" \
|
||||
--regextrans2 "s/[ ]+/_/g" \
|
||||
--regextrans2 "s/['\^\"\\\\]/_/g"
|
||||
--exclude "\[Gmail\]$" \
|
||||
--regextrans2 "s/['\^\"\\\\]/_/g" \
|
||||
--regextrans2 "s/[ ]+/_/g"
|
||||
|
||||
|
||||
Starting from imapsync 1.926 the last --regextrans2 replacing
|
||||
all blanks, which 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:
|
||||
|
|
@ -438,9 +464,10 @@ R. No.
|
|||
using the IMAP protocol.
|
||||
|
||||
=======================================================================
|
||||
Q. Can I safely use --useuid for Gmail transfers?
|
||||
Q. Can I safely use --useuid or --usecache for Gmail transfers?
|
||||
|
||||
R. Yes, but I suggest to not use --useuid for Gmail transfers.
|
||||
R. Yes, but I suggest to not use --useuid nor --usecache
|
||||
for Gmail transfers.
|
||||
|
||||
Using UIDs is useless with Gmail in the case of global duplicates
|
||||
(duplicates across different folders). Gmail always accept a global
|
||||
|
|
@ -546,7 +573,6 @@ xxx sub-folders show up nested within xxx/xxx.
|
|||
Q. How to migrate email from gmail to google apps?
|
||||
|
||||
R. Take a look at:
|
||||
http://www.linux-france.org/prj/imapsync_list/msg00639.html
|
||||
|
||||
http://biasecurities.com/2009/02/migrate-email-from-gmail-to-google-apps/
|
||||
http://www.thamtech.com/blog/2008/03/29/gmail-to-google-apps-email-migration/
|
||||
|
|
|
|||
40
FAQ.d/FAQ.Kerio.txt
Normal file
40
FAQ.d/FAQ.Kerio.txt
Normal file
|
|
@ -0,0 +1,40 @@
|
|||
#!/bin/cat
|
||||
$Id: FAQ.Kerio.txt,v 1.1 2019/06/26 22:14:50 gilles Exp gilles $
|
||||
|
||||
This document is also available online at
|
||||
https://imapsync.lamiral.info/FAQ.d/
|
||||
https://imapsync.lamiral.info/FAQ.d/FAQ.Kerio.txt
|
||||
|
||||
=======================================================================
|
||||
Imapsync tips for Kerio accounts.
|
||||
=======================================================================
|
||||
|
||||
|
||||
|
||||
|
||||
=======================================================================
|
||||
Q. How to migrate from Kerio Connect to XXX
|
||||
|
||||
R. No special options required.
|
||||
See also:
|
||||
http://www.linux-france.org/prj/imapsync_list/msg01756.html
|
||||
http://web.archive.org/web/20140224041102/https://www.safetynet-it.com/it-support/mac-kerio-server-to-microsoft-exchange-2010-migration-1/
|
||||
http://web.archive.org/web/20121125074756/http://www.safetynet-it.com/it-support/mac-kerio-server-to-microsoft-exchange-2010-migration-2/
|
||||
|
||||
=======================================================================
|
||||
Q. How to use Kerio master authentication with imapsync?
|
||||
|
||||
R. Example:
|
||||
|
||||
Kerio at host1
|
||||
|
||||
imapsync ... --user1 USERNAME --password1 MASTERPASSWORD --authmech1 X-MASTERAUTH
|
||||
|
||||
Kerio at host2
|
||||
|
||||
imapsync ... --user2 USERNAME --password2 MASTERPASSWORD --authmech2 X-MASTERAUTH
|
||||
|
||||
See also:
|
||||
https://github.com/imapsync/imapsync/pull/53
|
||||
|
||||
=======================================================================
|
||||
|
|
@ -1,5 +1,5 @@
|
|||
#!/bin/cat
|
||||
$Id: FAQ.Massive.txt,v 1.24 2018/12/30 21:28:03 gilles Exp gilles $
|
||||
$Id: FAQ.Massive.txt,v 1.29 2019/06/18 16:38:06 gilles Exp gilles $
|
||||
|
||||
This document is also available online at
|
||||
https://imapsync.lamiral.info/FAQ.d/
|
||||
|
|
@ -29,18 +29,46 @@ Q. I run multiple imapsync applications at the same time then get a
|
|||
IMAP account in parallel?
|
||||
|
||||
=======================================================================
|
||||
Q. How long will take the whole migration?
|
||||
Q. How long will take the whole migration?
|
||||
|
||||
R. Consider the mean imapsync transfer rate to be around 340 Kbytes/s,
|
||||
ie, 2.8 Mbps, no matter the local link bandwidth.
|
||||
It's a mean, measured upon various different syncs, coming from
|
||||
the online interface /X.
|
||||
|
||||
With 1 TB to transfer and one sync at a time it will end in 35 days.
|
||||
At 10 transfers at a time, 1 TB will take 3.5 days.
|
||||
Double the time because best scenario never happens.
|
||||
Triple because, well, real world is like that.
|
||||
R1. First you have to consider several periods. There is the global
|
||||
period, from when the migration process is decided to the final end
|
||||
where all mailboxes are migrated. This global period can be divided
|
||||
into three smaller periods.
|
||||
|
||||
The first period is the analyse period: you play with the tools
|
||||
available, you estimate the volume to be transferred, the number of
|
||||
accounts, you measure how long it takes for one account under
|
||||
your context.
|
||||
|
||||
The second period is the presync period. The users are still using
|
||||
the old accounts but nothing prevents you from starting to sync
|
||||
the old accounts, as they are, to the new accounts.
|
||||
With tons of gigabytes to transfer, this period may be the longest one.
|
||||
There is nothing more to launch the presyncs and watch until
|
||||
the round is finished.
|
||||
|
||||
The last period is the final sync period where only the last
|
||||
changes of the mailboxes need to be synced in order to switch
|
||||
the users to their new mailboxes.
|
||||
|
||||
R2. To estimate the presync period, consider the mean imapsync transfer
|
||||
rate to be around 340 Kbytes/s, ie, 2.8 Mbps, no matter the local
|
||||
link bandwidth.
|
||||
It's a mean, measured upon various different syncs, coming from
|
||||
the online interface /X.
|
||||
|
||||
At 340 Kbytes/s,
|
||||
1 TB to transfer and one sync at a time will end in 35 days (1024^3/340/3600/24).
|
||||
At 10 transfers at a time, 1 TB will take 3.5 days.
|
||||
At 100 transfers at a time, 1 TB will take 8 hours.
|
||||
Double the time because the best scenario never happens.
|
||||
Triple the time because, well, real world is like that.
|
||||
|
||||
R3. To estimate the last period, just rerun a complete presync,
|
||||
ie, resync all the mailboxes, the final sync should take
|
||||
the same amount of time.
|
||||
|
||||
=======================================================================
|
||||
Q. I need to migrate hundred accounts, how can I do?
|
||||
|
||||
|
|
@ -119,43 +147,43 @@ of sync_loop_windows.bat
|
|||
Q. I have to migrate 500k users using 400 TB of disk space.
|
||||
How do I proceed? How about speed?
|
||||
|
||||
R. Solution to this issue is two words: parallelism and measurements.
|
||||
R. A good solution to this issue is two words: parallelism and measurements.
|
||||
|
||||
Since all mailboxes are functionnaly independent, they can be processed
|
||||
independently, here comes parallelism, lunching several imapsync
|
||||
independently, here comes the parallelism, ie, lunching several imapsync
|
||||
processes in parallel.
|
||||
|
||||
Meanwhile, mailboxes usually belong to the same server and syncs
|
||||
Meanwhile, mailboxes usually belong to the same server and the syncs
|
||||
share the same imapsync host via the same bandwidth, here come
|
||||
some limitations and bottlenecks.
|
||||
|
||||
How many syncs can we run in parallel? here comes measurements.
|
||||
How many syncs can we run in parallel in your context?
|
||||
Here comes some measurements.
|
||||
|
||||
1) Measure the total transfer rate by adding each one printed in each run.
|
||||
Since adding this way is not so easy, just look at the overall
|
||||
network rate of the imapsync host.
|
||||
|
||||
On Linux and FreeBSD, nload is a good candidate to measure this overall
|
||||
network rate, every 6 seconds (-t 6000), on eth0 or em0 interface,
|
||||
values in Kbytes (-u K):
|
||||
network rate. For example, to measure the rate every 6 seconds (-t 6000),
|
||||
on eth0 or em0 interface, with values in Kbytes (-u K), use:
|
||||
|
||||
nload -t 6000 eth0 -u K # Linux
|
||||
nload -t 6000 em0 -u K # FreeBSD
|
||||
|
||||
During nload, press the h to see the display commands available,
|
||||
every single feature is useful! Press h again and try each one.
|
||||
|
||||
On Linux only, another very good network tool is dstat:
|
||||
|
||||
dstat -n -N eth0 6 # Linux only (in 2018)
|
||||
|
||||
A excellent tool for this purpose is iftop, the following
|
||||
command will monitor imap and imaps connexions
|
||||
Another excellent tool to measure the network trafic is iftop.
|
||||
The following command will monitor imap and imaps connexions
|
||||
on interfce eth0, only them, and sum them up:
|
||||
|
||||
iftop -i eth0 -f 'port imap or port imaps' -B # Linux
|
||||
iftop -i em0 -f 'port imap or port imaps' -B # FreeBSD
|
||||
|
||||
During iftop, press the h to see the display commands available,
|
||||
every single feature is useful! Press h again and try each one.
|
||||
|
||||
|
||||
On Windows 8.1 Windows 10 Windows 2012 R2 Windows 2016,
|
||||
|
|
@ -232,9 +260,11 @@ Possible bottlenecks:
|
|||
|
||||
|
||||
- RAM memory.
|
||||
On all sides, monitor that your systems don't swap on disk,
|
||||
because swapping memory on disks decreases performance by
|
||||
a factor of 20, at least.
|
||||
On all sides, monitor that your systems don't swap its
|
||||
running processes on disk, because swapping running processes
|
||||
on disks decreases performance by a factor of 20, at least.
|
||||
It's not because the swap memory is used that your
|
||||
system swaps processes on disk.
|
||||
|
||||
- CPU.
|
||||
100% CPU during a whole transfer means the system is busy.
|
||||
|
|
@ -245,8 +275,9 @@ Possible bottlenecks:
|
|||
Other possible bottlenecks:
|
||||
- Number of hosts available to run imapsync processes.
|
||||
- Imapsync itself.
|
||||
- Errors management.
|
||||
- Management of errors.
|
||||
- MX domains, DNS.
|
||||
- Incompetence.
|
||||
- Money.
|
||||
- Time.
|
||||
- Bad luck.
|
||||
|
|
@ -263,7 +294,7 @@ Q. Any performance issue?
|
|||
You have to try and check the transfer rates, sum them up to
|
||||
have a uniq numeric criteria.
|
||||
There is always a limit, depending on remote imap servers
|
||||
and the one running imapsync;
|
||||
and the one running imapsync.
|
||||
CPU, memory, Inputs/Outputs are the classical bottlenecks,
|
||||
the worst bottleneck is the winner that sets the limit.
|
||||
|
||||
|
|
|
|||
51
FAQ.d/FAQ.Messages_Too_Big.txt
Normal file
51
FAQ.d/FAQ.Messages_Too_Big.txt
Normal file
|
|
@ -0,0 +1,51 @@
|
|||
#!/bin/cat
|
||||
$Id: FAQ.Messages_Too_Big.txt,v 1.3 2019/06/18 16:37:39 gilles Exp gilles $
|
||||
|
||||
This document is also available online at
|
||||
https://imapsync.lamiral.info/FAQ.d/
|
||||
https://imapsync.lamiral.info/FAQ.d/FAQ.Messages_Too_Big.txt
|
||||
|
||||
=======================================================================
|
||||
Dealing with too big messages with Imapsync.
|
||||
=======================================================================
|
||||
|
||||
Questions answered in this FAQ are:
|
||||
|
||||
Q. What can I do to transfer messages bigger than what allows the
|
||||
imap destination server?
|
||||
|
||||
R1. A solution is to truncate the message to the maximum size allowed
|
||||
before copying it to host2. That's a little dirty but it's ok
|
||||
if you prefer having a truncated message than no message
|
||||
at all. The attachments after the truncation won't be available
|
||||
but everything before should be ok. It may also depends
|
||||
on the software tool reading the email message.
|
||||
|
||||
For example,
|
||||
Gmail currently limits messages to 35651584 bytes (May 2019),
|
||||
|
||||
Starting with imapsync release 1.938 option --truncmess xxxx truncates
|
||||
messages bigger than the given size xxxx.
|
||||
|
||||
imapsync --truncmess 35651584 --appendlimit 1000000000000
|
||||
|
||||
Prior to imapsync release 1.938, instead of --truncmess:
|
||||
|
||||
On Linux, use:
|
||||
|
||||
imapsync ... --pipemess 'perl -0ne "print substr \$_,0,35651584" '
|
||||
|
||||
On windows, use:
|
||||
|
||||
I'm not sure of (not tested yet):
|
||||
|
||||
imapsync ... --pipemess "perl -0ne 'print substr $_,0,35651584' "
|
||||
|
||||
|
||||
R2. A not so dirty solution would be to transform the message and
|
||||
include links to the big attachments, instead of the attachments.
|
||||
Well, not done yet and too much complicted compared to the simple
|
||||
solution which is to allow big messages on the destination account.
|
||||
|
||||
=======================================================================
|
||||
=======================================================================
|
||||
|
|
@ -1,5 +1,5 @@
|
|||
#!/bin/cat
|
||||
$Id: FAQ.Migration_Plan.txt,v 1.5 2019/01/11 13:13:55 gilles Exp gilles $
|
||||
$Id: FAQ.Migration_Plan.txt,v 1.6 2019/04/10 12:05:31 gilles Exp gilles $
|
||||
|
||||
This document is also available online at
|
||||
https://imapsync.lamiral.info/FAQ.d/
|
||||
|
|
@ -85,7 +85,7 @@ Classical scenario, credentials triplets are different on both sides
|
|||
* In case there are still messages arriving at the old imap server
|
||||
host1, you can perform more postsyncs, ie, syncs every day
|
||||
with the options:
|
||||
--maxage 1 --delete1 --folder INBOX.
|
||||
--maxage 1 --delete1 --folder INBOX
|
||||
|
||||
|
||||
=====================================================================
|
||||
|
|
|
|||
|
|
@ -1,5 +1,5 @@
|
|||
#!/bin/cat
|
||||
$Id: FAQ.Passwords_on_Unix.txt,v 1.3 2019/01/10 13:27:28 gilles Exp gilles $
|
||||
$Id: FAQ.Passwords_on_Unix.txt,v 1.6 2019/04/02 17:19:21 gilles Exp gilles $
|
||||
|
||||
This document is also available online at
|
||||
https://imapsync.lamiral.info/FAQ.d/
|
||||
|
|
@ -12,19 +12,29 @@ https://imapsync.lamiral.info/FAQ.d/FAQ.Passwords_on_Unix.txt
|
|||
|
||||
|
||||
=======================================================================
|
||||
Q. On Unix, some passwords contain some *(),;& characters. Login fails.
|
||||
Q. On Unix, some passwords contain some weird *(),;&~ characters.
|
||||
Login fails.
|
||||
|
||||
R1. Enclose the password within single-quotes in the imapsync
|
||||
command line:
|
||||
|
||||
imapsync ... --password1 'passw*(),;&rd'
|
||||
imapsync ... --password1 'passw*(),;&rd~'
|
||||
|
||||
R2. If R1 fails, with very old imapsync or old Mail::IMAPClient Perl module,
|
||||
try also using double-quotes within single-quotes. It will enclose
|
||||
the password within double-quotes in the imap LOGIN command:
|
||||
|
||||
imapsync ... --password1 '"passw*(),;&rd"'
|
||||
imapsync ... --password1 '"passw*(),;&rd~"'
|
||||
|
||||
Old Mail::IMAPClient 3.37 is a bad horse having this issue solved
|
||||
by this double-quotes trick.
|
||||
fixed in 3.38 https://metacpan.org/changes/distribution/Mail-IMAPClient
|
||||
version 3.38: Tue Feb 9 02:48:21 UTC 2016
|
||||
- rt.cpan.org#110273: failure to quote password values
|
||||
(regression introduced in 3.36 via fix for rt.cpan.org#100601)
|
||||
|
||||
R3. Change the password to keep only f...ing normal characters.
|
||||
Make it long and random if strong security is your concern
|
||||
|
||||
=======================================================================
|
||||
=======================================================================
|
||||
|
|
|
|||
|
|
@ -1,5 +1,5 @@
|
|||
#!/bin/cat
|
||||
$Id: FAQ.Release_Checklist.txt,v 1.10 2019/02/14 15:52:44 gilles Exp gilles $
|
||||
$Id: FAQ.Release_Checklist.txt,v 1.11 2019/05/27 14:26:57 gilles Exp gilles $
|
||||
|
||||
This documentation is also available online at
|
||||
https://imapsync.lamiral.info/FAQ.d/
|
||||
|
|
@ -24,6 +24,10 @@ Checklist before release a new release:
|
|||
|
||||
- Review the general FAQ.d/FAQ.General.txt
|
||||
|
||||
- /X verify direct cgi
|
||||
- /X verify under noscript with firefox
|
||||
- /X verify under private with chrome
|
||||
|
||||
- make dist
|
||||
- make publish
|
||||
- verify VERSION is uploaded
|
||||
|
|
|
|||
|
|
@ -1,5 +1,5 @@
|
|||
#!/bin/cat
|
||||
$Id: FAQ.SSL_errors.txt,v 1.6 2018/05/24 11:34:30 gilles Exp gilles $
|
||||
$Id: FAQ.SSL_errors.txt,v 1.7 2019/04/05 20:04:38 gilles Exp gilles $
|
||||
|
||||
This document is also available online at
|
||||
https://imapsync.lamiral.info/FAQ.d/
|
||||
|
|
@ -67,14 +67,60 @@ R5. Set up a ssltunnel proxy to the host.
|
|||
Q. SSL connect attempt failed SSL
|
||||
routines:SSL23_GET_SERVER_HELLO:sslv3 alert handshake failure
|
||||
|
||||
R. Use:
|
||||
R1. Use:
|
||||
|
||||
imapsync ... --sslargs1 'SSL_cipher_list=DEFAULT'
|
||||
or
|
||||
imapsync ... --sslargs2 'SSL_cipher_list=DEFAULT'
|
||||
|
||||
depending on where the error occurs, host1 or host2 or both.
|
||||
|
||||
|
||||
R2. If it doesn't work, I let you try other things,
|
||||
I quote the § "SSL_version" section of
|
||||
https://metacpan.org/pod/IO::Socket::SSL (Module version: 2.066)
|
||||
|
||||
imapsync ... --sslargs1 SSL_version=SSLv2
|
||||
imapsync ... --sslargs1 SSL_version=TLSv1_2
|
||||
|
||||
SSLv2 and TLSv12 are just examples depending on your context
|
||||
(--ssl1 or --tls1, and also the imap server encryption scheme)
|
||||
|
||||
Feedback on what worked for you (and possibly hy) is welcome!
|
||||
|
||||
https://metacpan.org/pod/IO::Socket::SSL
|
||||
...
|
||||
SSL_version
|
||||
|
||||
Sets the version of the SSL protocol used to transmit data.
|
||||
'SSLv23' uses a handshake compatible with SSL2.0, SSL3.0 and TLS1.x,
|
||||
while 'SSLv2', 'SSLv3', 'TLSv1', 'TLSv1_1', 'TLSv1_2', or 'TLSv1_3'
|
||||
restrict handshake and protocol to the specified version.
|
||||
All values are case-insensitive. Instead of 'TLSv1_1', 'TLSv1_2', and 'TLSv1_3'
|
||||
one can also use 'TLSv11', 'TLSv12', and 'TLSv13'.
|
||||
|
||||
Support for 'TLSv1_1', 'TLSv1_2', and 'TLSv1_3'
|
||||
requires recent versions of Net::SSLeay and openssl.
|
||||
|
||||
Independent from the handshake format you can limit to set of
|
||||
accepted SSL versions by adding !version separated by ':'.
|
||||
The default SSL_version is 'SSLv23:!SSLv3:!SSLv2' which means,
|
||||
that the handshake format is compatible to SSL2.0 and higher,
|
||||
but that the successful handshake is limited to TLS1.0 and higher,
|
||||
that is no SSL2.0 or SSL3.0 because both of these versions have
|
||||
serious security issues and should not be used anymore.
|
||||
|
||||
You can also use !TLSv1_1 and !TLSv1_2 to
|
||||
disable TLS versions 1.1 and 1.2 while still allowing TLS version 1.0.
|
||||
|
||||
Setting the version instead to 'TLSv1' might break interaction
|
||||
with older clients, which need and SSL2.0 compatible handshake.
|
||||
|
||||
On the other side some clients just close the connection
|
||||
when they receive a TLS version 1.1 request.
|
||||
In this case setting the version
|
||||
to 'SSLv23:!SSLv2:!SSLv3:!TLSv1_1:!TLSv1_2' might help.
|
||||
|
||||
|
||||
=======================================================================
|
||||
=======================================================================
|
||||
|
||||
|
|
|
|||
|
|
@ -1,5 +1,5 @@
|
|||
#!/bin/cat
|
||||
$Id: FAQ.SmarterMail.txt,v 1.12 2018/05/24 11:34:30 gilles Exp gilles $
|
||||
$Id: FAQ.SmarterMail.txt,v 1.13 2019/06/20 10:11:21 gilles Exp gilles $
|
||||
|
||||
This document is also available online at
|
||||
https://imapsync.lamiral.info/FAQ.d/
|
||||
|
|
@ -17,21 +17,13 @@ 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 \
|
||||
--regextrans2 "s,Deleted Items,Trash," \
|
||||
--regextrans2 "s,Junk E-Mail,Junk," \
|
||||
--regextrans2 "s,Sent Items,Sent,"
|
||||
--sep1 "/" --prefix1 "" --useheader Message-Id --noabletosearch1
|
||||
|
||||
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 ^
|
||||
--regextrans2 "s,Deleted Items,Trash," ^
|
||||
--regextrans2 "s,Junk E-Mail,Junk," ^
|
||||
--regextrans2 "s,Sent Items,Sent,"
|
||||
--sep1 "/" --prefix1 "" --useheader Message-Id --noabletosearch1
|
||||
|
||||
Maybe add other --regextrans2 to change folder names, for this
|
||||
see also http://imapsync.lamiral.info/FAQ.d/FAQ.Folders_Mapping.txt
|
||||
|
||||
=======================================================================
|
||||
Q. Synchronizing from XXX to SmarterMail
|
||||
|
|
|
|||
|
|
@ -1,5 +1,5 @@
|
|||
#!/bin/cat
|
||||
$Id: FAQ.Various_Software_Servers.txt,v 1.10 2018/10/24 11:03:57 gilles Exp gilles $
|
||||
$Id: FAQ.Various_Software_Servers.txt,v 1.12 2019/06/26 22:17:03 gilles Exp gilles $
|
||||
|
||||
This document is also available online at
|
||||
https://imapsync.lamiral.info/FAQ.d/
|
||||
|
|
@ -13,12 +13,10 @@ https://imapsync.lamiral.info/FAQ.d/FAQ.Various_Server_Softwares.txt
|
|||
|
||||
|
||||
=======================================================================
|
||||
Q. From Zimbra to XXX
|
||||
Q. From or to Zimbra
|
||||
|
||||
imapsync ... \
|
||||
--exclude "Conversation Action Settings" \
|
||||
--exclude "Quick Step Settings" \
|
||||
--exclude "News Feed"
|
||||
R. Read the FAQ.Zimbra.txt
|
||||
https://imapsync.lamiral.info/FAQ.d/FAQ.Zimbra.txt
|
||||
|
||||
=======================================================================
|
||||
Q. From or to HMailServer version 4.4.1.
|
||||
|
|
@ -36,16 +34,6 @@ No specific option for HMailServer 5.3.3 since NAMESPACE is supported.
|
|||
Maybe --subscribe_all will help you to see all migrated folders.
|
||||
|
||||
|
||||
=======================================================================
|
||||
Q. Synchronizing from Kerio Connect to XXX
|
||||
|
||||
R. No special options required.
|
||||
See also:
|
||||
http://www.linux-france.org/prj/imapsync_list/msg01756.html
|
||||
http://www.safetynet-it.com/it-support/mac-kerio-server-to-microsoft-exchange-2010-migration-1/
|
||||
http://www.safetynet-it.com/it-support/mac-kerio-server-to-microsoft-exchange-2010-migration-2/
|
||||
|
||||
|
||||
=======================================================================
|
||||
Q. from Microsoft's Exchange 2007 to Google Apps for your Domain
|
||||
(GAFYD)
|
||||
|
|
@ -142,37 +130,15 @@ I encounter many errors like this:
|
|||
|
||||
R. GroupWise 7 seems buggy. Apply GroupWise 7 support pack 1
|
||||
|
||||
=======================================================================
|
||||
Q. Migrating from David Tobit V10 (DvISE Mail Access Server MA-...)
|
||||
|
||||
R. Use the following options:
|
||||
|
||||
imapsync ... --prefix1 "" --sep1 / --idatefromheader ^
|
||||
--nofoldersizes --useuid --nocheckmessageexists
|
||||
|
||||
=======================================================================
|
||||
Q. Migrating from David Tobit V8
|
||||
("* OK IMAP4rev1 DvISE Mail Access Server MA-8.10a (0126)")
|
||||
Q. Migrating from or to David Tobit
|
||||
|
||||
First try above V10 solution since improvments have been made
|
||||
to support Tobit.
|
||||
|
||||
R. Use the following options :
|
||||
imapsync ... --prefix1 INBOX. --sep1 / --subscribe --subscribed
|
||||
R. See FAQ.David_Tobit.txt
|
||||
https://imapsync.lamiral.info/FAQ.d/FAQ.David_Tobit.txt
|
||||
|
||||
=======================================================================
|
||||
Q. Migrating from Tobit David Server 6
|
||||
("DvISE Mail Access Server MA-6.60a (0118)")
|
||||
|
||||
First try above V10 solution since improvments have been made
|
||||
to support Tobit.
|
||||
|
||||
R. Look at the discussion:
|
||||
http://www.linux-france.org/prj/imapsync_list/msg00582.html
|
||||
http://www.linux-france.org/prj/imapsync_list/threads.html#00582
|
||||
patch saved in ./patches/imapsync-1.337_tobit_V6.patch
|
||||
|
||||
=======================================================================
|
||||
Q. I need to migrate 1250 mailboxes, passwords are in a MySQL Database.
|
||||
Can you tell me if your script suits my needs?
|
||||
|
||||
|
|
|
|||
|
|
@ -1,5 +1,5 @@
|
|||
#!/bin/cat
|
||||
$Id: FAQ.Zimbra.txt,v 1.4 2019/01/28 22:39:28 gilles Exp gilles $
|
||||
$Id: FAQ.Zimbra.txt,v 1.6 2019/06/25 00:15:16 gilles Exp gilles $
|
||||
|
||||
This documentation is also available online at
|
||||
https://imapsync.lamiral.info/FAQ.d/
|
||||
|
|
@ -16,6 +16,27 @@ It's obsolete and it will give you, and me, more difficulties than
|
|||
doing a standard sync without additional options.
|
||||
|
||||
|
||||
=======================================================================
|
||||
Q. From Zimbra to XXX
|
||||
|
||||
imapsync ... \
|
||||
--exclude "Conversation Action Settings" \
|
||||
--exclude "Quick Step Settings" \
|
||||
--exclude "News Feed"
|
||||
|
||||
=======================================================================
|
||||
Q. Zimbra disconnects without reason
|
||||
Could not select: * BYE ... Zimbra IMAP4rev1 server closing connection
|
||||
|
||||
R. The cause of this problem may be that some users have a subscription
|
||||
of a shared folder from a mailbox locked and so the shared folder.
|
||||
The access problems may happen in a lot of folders,
|
||||
not only the shared/locked one.
|
||||
|
||||
It should work after removing the locked/shared folder.
|
||||
|
||||
Thanks to Danny Herrlitz for this input!
|
||||
|
||||
=======================================================================
|
||||
Q. How to migrate from Zimbra with an admin account?
|
||||
|
||||
|
|
|
|||
|
|
@ -1,5 +1,5 @@
|
|||
|
||||
# $Id: htaccess.txt,v 1.23 2019/02/16 22:42:25 gilles Exp gilles $
|
||||
# $Id: htaccess.txt,v 1.25 2019/05/17 10:16:00 gilles Exp gilles $
|
||||
|
||||
|
||||
AddDescription "<b>Back</b> to Imapsync main page." ..
|
||||
|
|
@ -11,6 +11,7 @@ AddDescription "<b>Big mailboxes</b> tips." FAQ.Big_Mailb
|
|||
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
|
||||
|
|
@ -33,6 +34,7 @@ AddDescription "<b>Password & special characters on Windows</b>." FAQ.Passwords
|
|||
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
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue