How can i tell SASL2 to stop using /etc/sasldb2 ?

[websrvr]

I think you might be better off contacting Patrick Ben Koetter about  
the book of postfix.

He wrote a very nice book (available in PDF for your viewing  
pleasure) on the inner workings/configuration of postfix which  
touches on the sasl side as well and IMHO should be a must-have for  
the mail-admin.

No it's not a shame-less plug, I get nothing out of it other than the  
satisfaction of passing on the wisdom which I have attained in my  
postfix endeavors and assistance directly from/with Patrick who  
helped me achieve the impossible in an environment that wasn't  
designed to support postfix/mysql or cyrus-sasl/mysql.

While I understand the need to resolve the issue at hand, the minor  
pittance to obtain the book is well worth the information contained  
therein and will increase your ability to troubleshoot and correct  
any issues you might encounter thus increasing your value as a mail- 
admin.

On Jul 30, 2007, at 23:42:17, Gert Cuykens wrote:

> On 7/29/07, Gert Cuykens <gert.cuykens at gmail.com> wrote:
>> Making progress now
>>
>> SASL per-process initialization failed
>> process /usr/lib/postfix/smtpd pid 5790 exit status 1
>> usr/lib/postfix/smtpd: bad command startup -- throttling
>>
>> So i can assume that it finds the smtpd.conf file but doesn't like it
>>
>> /etc/postfix/sasl/smtpd.conf
>> pwcheck_method: auxprop
>> auxprop_plugin: sql
>> mech_list: login plain cram-md5 digest-md5 ntlm
>> sql_engine: mysql
>> sql_user: dbmail
>> sql_passwd:
>> sql_database: dbmail
>> sql_statement: SELECT passwd FROM dbmail_users WHERE userid = '%u'
>> log_level: 7
>>
>
> Ok i finaly found out what it was "sql_passwd:" can not be a blank
> password it has to be a word like "sql_passwd: grrrrrrrr". Also
> changed sql_statement to sql_select , don't know if it matters.
>
> I now have no more "initialization failed" and also no more "can not
> find /etc/sasl2db"
> But my sql databases is still not receiving a query
>
> Any suggestions please ?
>