no program should ever try to get such data from /etc/passwd directly. It
uses
the glibc which builds a transparent system to access data from various
sources
like NIS, LDAP...
That's what I figured! But maildrop's manpage has /etc/passwd listed as one
of the used files... Not 100% true I guess..
There should be a maildropldap.config file. There you set the attributes
which
contain the needed data. e.G.LDAP attribute homeDir. So if you have a
proper
ldap installation, there should be no problem.
Okay... This is where it got interesting; I am using the rpm's generated
from the tarfile, as per the instructions that come with Courier. The
maildrop configuration defined in the specfile doesn't compile with the
enable-maildropldap option, so I editted the specfile. It doesn't seem to
pickup my altered --with-ldapconfig option though, which means the
maildropldap.config file is in /etc instead of /etc/courier, but that's an
esthetic thing.
This actually seems to work somewhat; if I now execute 'maildrop -V 10 -d
ggou...@magicminds.com' I get the following:
maildrop: Changing to /data/mail/magicminds.com/ggoudsmit
maildrop: Unable to change to home directory.
So maildrop has correctly figured out where my homedirectory is, and is
trying to chdir to it to read my .mailfilter...
I have no idea why maildrop can't change to my homedir though... My maildrop
is root setuid, so I suppose it runs as root. It should be able to chdir
anywhere right?
Any idea as to what might be causing this?
If you don't use this file or ldap in maildrop, you can use pam_ldap
nss_ldap
instead. They let you access ldap through PAM and NSSWITCH (glibc)
Wouldn't that mean all user-authentication goes thru LDAP? Even local logins
and such? That wouldn't be what I want...
Regards, Gilion R. Goudsmit
4 messages in net.sourceforge.lists.courier-maildropRe: [maildropl] Maildrop used with Co...
