OSEC

Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com
Re: /usr/lib/sasl2 failed to open directory

From: Mark Edwards (markantsclimbtree.com)
Date: Sun May 27 2007 - 19:39:19 CDT


On May 27, 2007, at 5:12 PM, Wietse Venema wrote:

> Mark Edwards:
>> May 27 16:35:44 mini postfix/trivial-rewrite[4091]: looking for
>> plugins in '/usr/lib/sasl2', failed to open directory, error: No such
>> file or directory
>> May 27 16:35:44 mini postfix/smtpd[4092]: looking for plugins in '/
>> usr/lib/sasl2', failed to open directory, error: No such file or
>> directory
>> May 27 16:35:47 mini postfix/cleanup[4097]: looking for plugins in '/
>> usr/lib/sasl2', failed to open directory, error: No such file or
>> directory
>
> This has absolutely nothing to do with Cyrus SASL for SMTP.
>
> Perhaps you're using LDAP with SASL authentication.
>
> In that case it's the LDAP library that is doing Cyrus SASL calls.
> No amount of smtpd_sasl_mumble tweaking will change that.

AHA! That's it. I am indeed using LDAP for authentication via /usr/
lib/postfix/dict_ldap.so

I temporarily disabled ldap and relayed a message, and no errors.

Sorry to have occupied so much of your time, but perhaps this will
help someone else avoid a similar investigation. What was really
confusing is that these errors were not reported with postfix 2.3.3,
despite an identical configuration.

So, just to finish this, is it correct that, assuming I want/need to
use postfix 2.3.8 with dict_ldap.so, I can only avoid these errors by
disabling chroot or building proper usr/lib/sasl2 directory within /
var/spool/postfix? Are those my only two options?

Thanks so much.

--
Mark Edwards