Re: Postfix+MYSQL Authentication problems

I've read what I can. I've given userid 'postfix' ALL priveleges for
127.0.0.1, localhost, and the "real" IP address - yet I continue to
get:

Jun 6 15:30:40 dns1 imapd: authdaemon: starting client module
Jun 6 15:30:40 dns1 authdaemond.mysql: failed to connect to mysql
server (server=3Dlocalhost, userid=3Dpostfix)

> Try using 127.0.0.1 instead of localhost in your authdaemon config
file and see if the problem persists.
=20
> Also search the archive for a thread named "Invalid user error"
> (about May 13th). you may have a similar problem.

Jun 6 15:30:40 dns1 imapd: authdaemon: TEMPFAIL - no more modules will
be tried

tcpdump has yielded nothing for me.

> tcpdump won't show unix socket connections.

The firewall is showing nothing being dropped or rejected.

Yes, Ralf, I KNOW it's an authentication problem - But WHERE do I have
to go to find out how to debug the authentication ? What can I post to
get some help from the list...I've been stuck for the last 4
days. Is there something I need to post ? Anyone ?

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3 D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3 D=3D=3D=3D=3D=3D

Thanks

Hmmmm Very close to the May 12th thread... What I have is SuSE 9.2,
with a downloaded version of Postfix 2.2.3 (because the distro postfix
does NOT include a mysql version). However MAILDROP is NOT installed=20
(not part of SuSE's 9.2 distro that I can tell). I was under the
impression (probably incorrectly) that MAILDROP was used for
"dropping off" the mail. I can receive to both "real" *nix users as
well as virtual domain users - I used Ralf's book as the "cookbook" so
when I got mail dumped into the appropriate
/var/spool/mail/vhosts/v-domainname/username/Maildir/new
I thought I was home free. I just wasn't able to "get" the mail, I
was
just doing a "less" to see it in the user directory. I guess I was
missing how maildrop fit in ? Should I install it - from the source,
or am I missing something ?

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3 D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

Installed maildrop...

master.cf no changes were required - the requested lines were already
there

main.cf=20
changed: mailbox_command =3D to:
mailbox_command =3D /usr/local/bin/maildrop -d ${USER}

I can't see a good connection:

Jun 6 17:16:12 xxxxx authdaemond.mysql: modules=3D"authmysql", daemons=3D=
5
Jun 6 17:16:12 xxxxx authdaemond.mysql: modules=3D"authmysql", daemons=3D=
5
Jun 6 17:16:38 xxxxx imapd: Connection, ip=3D[::ffff:192.xxx.xx.xx]
Jun 6 17:17:15 xxxxx imapd: LOGIN: DEBUG: ip=3D[::ffff:192.xxx.xx.xx],
command=3DLOGIN
Jun 6 17:17:15 xxxxx imapd: LOGIN: DEBUG: ip=3D[::ffff:192.xxx.xx.xx],
username=3Dvaliduser@my-virtualdomain.com
Jun 6 17:17:15 xxxxx imapd: authdaemon: starting client module
Jun 6 17:17:15 xxxxx imapd: authdaemon: TEMPFAIL - no more modules
will
be tried
Jun 6 17:17:20 xxxxx imapd: LOGIN FAILED, ip=3D[::ffff:192.xxx.xx.xx]

AND - Now it doesn't even seem to be looking for mysql table at all

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3 D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

Using 127.0.0.1 Appears to cause this last symptom of not using mysql
I put it back to "localhost" and it then "tries" validating against
mysql.