On 26 September 2017 15:08:42 CEST, Urbain Vaes <urb...@vaes.uk> wrote: >Hello, > >I have been happily using isync for a couple of years without problems, >but in the last week or so the following error always appears: > ># mbsync -V -D Work-sent ># ># Reading configuration file /home/username/.mbsyncrc ># Channel Work-sent ># Opening master store Work-remote... ># Resolving outlook.office365.com... ok ># Connecting to outlook.office365.com ([2603:1026:6:2::2]:993)... ># Opening slave store Work-local... ># Connection is now encrypted ># * OK The Microsoft Exchange IMAP4 service is ready. >[RABCADYAUABSADAAOQAwADIAQwBBADAAMAAwADUALgBlAHUAcgBwAHIAZAAwADkALgBwAHIAbwBkAC4AbwB1AHQAbABvAG8AawAuAGMAbwBtAA==] ># >>> 1 CAPABILITY ># * CAPABILITY IMAP4 IMAP4rev1 AUTH=PLAIN AUTH=XOAUTH2 SASL-IR UIDPLUS >ID UNSELECT CHILDREN IDLE NAMESPACE LITERAL+ ># 1 OK CAPABILITY completed. ># Logging in... ># Authenticating with SASL mechanism PLAIN... ># >>> 2 AUTHENTICATE PLAIN <authdata> ># 2 OK AUTHENTICATE completed. ># >>> 3 NAMESPACE ># 3 BAD User is authenticated but not connected. ># IMAP command 'NAMESPACE' returned an error: BAD User is >authenticated but not connected.
See https://unix.stackexchange.com/questions/164823/user-is-authenticated-but-not-connected-after-changing-my-exchange-password#164824 This seems to be Outlooks buggy way of telling you that your password is wrong. Microsoft must have a dedicated army of people that changes error messages to make sure they are as useless or misleading as possible, and they are particularly proud of this one I am sure. ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ isync-devel mailing list isync-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/isync-devel
