On Thu, Dec 08, 2016 at 03:56:32PM +0100, Claus-Michael Schlesinger wrote: > it seems that the authentication error might still be due to the ssl problem. > no, that's unrelated. ssl works at a different layer than the authentication. it appears that SASL PLAIN authentication isn't working with this server, which is totally not a surprise. try 'AuthMechs LOGIN' as a workaround.
> memcpy(0xe42e20, "AUTHENTICATE PLAIN GWMxMjyyxjdAa"..., 119) > = 0xe42e20 > memcpy(0xe42eac, "2 AUTHENTICATE PLAIN YWMxMjgyMjd"..., 123) > = 0xe42eac > note that you partially revealed your login credentials. it's not that bad, as the first appears to be just binary garbage while the second is the start of your login name, but you need to pay better attention to not post data which is not clearly harmless. > I'll try to solve the certificate related problems with the server > administrator. > yes. though i wouldn't be surprised if users are generally instructed to just click away the certificate warning in their gui mua, which is effectively equivalent to what you did now. ------------------------------------------------------------------------------ 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
