Postfix 'falling back' on sasldb? I don't want it to!

7 msg	Postfix 2.2.5 on latest Solaris 9 x86
5 msg	Postfix Relay, and Pop-before-smtp
12 msg	Newb Question
13 msg	Best defense against this?
1 msg	undelivered mail problem - SOLVED
4 msg	Legal local-part
3 msg	virtual_alias_domains with mysql: 'User unknown...
6 msg	Submission port (587): howto to use differente ...
5 msg	When does smtpd_reject_unlisted_recipient kick in?

Postfix 'falling back' on sasldb? I don't want ...
\ Stefán Freyr Stefánsson (22 Sep 2007)
. \ (Wietse Venema) (22 Sep 2007)
. \ Patrick Ben Koetter (22 Sep 2007)
. . \ Stefán Freyr Stefánsson (22 Sep 2007)

3 msg	Nested access maps (I think ;))
3 msg	Suppression of encoding bad header function in ...
4 msg	RE: Catchall ??
3 msg	problem with .forward files + forwarding loops
5 msg	Postfix Strange Behaviours
7 msg	Content filter question, based upon auth'ed or not
28 msg	Mail stuck in active queue for loooong time
11 msg	How to stop a user from changing the 'From:' he...
10 msg	[Semi-OT] blocked port 465, anywhere?
7 msg	chroot problems on Nexenta (OpenSolaris)

Subject:	Postfix 'falling back' on sasldb? I don't want it to!
Group:	Postfix-users
From:	Stefán Freyr Stefánsson
Date:	22 Sep 2007

Hello.

I've been battling setting up Postfix to authenticate SMTP users via
SASL on a Nexenta (Debian like OpenSolaris distro). For this I've been
following various howtos and to make a long story short I have managed
to get this up and running so my users are now authenticated from the
sasldb.

I configured SASL to use the sasldb backend and I've configured
Postfix (to the best of my knowledge) to use the saslauthd by:
1) creating the file /etc/postfix/sasl/smtpd.conf which contains the line:
pwcheck_method: saslauthd
2) editing the main.cf file to contain this:
smtpd_sasl_application_name = smtpd
smtpd_sasl_auth_enable = yes
smtpd_sasl_security_options = noanonymous
smtpd_sasl_local_domain = $myhostname
broken_sasl_auth_clients = yes
smtpd_recipient_restrictions =
permit_sasl_authenticated,
permit_mynetworks,
reject_unauth_destination

As I said... this works... even too well.

The problem is that I tried turning off saslauthd but Postfix is still
authenticating users from my sasldb!

I did an strace (actually called truff on Solaris) run of Postfix and
found out that grepping the output for "sasldb" yielded a lot of
responses BOTH when saslauthd was turned of as well as when it was
running. Grepping for "saslauth" however, yields nothing!

Can anyone explain to me why Postfix seems to be "falling back" to a
mechanism that it shouldn't know anything about (according to my
configuration files at least)? How can I force Postfix to use
saslauthd and _only_ saslauthd?

With kind regards and gratitude for an otherwise great piece of software.
Stefan Freyr.

p.s. I'm attaching a link to both trace files in case anyone is
interested. Both contain the call traces for postfix (and all child
processes), one of them is for a run when saslauthd was running and
the other one was for a run when saslauthd was not running. Both
"runs" just consisted of starting postfix, sending a single mail (mail
was identical in both runs) using SMTP authentication and turning off
postfix.

Here are the files but be warned, they're each ~1.6Mb:
http://datalab.ru.is/~stefan/postfix_nosasl.truss
http://datalab.ru.is/~stefan/postfix_withsasl.truss