Lynn Winebarger wrote:
> You can set the name of the attribute type for the homedirectory to
> something else that won't conflict in qmail-ldap.h.
I would prefer not to hack around inside the source if I can. If you do
this, and someone else tries to upgrade the system a year down the line
the hacks vanish and everything breaks.
> The way qmail-local and courier-imap handle it is
> this: qmail-lspawn/auth_* switch to the home directory. Then there is a
> parameter passed (for qmail-local it's called aliasempty on the command
> line, for courier-imap it's the MAILDIR environment variable. Then
> qmail-local/courier-imap switch to the directory it's passed, from
> whatever the current working directory is (i.e. the home directory).
So if the mailmessagestore attribute has a leading /, it will jump out
of the homedirectory completely and into the mail directory instead? If
so, then it will work fine.
What happens though if the homeDirectory attribute is missing, or does
not exist? Does qmail-ldap silently ignore the error and still try to
change to the mailmessagestore directory? (I think it should).
Some of the people in my LDAP tree have corresponding system access, but
most people don't, and I want to keep it that way.
Regards,
Graham
--
-----------------------------------------
[EMAIL PROTECTED] "There's a moon
over Bourbon Street
tonight..."
S/MIME Cryptographic Signature
