> that means that your sasl library doesn't know anything about gssapi
> as far as mbsync can determine. i have no clue why offlineimap would
> behave differently - check with ldd whether it's using the same sasl
> library, and if so, use ltrace and/or strace to compare the the
> programs' behavior.
Duh! I'm trying it on another machine (with similar yet obviously not
identical config) and indeed I forgot to install the
`libsasl2-modules-gssapi-mit` package on that machine.
Thanks for debugging my config.
OK, I now fixed this problem, but I get another:
% mbsync --config ~/tmp/.mbsyncrc -a --verbose --debug
Reading configuration file ~/tmp/.mbsyncrc
Channel diro-local
Opening master store diro-remote...
M: [ 1] Enter connect_store
Resolving mail.iro.umontreal.ca... ok
Connecting to mail.iro.umontreal.ca (132.204.27.60:993)...
M: [ 1] Leave connect_store
Opening slave store diro-local...
S: [ 2] Enter connect_store
S: [ 2] Callback enter connect_store, sts=0
pattern '*' (effective '*'): Path, no INBOX
S: [ 3] Enter list_store, flags=2
S: [ 3] Callback enter list_store
S: [ 3] Callback leave list_store
S: [ 3] Leave list_store
S: [ 2] Callback leave connect_store
S: [ 2] Leave connect_store
Connection is now encrypted
M: * OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE
IDLE AUTH=GSSAPI AUTH=LOGIN AUTH=PLAIN] Dovecot ready.
Logging in...
Authenticating with SASL mechanism GSSAPI...
Fatal: buffer too small. Please report a bug.
zsh: abort (core dumped) mbsync --config ~/tmp/.mbsyncrc -a --verbose
--debug
%
What's the next step?
Stefan
_______________________________________________
isync-devel mailing list
isync-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/isync-devel
