Hi!

I tested mbsync with Microsoft Outlook using custom Entra IDs and ran into
trouble until I increased the size of the SASL and vprintf buffers, since
Microsoft issues long tokens.  Attached is a patch that offers plenty of
headroom.

I didn't stop to look how big my token actually was when the error was
occurring, but my current token is 1400 bytes.  The consumer access tokens
are encrypted and tend to be smaller, but the work/school tokens are jwt
and are larger.

Chad

Attachment: 0001-Increases-SASL-print-buffers-to-support-large-access.patch
Description: Binary data

_______________________________________________
isync-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/isync-devel

Reply via email to