GitLab

client ask for password and save it. the daemon checks it after a minute
to see if the password is set or not. Does this thrice before it returns
NULL. Ideally the backends should retunr NEED_PASSWORD and clients
should prompt for it and redo the command.

password isn't available for the backend.

(cherry picked from commit d331e6f0)

This still isn't good enough; we need to support calling out to
/usr/bin/ntlm_auth to handle the challenge/response *for* us, for
single-sign-on so that we don't need to know the password for ourselves.
(cherry picked from commit e3181159)

(cherry picked from commit b0dfd4ae)

Apparently when building without Kerberos support the entire contents of
camel-sasl-gssapi.c is omitted, which breaks generating API docs because
camel-scan.c expects a camel_sasl_gssapi_get_type() regardless.

With this commit, when building with Kerberos support, CamelSaslGssapi
is still a registered CamelSasl subclass but it does absolutely nothing
and is never used by Camel's SASL support.

For some reason, cached mail message files are sometimes winding up as
zero-length files.  Still need to figure out how this is happening, but
in the meantime teach Camel to disregard zero-length cache files.

Should have been commited to master

This reverts commit 28feecc3.