mirror of
https://github.com/imapsync/imapsync.git
synced 2025-06-10 14:44:32 +02:00
1.678
This commit is contained in:
Nick Bebout
parent
c16227350f
commit
629adbb8db
113 changed files with 7581 additions and 43297 deletions
20
FAQ.d/.htaccess
Normal file
20
FAQ.d/.htaccess
Normal file
|
|
@ -0,0 +1,20 @@
|
|||
|
||||
# $Id: .htaccess,v 1.1 2016/01/18 18:13:48 gilles Exp gilles $
|
||||
|
||||
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>Exchange 20xx</b> and <b>Office365</b>." FAQ.Exchange.txt
|
||||
AddDescription "<b>Changing folders names</b>." FAQ.Folders_Mapping.txt
|
||||
AddDescription "<b>Flags</b>." FAQ.Flags.txt
|
||||
AddDescription "<b>Gmail</b> accounts." FAQ.Gmail.txt
|
||||
AddDescription "<b>ISP</b>." FAQ.ISP.txt
|
||||
AddDescription "<b>Massive/bulk migrations</b>." FAQ.Massive.txt
|
||||
AddDescription "<b>Selecting messages</b>." FAQ.Messages_selection.txt
|
||||
AddDescription "<b>Oracle-UCS</b>." FAQ.Oracle-UCS.txt
|
||||
AddDescription "<b>Security</b>." FAQ.Security.txt
|
||||
AddDescription "<b>SmarterMail</b>." FAQ.SmarterMail.txt
|
||||
AddDescription "<b>Various imap server</b> softwares." FAQ.Various_Server_Softwares.txt
|
||||
AddDescription "<b>XOAUTH2</b> (<b>Gmail</b>)." FAQ.XOAUTH2.txt
|
||||
|
||||
|
||||
|
|
@ -1,9 +1,9 @@
|
|||
#!/bin/cat
|
||||
# $Id: FAQ.Domino.txt,v 1.4 2015/09/19 08:58:34 gilles Exp gilles $
|
||||
# $Id: FAQ.Domino.txt,v 1.5 2016/01/18 18:14:12 gilles Exp gilles $
|
||||
|
||||
======================================================================
|
||||
Imapsync. Domino specific issues and solutions
|
||||
======================================================================
|
||||
=============================
|
||||
Imapsync tips for Domino.
|
||||
=============================
|
||||
|
||||
|
||||
======================================================================
|
||||
|
|
@ -71,4 +71,4 @@ For Domino 853FP6 on Linux, we used this command on Unix:
|
|||
--regexmess 's{\A(.*?(?! ^$))^Date:(.*?)$}{$1Migratedbyus:$2\nx-MailDate:$2}gxms'
|
||||
|
||||
|
||||
======================================================================
|
||||
======================================================================
|
||||
|
|
|
|||
|
|
@ -1,8 +1,8 @@
|
|||
#!/bin/cat
|
||||
$Id: FAQ.Dovecot.txt,v 1.2 2015/07/18 22:35:27 gilles Exp gilles $
|
||||
$Id: FAQ.Dovecot.txt,v 1.3 2016/01/18 18:14:12 gilles Exp gilles $
|
||||
|
||||
=======================================================================
|
||||
Imapsync. Dovecot specific issues and solutions
|
||||
Imapsync tips for Dovecot. Specific issues and solutions.
|
||||
=======================================================================
|
||||
|
||||
|
||||
|
|
@ -16,4 +16,4 @@ R. Dovecot uses the same syntax as uw-imap
|
|||
To setup a Dovecot MasterUser see
|
||||
http://wiki2.dovecot.org/Authentication/MasterUsers
|
||||
|
||||
======================================================================
|
||||
======================================================================
|
||||
|
|
|
|||
|
|
@ -1,8 +1,8 @@
|
|||
#!/bin/cat
|
||||
$Id: FAQ.Duplicates.txt,v 1.5 2015/09/19 08:59:14 gilles Exp gilles $
|
||||
$Id: FAQ.Duplicates.txt,v 1.6 2016/01/18 18:14:12 gilles Exp gilles $
|
||||
|
||||
======================================================================
|
||||
Imapsync and duplicated messages issues.
|
||||
Imapsync tips about duplicated messages issues.
|
||||
======================================================================
|
||||
|
||||
=======================================================================
|
||||
|
|
|
|||
|
|
@ -1,49 +1,51 @@
|
|||
#!/bin/cat
|
||||
$Id: FAQ.Exchange.txt,v 1.14 2015/11/30 16:12:18 gilles Exp gilles $
|
||||
$Id: FAQ.Exchange.txt,v 1.17 2016/01/18 18:14:12 gilles Exp gilles $
|
||||
|
||||
=======================================================================
|
||||
Imapsync. Exchange 20xx and Office365 specific issues and solutions
|
||||
=======================================================================
|
||||
=================================================================================
|
||||
Imapsync tips for Exchange 20xx and Office365. Specific issues and solutions.
|
||||
=================================================================================
|
||||
|
||||
Questions anwswered in this FAQ are:
|
||||
|
||||
Q. Can I use imapsync to transfer from or to Exchange or Office365 accounts?
|
||||
|
||||
Q. How to sync from XXX to Exchange 2010/2013 or Office365
|
||||
|
||||
|
||||
Q. How to sync from XXX to Exchange 2010/2013
|
||||
|
||||
Q. How to sync from XXX to Office365
|
||||
|
||||
Q. For Office365 I have double and triple checked the username and
|
||||
password spelling but I still get a "LOGIN failed". Any clue?
|
||||
|
||||
|
||||
Q. Exchange fails with "User is authenticated but not connected".
|
||||
|
||||
|
||||
Q. From XXX to Exchange 2013 or Office365, read receipts are all
|
||||
resent again after a sync. Even for old messages. How can I fix that?
|
||||
|
||||
|
||||
Q. From XXX to Exchange 2010/2013 or Office365 I get this error message
|
||||
sometimes: "BAD Command Argument Error 11". What does it mean?
|
||||
|
||||
|
||||
Q. From XXX to Exchange 2010 or 2013 or Office365 the flag Flagged does
|
||||
not seem to be well synced. What can I do?
|
||||
|
||||
|
||||
Q. 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 with an
|
||||
admin/authuser account?
|
||||
|
||||
|
||||
Q. How to migrate from or to Office 365 with an admin/authuser account?
|
||||
|
||||
|
||||
Q. How to migrate from or to Exchange 2003 with an admin/authuser
|
||||
account?
|
||||
|
||||
|
||||
Q. Couldn't create folder [trash] "Mailbox already exists".
|
||||
|
||||
|
||||
Q. Migrating to Exchange 201O, messages get date of the transfer,
|
||||
this is bad for sorting and listing. What can I do?
|
||||
|
||||
|
||||
Q. How to sync from any to Exchange2007?
|
||||
|
||||
|
||||
Q. How to sync from Microsoft Exchange 2000 IMAP4rev1 server?
|
||||
|
||||
=======================================================================
|
||||
|
|
@ -54,27 +56,22 @@ R. Yes. But IMAP access to a Exchange or Office365 account is not always
|
|||
part:
|
||||
|
||||
=======================================================================
|
||||
Q. How to sync from XXX to Exchange 2010/2013 or Office365
|
||||
Q. How to sync from XXX to Exchange 2010/2013
|
||||
|
||||
R. Here is a command line resume that solves most encountered issues when
|
||||
migrating to Exchange or Office365. To understand or change the
|
||||
details you have to read next Q/R sections.
|
||||
migrating to Exchange. To understand or change the details you have
|
||||
to read next Q/R sections.
|
||||
|
||||
|
||||
On Windows:
|
||||
|
||||
imapsync.exe ... ^
|
||||
--maxsize 10000000 ^
|
||||
--maxlinelength 9900 ^
|
||||
--maxmessagespersecond 4 ^
|
||||
--regexflag "s/\\Flagged//g" ^
|
||||
--disarmreadreceipts ^
|
||||
--regexmess "s,(.{9900}),$1\r\n,g"
|
||||
|
||||
On Unix
|
||||
imapsync ... --regexmess 's,(.{9900}),$1\r\n,g'
|
||||
|
||||
|
||||
On Unix:
|
||||
|
||||
imapsync ... \
|
||||
|
|
@ -86,13 +83,43 @@ On Unix:
|
|||
--maxlinelengthcmd 'reformime -r7'
|
||||
|
||||
On Linux, to get the "reformime" command, install the "maildrop" package.
|
||||
In case you don't have it you can use
|
||||
In case you don't have it you can still use
|
||||
--regexmess 's,(.{9900}),$1\r\n,g'
|
||||
instead of --maxlinelengthcmd 'reformime -r7'
|
||||
|
||||
On Windows, no "reformime" is available so messages with too long line length
|
||||
can be synced to Exchange or Office365 by inserting a CRLF every 9900
|
||||
characters on long lines, using --regexmess "s,(.{9900}),$1\r\n,g"
|
||||
|
||||
=======================================================================
|
||||
Q. How to sync from XXX to Office365
|
||||
|
||||
R. Here is a command line resume that solves most encountered issues when
|
||||
migrating to Office365. It's similar with Exchange except for some
|
||||
values. To understand or change the details you have to read
|
||||
next Q/R sections.
|
||||
|
||||
|
||||
On Windows:
|
||||
|
||||
imapsync.exe ... ^
|
||||
--maxsize 45000000 ^
|
||||
--maxmessagespersecond 4 ^
|
||||
--regexflag "s/\\Flagged//g" ^
|
||||
--disarmreadreceipts ^
|
||||
--regexmess "s,(.{10500}),$1\r\n,g"
|
||||
|
||||
On Unix:
|
||||
|
||||
imapsync ... \
|
||||
--maxsize 45000000 \
|
||||
--maxlinelength 10500 \
|
||||
--maxmessagespersecond 4 \
|
||||
--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 use
|
||||
--regexmess 's,(.{10500}),$1\r\n,g'
|
||||
instead of --maxlinelengthcmd 'reformime -r7'
|
||||
|
||||
=======================================================================
|
||||
Q. For Office365 I have double and triple checked the username and
|
||||
|
|
@ -112,7 +139,7 @@ R3. Try with a classic email client like Thunderbird and the same
|
|||
=======================================================================
|
||||
Q. Exchange fails with "User is authenticated but not connected".
|
||||
|
||||
R. "The message “User is authenticated but not connected” is due to a
|
||||
R. "The message User is authenticated but not connected is due to a
|
||||
bug in the Exchange server's IMAP implementation. If the client
|
||||
presents a valid user name but an invalid password, the server
|
||||
accepts the login, but subsequent commands fail with the
|
||||
|
|
@ -164,14 +191,14 @@ R. This error message comes from Exchange IMAP server when it
|
|||
|
||||
* Some messages are bigger than the size limit. 10 MB by default
|
||||
on Exchange. It can be upped by configuration for Exchange.
|
||||
If you can't configure this limit then use option
|
||||
If you can't fix this limit on Exchange then use option
|
||||
--maxsize 10000000 for 10 MB, change it if needed) to tell
|
||||
imapsync to skip those messages.
|
||||
This value is 25 MB by default for Office365 --maxsize 25000000
|
||||
This value is 45 MB by default for Office365
|
||||
|
||||
imapsync ... --maxsize 10000000 # 10 MB for Exchange
|
||||
|
||||
imapsync ... --maxsize 25000000 # 25 MB for Office365
|
||||
imapsync ... --maxsize 45000000 # 45 MB for Office365
|
||||
|
||||
|
||||
* Quota reached. The whole account is full.
|
||||
|
|
@ -180,10 +207,15 @@ R. This error message comes from Exchange IMAP server when it
|
|||
* Some messages have some lines too long. Use option --maxlinelength
|
||||
to skip messages whose max line length is over a number of bytes.
|
||||
--maxlinelength 1000 is a RFC2822 must but most server support
|
||||
higher values. Exchange supports 9900:
|
||||
higher values.
|
||||
Exchange supports 9900 characters line length:
|
||||
|
||||
imapsync ... --maxlinelength 9900
|
||||
|
||||
Office365 supports 10500 characters line length:
|
||||
|
||||
imapsync ... --maxlinelength 10500
|
||||
|
||||
In case you prefer fixing messages with long lines the hard way,
|
||||
instead of skipping them with --maxlinelength 9900, just use:
|
||||
|
||||
|
|
|
|||
|
|
@ -1,9 +1,9 @@
|
|||
#!/bin/cat
|
||||
$Id: FAQ.Flags.txt,v 1.4 2015/07/18 22:35:27 gilles Exp gilles $
|
||||
$Id: FAQ.Flags.txt,v 1.6 2016/01/18 18:14:12 gilles Exp gilles $
|
||||
|
||||
======================================================================
|
||||
Imapsync and flags
|
||||
======================================================================
|
||||
===============================
|
||||
Imapsync tips about flags.
|
||||
===============================
|
||||
|
||||
Questions answered here are:
|
||||
|
||||
|
|
@ -222,15 +222,15 @@ R. Filter flag \FORWARDED with --regexflag like this:
|
|||
|
||||
On Windows:
|
||||
|
||||
imapsync ... --regexflag "s/\\FORWARDED//g"
|
||||
imapsync ... --regexflag "s/\\FORWARDED//gi"
|
||||
|
||||
On Unix:
|
||||
|
||||
imapsync ... --regexflag 's/\\FORWARDED//g'
|
||||
imapsync ... --regexflag 's/\\FORWARDED//gi'
|
||||
|
||||
or
|
||||
|
||||
imapsync ... --regexflag "s/\\\\FORWARDED//g"
|
||||
imapsync ... --regexflag "s/\\\\FORWARDED//gi"
|
||||
|
||||
|
||||
=======================================================================
|
||||
|
|
@ -279,4 +279,4 @@ Two solutions:
|
|||
command.
|
||||
|
||||
|
||||
=======================================================================
|
||||
=======================================================================
|
||||
|
|
|
|||
|
|
@ -1,9 +1,17 @@
|
|||
#!/bin/cat
|
||||
$Id: FAQ.Folders_Mapping.txt,v 1.8 2015/12/03 02:37:45 gilles Exp gilles $
|
||||
$Id: FAQ.Folders_Mapping.txt,v 1.9 2016/01/18 18:14:12 gilles Exp gilles $
|
||||
|
||||
===============================================
|
||||
Imapsync tips about changing folders names.
|
||||
===============================================
|
||||
|
||||
Folders names are by default reproduced identical except for
|
||||
the prefix and the separator which are automatically adapted
|
||||
for host2.
|
||||
|
||||
Before using --regextrans2 you should consider using --automap
|
||||
and -f1f2 because they are simpler to understand and use.
|
||||
|
||||
======================================================================
|
||||
Imapsync. Changing folders names
|
||||
======================================================================
|
||||
|
||||
Things to know and understand before playing with --regextrans2
|
||||
|
||||
|
|
|
|||
|
|
@ -1,25 +1,40 @@
|
|||
#!/bin/cat
|
||||
$Id: FAQ.Gmail.txt,v 1.13 2015/11/05 21:01:12 gilles Exp gilles $
|
||||
$Id: FAQ.Gmail.txt,v 1.18 2016/01/18 18:14:12 gilles Exp gilles $
|
||||
|
||||
======================================================================
|
||||
Imapsync with Gmail
|
||||
======================================================================
|
||||
=====================================
|
||||
Imapsync tips for Gmail accounts.
|
||||
=====================================
|
||||
|
||||
Questions anwswered in this FAQ are:
|
||||
|
||||
Q. Can I use imapsync to transfer from or to Gmail accounts?
|
||||
|
||||
Q. How to synchronize from Gmail to Gmail?
|
||||
|
||||
Q. How to synchronize from XXX to Gmail?
|
||||
|
||||
Q. How to synchronize from Gmail to XXX?
|
||||
|
||||
Q. Can I use the Extension of the SEARCH command: X-GM-RAW described at
|
||||
https://support.google.com/mail/answer/7190?hl=en
|
||||
|
||||
Q. How to avoid the [IMAP] prefix on Gmail side?
|
||||
|
||||
Q. I can't authenticate with Gmail via IMAP
|
||||
and Gmail says "Please log in via your web browser"
|
||||
|
||||
Q. Can not open imap connection on [imap.gmail.com]
|
||||
|
||||
Q. Gmail does not really delete messages in folder [Gmail]/All Mail
|
||||
|
||||
Q. Does imapsync have the capability to do 2 stage authentication?
|
||||
|
||||
Q. How to use XOAUTH2 to globally authenticate gmail users?
|
||||
|
||||
Q. How to use XOAUTH to globally authenticate gmail users?
|
||||
|
||||
Q. How to use a Gmail account to backup several different imap accounts?
|
||||
|
||||
Q. How to migrate email from gmail to google apps?
|
||||
|
||||
=======================================================================
|
||||
|
|
@ -48,6 +63,7 @@ R. Use the following example:
|
|||
--user2 account2@gmail.com \
|
||||
--password2 gmailsecret2 \
|
||||
--exitwhenover 500000000 \
|
||||
--automap \
|
||||
--exclude "\[Gmail\]$"
|
||||
|
||||
|
||||
|
|
@ -57,14 +73,32 @@ Explanations:
|
|||
imap ssl connections.
|
||||
|
||||
--exitwhenover 500000000 ( ~500 MB ) option is here to avoid
|
||||
locking or errors when transfers exceed maximum limit.
|
||||
locking or errors when imap transfers exceed maximum limit.
|
||||
See http://support.google.com/a/bin/answer.py?hl=en&answer=1071518
|
||||
--exitwhenover is not mandatory in the sense you may be able to
|
||||
use an upper value than 500 MB without disconnections; I don't
|
||||
--exitwhenover is not mandatory in the sense Gmail may allow you
|
||||
to use an upper value than 500 MB without disconnections; I don't
|
||||
know the hard value, it seems to vary, so just have some tries
|
||||
and report me what you discover in case you detect something
|
||||
reliable.
|
||||
|
||||
--automap is not mandatory but it's a feature to automatically
|
||||
map folder names based on the Gmail user configuration itself, par account.
|
||||
For example, imap folder "[Gmail]/Sent Mail" may be mapped as one of
|
||||
E-mails enviados
|
||||
Enviada
|
||||
Enviado
|
||||
Gesendet
|
||||
Gönderildi
|
||||
Inviati
|
||||
Sendt
|
||||
Skickat
|
||||
Verzonden
|
||||
etc.
|
||||
on both sides, host1 or host2, maybe differently, sometimes in
|
||||
incomprehensible alphabets, a headache for imap sysadmins.
|
||||
See a listing here:
|
||||
http://stackoverflow.com/questions/2185391/localized-gmail-imap-folders/2185548#2185548
|
||||
|
||||
--exclude "\[Gmail\]$" is just there to avoid a warning error
|
||||
when selecting this not used folder.
|
||||
|
||||
|
|
@ -87,13 +121,13 @@ imapsync --host1 mail.oldhost.com \
|
|||
--ssl2 \
|
||||
--exitwhenover 500000000 \
|
||||
--maxsize 25000000 \
|
||||
--automap \
|
||||
--expunge1 \
|
||||
--addheader \
|
||||
--exclude "\[Gmail\]$" \
|
||||
--regextrans2 "s/[ ]+/_/g" \
|
||||
--regextrans2 "s/[\^]/_/g" \
|
||||
--regextrans2 "s/['\"\\\\]/_/g" \
|
||||
--regextrans2 "s,^Sent$,[Gmail]/Sent Mail,"
|
||||
--regextrans2 "s/['\"\\\\]/_/g"
|
||||
|
||||
Explanations:
|
||||
|
||||
|
|
@ -112,6 +146,9 @@ up to 25 MB. This value increases over time, it was 10 MB some
|
|||
years ago so you can try higher values. The Gmail page about
|
||||
this limit is https://support.google.com/mail/answer/6584
|
||||
|
||||
--automap is optional but it will save manual folder names
|
||||
changes or the use of --regextrans2 to map folder names.
|
||||
|
||||
--expunge1 is optional. It deletes messages marked \Deleted on host1.
|
||||
Imapsync syncs messages with all their flags, Gmail takes the messages
|
||||
marked \Deleted but deletes or moves them just after.
|
||||
|
|
@ -149,22 +186,14 @@ not accepted by gmail, character ^ to character _ underscore.
|
|||
--regextrans2 "s/['\"\\\\]/_/g" is optional. It converts
|
||||
characters ' or " or \ to character _ underscore.
|
||||
|
||||
--regextrans2 "s,^Sent$,[Gmail]/Sent Mail," is to transform the
|
||||
folder name "Sent" and adapt it to Gmail "Sent Mail" folder.
|
||||
If you're using a different language in Gmail you might adapt
|
||||
this example with the folder name translated, an example in French:
|
||||
|
||||
imapsync ...
|
||||
--regextrans2 "s,^Messages envoy&AOk-s$,[Gmail]/Messages envoy&AOk-s," \
|
||||
|
||||
|
||||
You can add --folder "INBOX.Sent" in the example in case
|
||||
you want to sync only the "Sent" folder.
|
||||
|
||||
You can select folders exported to imap within the gmail preferences,
|
||||
unselect some "System labels", depending on your needs.
|
||||
|
||||
The "All Mail" archive pseudo-folder should be updated automatically.
|
||||
You can select folders exported to imap within the gmail preferences.
|
||||
Select or unselect some "System labels", depending on your needs.
|
||||
|
||||
|
||||
=======================================================================
|
||||
|
|
@ -183,7 +212,8 @@ R. Use this example:
|
|||
--exitwhenover 2500000000 \
|
||||
--useheader="X-Gmail-Received" \
|
||||
--useheader "Message-Id" \
|
||||
--regextrans2 "s,\[Gmail\].,," \
|
||||
--automap \
|
||||
--regextrans2 "s,\[Gmail\].,," \
|
||||
--skipcrossduplicates \
|
||||
--folderfirst "Work" \
|
||||
--folderfirst "Friends" \
|
||||
|
|
@ -211,6 +241,8 @@ have changed) that Gmail always adds a different header
|
|||
by imapsync can not fail using this header. "Message-Id" is there
|
||||
for safety about this Gmail rule.
|
||||
|
||||
--automap is optional but it will save manual folder names
|
||||
changes or the use of --regextrans2 to map folder names.
|
||||
|
||||
--regextrans2 "s,\[Gmail\].,,"
|
||||
If your destination imap server doesn't like "[Gmail]" name,
|
||||
|
|
@ -244,6 +276,23 @@ label CanWait and only it.
|
|||
--skipcrossduplicates, will only put in "[Gmail]/All Mail"
|
||||
the messages that are not labeled at all.
|
||||
|
||||
=======================================================================
|
||||
Q. Can I use the Extension of the SEARCH command: X-GM-RAW described at
|
||||
https://support.google.com/mail/answer/7190?hl=en
|
||||
https://developers.google.com/gmail/imap_extensions#extension_of_the_search_command_x-gm-raw
|
||||
|
||||
R. Sure. Example, to search only emails with attachment and in unread state:
|
||||
|
||||
On Unix:
|
||||
|
||||
imapsync ... --search 'X-GM-RAW "has:attachment in:unread"'
|
||||
|
||||
On Windows:
|
||||
|
||||
imapsync.exe ... --search "X-GM-RAW ""has:attachment in:unread"""
|
||||
|
||||
|
||||
|
||||
=======================================================================
|
||||
Q. How to avoid the [IMAP] prefix on Gmail side?
|
||||
How to stop creating folder with this prefix?
|
||||
|
|
@ -277,19 +326,21 @@ Q. Can not open imap connection on [imap.gmail.com]:
|
|||
R0. It looks like this issue is related to ipv6. Both ipv4 and ipv6
|
||||
protocols should work with gmail and imapsync, I test that regurlarly,
|
||||
imapsync works fine for both ipv4 and ipv6.
|
||||
If you disable ipv6 then disable also ipv6 resolution or at least
|
||||
make ipv4 answers be taken before ipv6 since default resolution
|
||||
order is to take ipv6 resolution if any.
|
||||
If you disable ipv6 then disable also ipv6 resolution!
|
||||
Or at least, make ipv4 answers be taken before ipv6 since the default
|
||||
names resolution order is to present ipv6 name resolutions first.
|
||||
|
||||
R1. A first simple solution is to use directly gmail ipv4 ip address:
|
||||
|
||||
imapsync ... --host1 74.125.133.108
|
||||
|
||||
In case it changes, get with any command showing the imap.gmail.com resolution
|
||||
In case it changes, get with any command showing the imap.gmail.com
|
||||
name resolution:
|
||||
|
||||
nslookup imap.gmail.com
|
||||
host imap.gmail.com
|
||||
ping imap.gmail.com
|
||||
|
||||
Or go to http://ping.eu/nslookup/ to get the resolution.
|
||||
|
||||
R2. Fix imapsync with the line:
|
||||
|
|
|
|||
|
|
@ -1,11 +1,11 @@
|
|||
#!/bin/cat
|
||||
$Id: FAQ.ISP.txt,v 1.2 2015/10/21 15:23:07 gilles Exp gilles $
|
||||
$Id: FAQ.ISP.txt,v 1.3 2016/01/18 18:14:12 gilles Exp gilles $
|
||||
|
||||
=================================================
|
||||
Imapsync. ISP specific issues and solutions
|
||||
=================================================
|
||||
=========================================================
|
||||
Imapsync tips for ISP. Specific issues and solutions.
|
||||
=========================================================
|
||||
|
||||
* IMAP Sync - usage scenario with ISP - by Flávio Zarur Lucarelli.
|
||||
* IMAPSync - usage scenario with ISP - by Flávio Zarur Lucarelli.
|
||||
|
||||
I thought Id write a quick step by step on my attempts to learn the
|
||||
imapsync features that matter the most, so it works as we expected in
|
||||
|
|
|
|||
|
|
@ -1,9 +1,9 @@
|
|||
#!/bin/cat
|
||||
$Id: FAQ.Massive.txt,v 1.5 2015/11/05 14:46:20 gilles Exp gilles $
|
||||
$Id: FAQ.Massive.txt,v 1.6 2016/01/18 18:14:12 gilles Exp gilles $
|
||||
|
||||
======================================================================
|
||||
Imapsync for massive migrations
|
||||
======================================================================
|
||||
==============================================
|
||||
Imapsync tips for massive/bulk migrations.
|
||||
==============================================
|
||||
|
||||
Questions answered here are:
|
||||
|
||||
|
|
|
|||
|
|
@ -1,9 +1,11 @@
|
|||
#!/bin/cat
|
||||
$Id: FAQ.Messages_selection.txt,v 1.2 2015/10/21 15:39:57 gilles Exp gilles $
|
||||
$Id: FAQ.Messages_selection.txt,v 1.3 2016/01/18 18:14:12 gilles Exp gilles $
|
||||
|
||||
====================================
|
||||
Imapsync. How to select messages
|
||||
====================================
|
||||
=====================================
|
||||
Imapsync tips to select messages.
|
||||
=====================================
|
||||
|
||||
By default, Imapsync syncs all messages, avoiding duplicates.
|
||||
|
||||
=======================================================================
|
||||
Q. Is there a way we can specify a date range to sync emails?
|
||||
|
|
|
|||
|
|
@ -1,15 +1,16 @@
|
|||
#!/bin/cat
|
||||
$Id: FAQ.Oracle-UCS.txt,v 1.1 2015/07/20 04:34:32 gilles Exp gilles $
|
||||
$Id: FAQ.Oracle-UCS.txt,v 1.2 2016/01/18 18:14:12 gilles Exp gilles $
|
||||
|
||||
=======================================================================
|
||||
Imapsync. Oracle-UCS specific issues and solutions
|
||||
=======================================================================
|
||||
==================================================
|
||||
Imapsync tips for Oracle-UCS. Specific issues.
|
||||
==================================================
|
||||
|
||||
Oracle-UCS was previously Sun JES, IPlanet, etc.
|
||||
|
||||
|
||||
"NO Message contains NUL characters"
|
||||
--skipmess 'm/(\x00)+\Z/'
|
||||
|
||||
"Message contains invalid header"
|
||||
--skipmess 'm/[\x80-\xff]/'
|
||||
--skipmess 'm/[\x80-\xff]/'
|
||||
|
||||
|
||||
|
|
|
|||
|
|
@ -1,9 +1,9 @@
|
|||
#!/bin/cat
|
||||
# $Id: FAQ.Security.txt,v 1.1 2015/10/21 14:18:27 gilles Exp gilles $
|
||||
# $Id: FAQ.Security.txt,v 1.3 2016/01/18 18:14:12 gilles Exp gilles $
|
||||
|
||||
======================================================================
|
||||
Imapsync. Security issues and solutions
|
||||
======================================================================
|
||||
=======================================================
|
||||
Imapsync tips about security. Issues and solutions.
|
||||
=======================================================
|
||||
|
||||
|
||||
======================================================================
|
||||
|
|
@ -16,6 +16,13 @@ R1. In function "sub set_ssl", replace
|
|||
by
|
||||
IO::Socket::SSL::SSL_VERIFY_PEER()
|
||||
|
||||
R2. After imapsync 1.673, for example
|
||||
to set SSL_verify_mode to SSL_VERIFY_PEER on host1
|
||||
and SSL_verify_mode to SSL_VERIFY_NONE on host2
|
||||
|
||||
imapsync ... --ssl1 --ssl2 \
|
||||
--sslargs1 SSL_verify_mode=1 \
|
||||
--sslargs2 SSL_verify_mode=0 \
|
||||
|
||||
C1. Don't do this in function "sub set_tls" since it won't work by principle,
|
||||
tls is done AFTER the application level connexion is established
|
||||
|
|
|
|||
8
FAQ.d/FAQ.SmarterMail.txt
Executable file → Normal file
8
FAQ.d/FAQ.SmarterMail.txt
Executable file → Normal file
|
|
@ -1,9 +1,9 @@
|
|||
#!/bin/cat
|
||||
$Id: FAQ.SmarterMail.txt,v 1.6 2015/11/30 02:58:25 gilles Exp gilles $
|
||||
$Id: FAQ.SmarterMail.txt,v 1.7 2016/01/18 18:14:12 gilles Exp gilles $
|
||||
|
||||
=======================================================================
|
||||
Imapsync. SmarterMail specific issues and solutions
|
||||
=======================================================================
|
||||
=================================================================
|
||||
Imapsync tips for SmarterMail. Specific issues and solutions.
|
||||
=================================================================
|
||||
|
||||
|
||||
=======================================================================
|
||||
|
|
|
|||
|
|
@ -1,9 +1,9 @@
|
|||
#!/bin/cat
|
||||
$Id: FAQ.Various_Server_Softwares.txt,v 1.2 2015/10/21 15:41:41 gilles Exp gilles $
|
||||
$Id: FAQ.Various_Server_Softwares.txt,v 1.3 2016/01/18 18:14:12 gilles Exp gilles $
|
||||
|
||||
=======================================================================
|
||||
Imapsync. Server software specific issues and solutions
|
||||
=======================================================================
|
||||
====================================================
|
||||
Imapsync tips for various imap server softwares.
|
||||
====================================================
|
||||
|
||||
|
||||
|
||||
|
|
|
|||
|
|
@ -1,9 +1,9 @@
|
|||
#!/bin/cat
|
||||
$Id: FAQ.XOAUTH2.txt,v 1.6 2015/11/30 23:40:10 gilles Exp gilles $
|
||||
$Id: FAQ.XOAUTH2.txt,v 1.8 2016/01/18 18:14:12 gilles Exp gilles $
|
||||
|
||||
=======================================================================
|
||||
Imapsync. Using XOAUTH2 and XOAUTH authentication (Gmail)
|
||||
=======================================================================
|
||||
======================================================================
|
||||
Imapsync tips to use XOAUTH2 authentication (Gmail) and old XOAUTH
|
||||
======================================================================
|
||||
|
||||
|
||||
=======================================================================
|
||||
|
|
@ -12,7 +12,10 @@ Q. Is XOAUTH2 authentication available with imapsync?
|
|||
R. Yes, but XOAUTH2 has been really tested on Unix systems,
|
||||
less profund on Windows but it should work.
|
||||
|
||||
First, consider the XOAUTH2 feature at a prototype level.
|
||||
=======================================================================
|
||||
Q. How to use XOAUTH2 to globally authenticate gmail users?
|
||||
|
||||
R. First, consider the XOAUTH2 feature at a prototype level.
|
||||
|
||||
Perl modules needed for xoauth2 are:
|
||||
Crypt::OpenSSL::RSA
|
||||
|
|
@ -20,11 +23,12 @@ Perl modules needed for xoauth2 are:
|
|||
JSON::WebToken
|
||||
LWP
|
||||
HTML::Entities
|
||||
Encode::Byte
|
||||
|
||||
A easy way to install or upgrade Perl modules is to use cpanm command,
|
||||
also called cpanminus.
|
||||
|
||||
sudo cpanm JSON::WebToken JSON Crypt::OpenSSL::RSA LWP HTML::Entities
|
||||
sudo cpanm JSON::WebToken JSON Crypt::OpenSSL::RSA LWP HTML::Entities Encode::Byte
|
||||
|
||||
The code and first explanation comes from Joaquin Lopez at
|
||||
https://github.com/imapsync/imapsync/pull/25
|
||||
|
|
@ -35,12 +39,13 @@ convert the pk12 file.
|
|||
On Windows I've tried xoauth2 with openssl from
|
||||
https://slproweb.com/download/Win32OpenSSL-1_0_2d.exe at
|
||||
https://slproweb.com/products/Win32OpenSSL.html
|
||||
|
||||
It works.
|
||||
|
||||
Here is a complete example for Gmail. It is a little stupid
|
||||
since it is the same account as source and destination.
|
||||
since it is the same account as source and destination but
|
||||
it's just to get the picture for xoauth2 authentication.
|
||||
|
||||
All xoauth2 is given via the --password1 parameter.
|
||||
All xoauth2 config is given via the --password1 parameter.
|
||||
It has the form:
|
||||
|
||||
--password1 "A;B;C"
|
||||
|
|
@ -65,6 +70,22 @@ imapsync \
|
|||
|
||||
Use your own xoauth2 values.
|
||||
|
||||
|
||||
|
||||
=======================================================================
|
||||
Q. How to use a proxy with XOAUTH2 authentication?
|
||||
|
||||
With imapsync 1.670, you have to set two environment variables
|
||||
PERL_LWP_ENV_PROXY and https_proxy. Example:
|
||||
|
||||
PERL_LWP_ENV_PROXY=1 https_proxy=http://myproxy:8080/ imapsync --host1 ...
|
||||
|
||||
With later release than 1.670, you have to set only the https_proxy
|
||||
environment variable, if it isn't already set. Example:
|
||||
|
||||
https_proxy=http://myproxy:8080/ imapsync --host1 ...
|
||||
|
||||
|
||||
=======================================================================
|
||||
Q. How to use XOAUTH to globally authenticate gmail users?
|
||||
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue