sync_client fails with GSSAPI error 'unknown mech-code 0 for mech unknown'

Karl Pielorz kpielorz_lst at
Wed Jun 5 11:33:36 EDT 2013

--On 05 June 2013 09:09 -0500 Dan White <dwhite at> wrote:

> You can configure sasl_mech_list per service.
> Within your /etc/cyrus.conf, you may have something like:
>      imap             cmd="imapd -U 30 -D" listen="imap" prefork=0
>      pop3             cmd="pop3d -U 30" listen="pop3" prefork=0
>      syncserver       cmd="/usr/lib/cyrus/bin/sync_server" listen="csync"
> within your services section. 'imap', 'pop3', and 'syncserver' are the
> names of the services, which can be referenced within /etc/imapd.conf
> like this:
> syncserver_sasl_mech_list: digest-md5
> On the next spawn of that service, libsasl2 will only initialize the
> specified mechanisms.

That suddenly makes sense, thanks! - I've updated the config to use this, 
and it works as well,



More information about the Cyrus-devel mailing list