Dear Oswald, list,
* Oswald Buddenhagen <[email protected]> [2016-03-07 09:45]:
> On Sun, Mar 06, 2016 at 08:59:21PM +0100, Peter P. wrote:
> > * OK [CAPABILITY IMAP4rev1 STARTTLS LOGINDISABLED] GroupWise Server
> > >>> 1 STARTTLS
> > 1 OK Begin TLS negotiation
> > >>> 2 CAPABILITY
> > * CAPABILITY IMAP4rev1 AUTH=PLAIN AUTH=XGWTRUSTEDAPP UNSELECT
> > 2 OK CAPABILITY completed
> > >>> 3 LOGIN <user> <pass>
> > [then after some time]
> > IMAP command 'LOGIN <user> <pass>' returned an error: NO LOGIN
> > GroupWise login failed
> >
> > Every third time or so I would get beyond that point with
> > 3 OK LOGIN completed
> > and so on and so forth.
> >
> > Is there anything I could try to get more stable logins? Is it me,
> > mbsync or the mail server?
> >
> to me it seems that the server forgets to internally re-enable LOGIN
> after TLS negotiation despite reporting that it has done so.
Thank you for this idea!
> you can try UseIMAPS to work around that apparent server bug.
Which sadly didn't help.
> you can also try AuthMech PLAIN when you upgrade to isync 1.2.1 from
> experimental (or build it yourself).
I did build it myself but, witch AuthMech PLAIN in my config's
IMAPAccount section, it still doesn't work. I am now getting:
[...]
Connection is now encrypted
Logging in...
Authenticating with SASL mechanism PLAIN...
IMAP command 'AUTHENTICATE PLAIN <authdata>' returned an error: NO
AUTHENTICATE GroupWise login failed
cheers,
P
------------------------------------------------------------------------------
Transform Data into Opportunity.
Accelerate data analysis in your applications with
Intel Data Analytics Acceleration Library.
Click to learn more.
http://makebettercode.com/inteldaal-eval
_______________________________________________
isync-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/isync-devel
