<style type="text/css">
<!--
/* Nine - Font styles for outgoing message (text) */
p {font-family:Century Gothic, CenturyGothic, AppleGothic, sans-serif; font-size:10.0pt; color:#1F497D}
-->
</style><div style="font-family:Century Gothic, CenturyGothic, AppleGothic, sans-serif; font-size:10.0pt; color:#1F497D"><p dir=ltr> Apologizes for the thread diversion here but I've been seeing a lot of discussion about using imapsync to migrate servers. From what I have read in the documentation, you must have each user's password. How is this possible in a business environment where you can't have (or shouldn't have) that information because of legal/privacy/ethical reasons? Is there something I'm missing in the docs?</p>
<p dir=ltr>Brian<br>
</p>
</div><div id="quoted_header" style="clear:both;"><br/><div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm 0cm 0cm"><span style="font-size:11.0pt;font-family:Calibri, Arial, Helvetica, sans-serif"><b>From:</b> Marcus Schopen <lists@localguru.de><br><b>Sent:</b> Aug 24, 2015 3:54 AM<br><b>To:</b> mogens@fumlersoft.dk<br><b>Cc:</b> info-cyrus@lists.andrew.cmu.edu<br><b>Subject:</b> Re: Migrate from 2.2.13 to 2.4.17 disasters<br></span></div></div><br type='attribution'><div id="quoted_body"><pre>Am Sonntag, den 23.08.2015, 20:36 +0200 schrieb Mogens Melander:
> For a task like this, I would use imapsync, a well documented,
> well supported and open source tool.
>
> https://github.com/imapsync/imapsync
I've used imapsync to migrate an internal server from 2.1.18 to 2.4.17
without any problems. Good tool.
Ciao!
----
Cyrus Home Page: http://www.cyrusimap.org/
List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/
To Unsubscribe:
https://lists.andrew.cmu.edu/mailman/listinfo/info-cyrus
</pre></div>