[Dovecot] Question about lda & auth_socket_path

[Jahnke-Zumbusch, Dirk]

Hi all,

storing e-mails (using postfix) via dovecot-lda fails and I assume this
is related with a auth_socket configuration problem. But I am at a dead
end, so perhaps anybody has got a hint for me:

This is dovecot-2.0.8 on Solaris 10:


10-auth.conf and its include:
-----------------------------
...
userdb {
  driver = static
  args = uid=104 gid=104 home=/some/path/%u
}


Relevant parts of 10-mail.conf:
---------------------------------
...
auth_socket_path = /var/run/dovecot/auth-userdb



Relevant parts of 10-master.conf:
---------------------------------
...service auth {
  unix_listener auth-userdb {
    mode = 0644
    user = vmail
    #group =
  }
}

service auth-worker {
  user = root
}



Relevant parts of 15-lda.conf:
---------------------------------
...
protocol lda {
  # Space separated list of plugins to load (default is global
mail_plugins).
  #mail_plugins = $mail_plugins
}


# ls -l /var/run/dovecot/auth-userdb
srw-r--r--   1 vmail    root           0 Jan 12 15:49
/var/run/dovecot/auth-userdb


Using dovecot-lda for mail delivery or doveadm for user inquirement
fails:

via debug_log_path:
-------------------
Jan 12 16:04:14 auth: Debug: Loading modules from directory:
/dovecot/code/dovecot-2.0.8/lib/dovecot/auth
Jan 12 16:04:14 auth: Debug: passwd-file /store1/db/masterusers.passwd:
Read 1 users
Jan 12 16:04:14 auth: Debug: master in: USER    1       djahnke
service=lda
Jan 12 16:04:14 auth: Debug: password(djahnke): passdb doesn't support
credential lookups
Jan 12 16:04:14 auth: Debug: master out: FAIL   1
Jan 12 16:04:14 lda: Debug: auth input:

via syslog:
-----------
Jan 12 16:04:14 deliver1 dovecot: [ID 583609 local0.error] auth: Error:
static(djahnke): passdb doesn't support lookups, can't verify user's
existence
Jan 12 16:04:14 deliver1 dovecot: [ID 583609 local0.error] lda: Error:
user djahnke: Auth USER lookup failed
Jan 12 16:04:14 deliver1 dovecot: [ID 583609 local0.crit] lda: Fatal:
Internal error occurred. Refer to server log for more information.

When I use "allow_all_users=yes" everything works fine, so I think
somehow the communication with the socket fails. I cannot see what
I have missed :-(


Any suggestions what I should look for / configure ?

Any help appreciated,
cheers,
Drik
--
Dirk Jahnke-Zumbusch              Deutsches Elektronen-Synchrotron DESY
IT Information Fabrics              Member of the Helmholtz Association
D-22603 Hamburg                        Notkestrasse 85  / 22607 Hamburg
T: +49-40-899.81760   F: +49-40-899.41760  dirk.jahnke-zumbusch at desy.de