saslauthd missing mech "sasldb"

[MGStudioWEB]

I'm migrating from a system that has sasldb enabled as a mechanism for saslauthd.
I would prefer the authentication passwords be separate from the system login (/etc/passwd) and I won't use MySQL or other database, my solution is use a db files created by saslpasswd2 (/etc/sasldb2).
After install Centos 5.4 and compile cyrus-sasl-2.1.23 this features is disabled.

saslauthd -v

saslauthd 2.1.23
authentication mechanisms: getpwent kerberos5 pam rimap shadow

How i can do?

Help me please!

[Mark_NL]

sasldb2 is defined as auxprop

in your sasl smtpd.conf file you should define

pwcheck_method:auxprop

[MGStudioWEB]

Thanks,

what is the MECH in /etc/sysconfig/saslauthd?

I've pam but not sasldb...

[Mark_NL]

use this:

MECH=pam

[MGStudioWEB]

Ok, it works but i don't understand, i've created a user with saslpasswd2 and put permit_sasl_authenticated in smtpd_recipient_restrictions of main.cf ...
postfix authenticates the user even if the saslauthd daemon is stopped!

I've read this tutorial (http://postfix.state-of-mind.de/patr...iguration.html) but i don't understand this line:

If you plan to use sasldb instead of saslauthd on your system then you should make sure the daemon will not get started automatically when you system enters the different runlevels or when you reboot. So you either disable the daemon or remove it completely.

[MGStudioWEB]

How can Postfix autenticate sasldbuserlist users if saslauthd is stopped...?

[Mark_NL]

You can disable the automatic starting of sasauthd in centos with i THINK

chkconfig saslauthd off

I've no experience with using centos, but it's a free version of RHEL and RHEL works like that, so i assume CentOS does that as well.

[MGStudioWEB]

Thanks for your help, I've disabled the automatic starting...
I just wanted to know if it is right that Postfix authenticate the saslusers with saslauthd stopped...

[Mark_NL]

Yes, you quoted the text yourself:

If you plan to use sasldb (yes we want that) instead of saslauthd on your system then you should make sure the daemon will not get started (cool, we just did that) automatically when you system enters the different runlevels or when you reboot. So you either disable the daemon or remove it completely.

[MGStudioWEB]

Is there a way to configure the way you use the SASL user Courier (userdb) so had a user for both authentication (POP3/IMAP and SMTP)?

Many thanks