Re: Sasl: No worthy mechs found

On Sun, Dec 04, 2016 at 04:21:54AM +0100, Peter P. wrote: > Oswald Buddenhagen [2016-12-03 18:03]: > > then the next guess would be that libsasl2-modules is not installed. > > At least, on my system, libsasl2-modules is installed. > yeah, while testing my fixes, i

Re: Sasl: No worthy mechs found

On Sat, Dec 03, 2016 at 05:37:47PM +0100, Oswald Buddenhagen wrote: > peter's oringinal problem is probably actually expected behavior: > when the connection is not encrypted, > actually, nonsense, the -V log says it is encrypted. then the next guess would be that libsasl2-modules is not

Re: Sasl: No worthy mechs found

* Oswald Buddenhagen [2016-12-03 17:38]: > On Fri, Dec 02, 2016 at 12:40:34PM +, david wen riccardi-zhu wrote: > > Connection is now encrypted > > * OK IMAP4 ready > > >>> 1 CAPABILITY > > * CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS IDLE AUTH=PLAIN > > 1

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

Re: Sasl: No worthy mechs found

Glad to hear! I'd made the same assumption. Not sure if something is broken, if the documentation needs to be updated, or if users need to be better informed. : ) --- dwrz|朱为文 On 2016-12-01 18:57, Peter P. wrote: > * dwrz [2016-12-01 16:19]: > >> Hi Peter, >> >> Just a shot

Re: Sasl: No worthy mechs found

* dwrz [2016-12-01 16:19]: > Hi Peter, > > Just a shot in the dark -- have you tried setting AuthMechs to LOGIN? And back from the dark I report that this works. Please excuse me, I did misunderstand the manpage saying approximately that "AuthMechs defaults to * and all