Re: Sasl: No worthy mechs found

2016-12-04 Thread Oswald Buddenhagen 
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 found that you'd get at least EXTERNAL
even if no modules at all are available, so that guess wasn't all that
informed, either.

things should work without workarounds in the 1.2 branch now.

--
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

2016-12-03 Thread Oswald Buddenhagen 
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 installed.

... and i notice that the LOGIN fallback in the case of a build with
SASL is even more spectacularly botched. :}

--
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

2016-12-03 Thread Peter P. 
* 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 OK completed
> > Logging in...
> > IMAP error: authentication mechanism PLAIN is not supported 
> > 
> i fixed this in the 1.2 branch.
> 
> peter's oringinal problem is probably actually expected behavior: when
> the connection is not encrypted, LOGIN will be used only when explicitly
> specified, not via *. i suppose i could make the messages more explicit ...
Again thank you! That could be a good idea. 

cheers, P

--
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

2016-12-02 Thread david wen riccardi-zhu 
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

Re: Sasl: No worthy mechs found

2016-12-01 Thread david wen riccardi-zhu 
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 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 mechanismes deemed secure enough for the given SSL method."
> (of which I thought LOGIN was included). This is on imap.aol.com btw.
> 
> Thanks dwrz!
> P--
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

2016-12-01 Thread Peter P. 
* 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 mechanismes deemed secure enough for the given SSL method."
(of which I thought LOGIN was included). This is on imap.aol.com btw.

Thanks dwrz!
P

--
___
isync-devel mailing list
isync-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/isync-devel