I have previously used imapsync ( http://imapsync.lamiral.info/ ) with great success, primarily as a backup tool, but also to import data for new users, and export data to other provider when a user moves.
Office 365 is on the list of supported imap servers ( imapsync.lamiral.info/S/imapservers.shtml #44 ) Regards Mogens at fumlersoft dk 2016-06-22 23:02 GMT+07:00 Dan White via Info-cyrus < info-cyrus@lists.andrew.cmu.edu>: > On 06/22/16 17:28 +0200, Eric Luyten via Info-cyrus wrote: > >> All, >> >> >> After trying for a couple of days I have come to the conclusion >> that the Office 365 IMAP import tool uses the LOGIN authentication >> mech while Cyrus requires PLAIN or stronger for proxying to work. >> >> Even when only announcing AUTH=PLAIN in our server capabilities, >> Microsoft executes LOGIN ... ... >> >> (violation of RFC3501 section 6.1.1 ? >> dunno whether I am reading that correctly) >> >> >> Is my conclusion correct ? >> Any hacks or workarounds ? >> > > To enable SASL LOGIN support, add 'LOGIN' to your sasl_mech_list. Don't > confuse login with pre-sasl user/pass authentication. > > If Office 365 isn't performing TLS, you'll need to configure > sasl_minimum_layer and allowplaintext appropriately. > > -- > Dan White > > ---- > 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 >
---- 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
