mirror of
https://github.com/imapsync/imapsync.git
synced 2025-07-23 02:35:54 +02:00
1.684
This commit is contained in:
parent
d0595b7dfd
commit
8d24f07718
110 changed files with 6018 additions and 4489 deletions
|
@ -7,7 +7,7 @@
|
|||
<CENTER>
|
||||
<H1>Imapsync tutorial</H1>
|
||||
<FONT SIZE="4"><I>Gilles LAMIRAL gilles.lamiral@laposte.net</I></FONT><BR>
|
||||
<FONT SIZE="4">$Id: TUTORIAL_Unix.t2t,v 1.17 2016/01/21 03:34:23 gilles Exp gilles $ </FONT>
|
||||
<FONT SIZE="4">$Id: TUTORIAL_Unix.t2t,v 1.18 2016/02/04 03:27:01 gilles Exp gilles $ </FONT>
|
||||
</CENTER>
|
||||
|
||||
<P></P>
|
||||
|
@ -23,11 +23,12 @@
|
|||
<LI><A HREF="#toc5">2.3. Prepare your credentials</A>
|
||||
<LI><A HREF="#toc6">2.4. Take a real user account as source</A>
|
||||
<LI><A HREF="#toc7">2.5. Take a test user account as destination</A>
|
||||
<LI><A HREF="#toc8">2.6. Edit your own script mysync</A>
|
||||
</UL>
|
||||
<LI><A HREF="#toc8">3. Background knowledge about emailboxes</A>
|
||||
<LI><A HREF="#toc9">4. Conventions</A>
|
||||
<LI><A HREF="#toc10">5. Why start with a test account on destination host2?</A>
|
||||
<LI><A HREF="#toc11">6. Imapsync default behaviour</A>
|
||||
<LI><A HREF="#toc9">3. Background knowledge about emailboxes</A>
|
||||
<LI><A HREF="#toc10">4. Conventions</A>
|
||||
<LI><A HREF="#toc11">5. Why start with a test account on destination host2?</A>
|
||||
<LI><A HREF="#toc12">6. Imapsync default behaviour</A>
|
||||
</UL>
|
||||
|
||||
<P></P>
|
||||
|
@ -202,19 +203,23 @@ we now have the next three parameters.
|
|||
<LI>--host2 <B>imaphost2.mydomain.tld</B>
|
||||
<LI>--user2 <B>myuser2</B>
|
||||
<LI>--password2 <B>mysecret2</B>
|
||||
<P></P>
|
||||
++ Edit your own script mysync ++
|
||||
<P></P>
|
||||
</UL>
|
||||
|
||||
<A NAME="toc8"></A>
|
||||
<H2>2.6. Edit your own script mysync</H2>
|
||||
|
||||
<P>
|
||||
Now edit the script <CODE>mysync</CODE> and replace the test values by yours.
|
||||
<P></P>
|
||||
</P>
|
||||
<P>
|
||||
You're ready for a dry test on your accounts.
|
||||
<P></P>
|
||||
</P>
|
||||
|
||||
<PRE>
|
||||
sh mysync
|
||||
</PRE>
|
||||
|
||||
<P></P>
|
||||
<P>
|
||||
Since mysync script is a copy of examples/imapsync_example.sh,
|
||||
your first run with your data should include three other options
|
||||
--automap --justfolders --dry.
|
||||
|
@ -222,13 +227,15 @@ With --dry option, nothing will really be done on host2
|
|||
but you will test whether the credentials are ok on both sides
|
||||
or not, by a successful login or a failure. You will also observe
|
||||
if the folders mapping is ok.
|
||||
<P></P>
|
||||
</P>
|
||||
<P>
|
||||
If a login fails then double-check all three values that identify
|
||||
the account, which are the host, the login name, and the password.
|
||||
<P></P>
|
||||
</P>
|
||||
<P>
|
||||
If the folders mapping proposed is not ok then you can fix it with
|
||||
option --f1f2, like this example:
|
||||
</UL>
|
||||
</P>
|
||||
|
||||
<PRE>
|
||||
... --f1f2 "Sent Messages=Sent"
|
||||
|
@ -251,7 +258,7 @@ folders. Remove --dry from mysync and rerun it:
|
|||
sh mysync
|
||||
</PRE>
|
||||
|
||||
<A NAME="toc8"></A>
|
||||
<A NAME="toc9"></A>
|
||||
<H1>3. Background knowledge about emailboxes</H1>
|
||||
|
||||
<P>
|
||||
|
@ -324,7 +331,7 @@ OS X users are in the Unix world nowadays so they must follow
|
|||
the Unix examples.
|
||||
</P>
|
||||
|
||||
<A NAME="toc9"></A>
|
||||
<A NAME="toc10"></A>
|
||||
<H1>4. Conventions</H1>
|
||||
|
||||
<P>
|
||||
|
@ -380,7 +387,7 @@ is equivalent to
|
|||
imapsync --host1 test.lamiral.info --user1 test1 --password1 secret1 ...
|
||||
</PRE>
|
||||
|
||||
<A NAME="toc10"></A>
|
||||
<A NAME="toc11"></A>
|
||||
<H1>5. Why start with a test account on destination host2?</H1>
|
||||
|
||||
<P>
|
||||
|
@ -407,7 +414,7 @@ the duplicates on host2 but it's better to avoid them on user accounts,
|
|||
users won't like you mess up their mailboxes.
|
||||
</P>
|
||||
|
||||
<A NAME="toc11"></A>
|
||||
<A NAME="toc12"></A>
|
||||
<H1>6. Imapsync default behaviour</H1>
|
||||
|
||||
<P>
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue