On Tue, Jan 16, 2007 at 07:57:47AM +0100, Turbo Fredriksson wrote:
Quoting mouss <mlis...@free.fr>:
Turbo Fredriksson wrote:
Devin> Simple solution: set $HOME to /var/mail/<domain>/<user>/
Didn't/don't work because maildrop does the cd BEFORE anything else/it
reads system maildroprc.
# grep MYSQL_HOME_FIELD /usr/pkg/etc/authlib/authmysqlrc
MYSQL_HOME_FIELD '/var/mail'
works with other backends as well.
here, maildroprc is responsible of loading per user config files.
I've had this al along:
----- s n i p -----
root@aurora# cd /etc/courier/
root@aurora# grep -i home *
authldaprc:##NAME: LDAP_HOMEDIR:0
authldaprc:# The HOMEDIR attribute MUST exist, and we MUST be able to chdir to
it
authldaprc:LDAP_HOMEDIR mailMessageStore
authldaprc:# If homeDirectory is not an absolute path, define the root of the
----- s n i p -----
It STILL does a cd to $HOME (i.e. homeDirectory). If that's because
libnss-ldap I'm not sure, but still...
Yes. $HOME should always be expected to exist for a number of good
reasons.
Now, seeing as you have this piece of goodness:
authldaprc:LDAP_HOMEDIR mailMessageStore
you should be golden. However, is you are doing something nasty like
having your Maildirs being created in your mail filters, then you get
what you deserve. See my discussion in the recent thread: "maildrop
and maildir creation: it can't, why?"
33 messages in net.sourceforge.lists.courier-maildropRe: [maildropl] Avoiding '/usr/bin/ma...
