On Wed, 2016-06-22 at 17:28 +0200, Eric Luyten via Info-cyrus wrote:
> 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
On 06/23/16 16:49 +0200, Eric Luyten via Info-cyrus wrote:
On Wed, June 22, 2016 6:02 pm, Dan White wrote:
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
s
On Wed, June 22, 2016 6:02 pm, Dan White wrote:
> 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
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.sh
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=PL
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 ...
