Cyrus: master/slave synchronisation

Dan White dwhite at
Sun Feb 7 18:11:06 EST 2010

On 07/02/10 09:37 +0100, Martin Schweizer wrote:
>I use FreeBSD 7.2/amd64 with Cyrus IMAP v2.3.16. Cyrus is installed on

>/var/log/auth.log on the Sync server:
>auth.log.4.bz2:Feb  6 17:37:00 acsvfbsd02 syncserver[49881]:
>DIGEST-MD5 server step 1
>auth.log.4.bz2:Feb  6 17:37:00 acsvfbsd02 syncserver[49881]:
>DIGEST-MD5 server step 2
>auth.log.4.bz2:Feb  6 17:37:00 acsvfbsd02 syncserver[49881]: no user in db
>So this meens for me that the sync communication would be accepted,
>isn't it? If I check the mails on both servers, they are identicaly.

>Cyrus  sync client:
>sync_host: server1
>sync_authname: test
>sync_password: xxxx
>sync_machineid: 1
>sync_log: 1
>sync_repeat_interval: 1
>Cyrus  sync server:
>sync_machineid: 2
>sync_repeat_interval: 1
>In the past I used sasldb2.db as password store. Now I use
>saslauthd/Kerberos5 which is works as expected. As described in the
>docs, DIGEST-MD5 and CRAM-MD5 use only the sasldb. So I store the user
>test on both servers in the sasldb. The result are the same. I also
>study around the mech-list but I use sasl_mech_list: PLAIN LOGIN
>DIGEST-MD5 CRAM-MD5 and sasl_mech_list: PLAIN LOGIN. The result is
>also the same.

You can use force_sasl_client_mech or <host shortname>_mechs on your sync
client to force a particular mech (see the imapd.conf man page).

Were you specifying sasl_mech_list on the sync server?

You can explicitly set the server side mech list for just the sync_server
process with:

syncserver_sasl_mech_list: PLAIN

Assuming you're using 'syncserver' as the sync_server service name
in cyrus.conf.

Dan White

More information about the Info-cyrus mailing list