{"id":19,"date":"2005-03-22T01:11:32","date_gmt":"2005-03-22T00:11:32","guid":{"rendered":"http:\/\/blog.blackdown.de\/2005\/03\/22\/cyrus_sasl-patch-for-exim-4\/"},"modified":"2016-10-29T03:51:03","modified_gmt":"2016-10-29T01:51:03","slug":"cyrus_sasl-patch-for-exim-4","status":"publish","type":"post","link":"https:\/\/blackdown.de\/articles\/cyrus_sasl-patch-for-exim-4\/","title":{"rendered":"cyrus_sasl patch for Exim 4"},"content":{"rendered":"

The Exim 4<\/a> source code supports authentication with SASL<\/acronym><\/a> since version 4.43. Debian<\/a> started enabling this feature in exim4_4.50-2. After I’ve had upgraded to that version and replaced my saslauthd<\/em> authenticators with brand-new cyrus_sasl<\/em> authenticators, I’ve noticed that auth.log<\/code> got flooded with entries like ‘exim4: OTP unavailable because can't read\/write key database \/etc\/opiekeys: No such file or directory<\/code>.’<\/p>\n

My exim configuration uses three different cyrus_sasl<\/em> authenticators and each exim invocation resulted in three of these OTP<\/abbr> warnings because exim calls sasl_listmech()<\/code> for each configured authenticator. It doesn’t specify a limiting mech_list<\/code>, that means SASL will test which of all installed mechs actually can be used for authentication. Debian’s SASL package includes libotp.so<\/code>, so it also tries to use OTP which is not configured on my system.<\/p>\n

There are two ways to get rid off the warnings:<\/p>\n