Patch applied cleanly against 1.5.1 and fixes it. On a node advertising AUTH=PLAIN, mbsync now reports
IMAP error: LOGIN credentials are excessively long. Wrong AuthMech selected? and exits normally. No SIGABRT across several runs. You were right that AUTH=PLAIN was a red herring -- it's the LOGIN path and the credential length, not anything SASL-specific. And the new message is accurate for my case: this build has no XOAUTH2 mechanism available, which is the real misconfiguration underneath. Thanks for the quick turnaround. Aug 27, 2026, 17:48 by [email protected]: > On Tue, Aug 25, 2026 at 07:11:24PM +0200, [email protected] wrote: > >> F: 1 OK CAPABILITY completed. >> Logging in... >> Fatal: buffer too small. Please report a bug. >> >> #6 0x0000aaaaaaab2ee8 in imap_exec (ctx=0xaaaaaaaf5af0, >> cmdp=0xaaaaaacadbb0, done=<optimized out>, >> fmt=<optimized out>) at drv_imap.c:539 >> #7 0x0000aaaaaaaaf0cc in done_imap_cmd (ctx=0xaaaaaaaf5af0, >> cmd=0xaaaaaacadc80, >> response=<optimized out>) at drv_imap.c:359 >> > the call chain was obviously tail-merged, making this trace kinda useless. > however, the only place where this is actually possible is the LOGIN path, > and thus the AUTH=PLAIN thing must be a red herring. > > please try the attached patch. > > _______________________________________________ > isync-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/isync-devel >
_______________________________________________ isync-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/isync-devel
