Re: Sasl: No worthy mechs found
On Fri, Dec 02, 2016 at 03:47:01AM +, david wen riccardi-zhu wrote: > Glad to hear! I'd made the same assumption. > Not sure if something is broken, > sounds like it. a -Dn dump from such a failing session would be interesting. -- 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
Re: empty line in output of -l
On Thu, Dec 01, 2016 at 11:35:16AM +0100, Peter P. wrote: > after some more research I think I can answer this for myself. It seems > the first block is the local (slave) folders, the second block the > remote (master) folders. > nah, this sounds totally wrong. the folder mapping must be somehow incorrect. the empty line is also scary. i'd need the config file and the output of -Dmn to try some wild guesses. -- 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
Re: different behavior between 1.2.1 and 1.1.2
On Thu, Dec 01, 2016 at 12:14:21PM +0100, Peter P. wrote: > I assume that the way the config options have changed, > yes, there is this item in the NEWS file: > > An IMAP Path/NAMESPACE rooted in INBOX won't be handled specially > > any more. This means that some Patterns may need adjustment. from the first look it seems that this is exactly what is hitting you. > IMAPStore box-remote > Account box > Path INBOX > an entirely wild guess is that you just need to remove this. running with -l will tell you. if it doesn't help, try adding 'UseNamespace no' as well. other than that, see reply to the other mail. -- 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
Re: Sasl: No worthy mechs found
This is mine: Reading configuration file /home/user/.mbsyncrc Channel example Opening master store example-remote... Resolving mail.example.com... ok Connecting to mail.example.com (xx.xx.xx.xxx:993)... Opening slave store example-local... Connection is now encrypted * OK IMAP4 ready >>> 1 CAPABILITY * CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS IDLE AUTH=PLAIN 1 OK completed Logging in... IMAP error: authentication mechanism PLAIN is not supported This is with "AuthMechs *". With "AuthMecs LOGIN" everything works. Just saw you email about the config file, though; I have a suspicion it applies to me as well. --- dwrz|朱为文 On 2016-12-02 09:15, Oswald Buddenhagen wrote: > On Fri, Dec 02, 2016 at 03:47:01AM +, david wen riccardi-zhu wrote: > >> Glad to hear! I'd made the same assumption. > >> Not sure if something is broken, > sounds like it. a -Dn dump from such a failing session would be > interesting. > > -- > 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-- 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
