{"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 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 There are two ways to get rid off the warnings:<\/p>\n May 3rd, 2005:<\/strong> A slightly modified version of the patch has been integrated into Exim CVS and will be included in the next Debian release of exim4 (see Debian bug #299743<\/a>)<\/em><\/p>\n","protected":false},"excerpt":{"rendered":" The Exim 4 source code supports authentication with SASL since version 4.43. Debian started enabling this feature in exim4_4.50-2. After I’ve had upgraded to that version and replaced my saslauthd authenticators with brand-new cyrus_sasl authenticators, I’ve noticed that auth.log got flooded with entries like ‘exim4: OTP unavailable because can’t read\/write key database \/etc\/opiekeys: No suchauth.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
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
\n
\/usr\/lib\/sasl2\/libotp.*<\/code>. You’ll have to do this after each upgrade of the libsasl2-modules package.<\/li>\n
mech_list<\/code> option for SASL. This limits
sasl_listmech()<\/code> to the mechs used in the exim configuration. Other mechs won’t be tried anymore.<\/li>\n<\/ul>\n
[→ Read the rest of this entry<\/a>]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"spay_email":"","jetpack_publicize_message":"","jetpack_is_tweetstorm":false,"jetpack_publicize_feature_enabled":true},"categories":[6,3,7],"tags":[],"yoast_head":"\n\n\n\n\n\n\n\n\n\n\n\n\n\t\n\t\n\t\n