Re: Sasl: No worthy mechs found

[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

[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

unknown/misplaced keyword 'AuthMechs' (plus 'SSLType' and 'SSLVersions')

[david wen riccardi-zhu]

I had mbsync working perfectly until a recent server upgrade. 

Not sure if it matters, but I went from a Raspberry Pi 3 running
Raspbian to a Dell Chromebox running Ubuntu server. 

Installed isync to the new sever, copied my .mbsyncrc, and now it's not
working. 

I am getting the following errors when trying to run mbsync: 

/home/user/.mbsyncrc:5: unknown/misplaced keyword 'AuthMechs'
/home/user/.mbsyncrc:6: unknown/misplaced keyword 'SSLType'
/home/user/.mbsyncrc:7: unknown/misplaced keyword 'SSLVersions' 

If I comment out those lines, I get the following: 

Socket error from wtf.imap.com (##.##.##.###:993): Connection reset by
peer 

I'm struggling to figure out what is going on and why. As far as I know,
nothing has changed with either my mail provider's IMAP server or my
MaildirStore. 

After reading through the list, I tried using a new Maildirstore, but
I'm still getting the same error. 

Any insights or suggestions? 

Thank you, 

David

-- 
dwrz|朱为文--
Developer Access Program for Intel Xeon Phi Processors
Access to Intel Xeon Phi processor-based developer platforms.
With one year of Intel Parallel Studio XE.
Training and support from Colfax.
Order your platform today. http://sdm.link/xeonphi___
isync-devel mailing list
isync-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/isync-devel