Lynn Winebarger wrote:
> Well, this can be considered an experimental patch. I thought this
> directory handling might be the stickiest point (well, that, and the "Why
> are you 'manually' chasing domain aliases rather than using ldap's builtin
> aliasing support?").
> As far as not changing qmail-ldap.h or the Makefile, we are talking
> about a patch on a patch that says "This is no ./configure; make
> software", so buck up. At least you're not really digging into the source
> code.
The problem I have with this "this isn't ./configure..." argument is
that it's usually used when a programmer didn't want to (too lazy to?)
build in a proper configuration option, relying instead on #defines in
source files and definitions in Makefiles and saying "it's the user's
problem".
I am a programmer myself, and am quite happy to go rooting around inside
source files. But once I've done so I don't like putting those files
into production without including the patches to the base code where
this is possible. Usually the person doing the upgrade job six months
down the line is me - and I know now that I will miss something and end
up pulling my hair out no matter how good I note what I did down.
> I have it log at level 2 and 64 that there's no home directory. The
> program doing the lookup (qmail-lspawn or auth_*) will then switch to
> ldapmailroot (a control file I added - if that doesn't exist, then '/'
> will be used).
Ok.
> The next process gets whatever's in mailmessagestore (with
> some compile time options for (a) ignoring absolute mailmessagestores and
> (b) having a compiled in default mailmessagestore if that attribute
> doesn't exist) - if that doesn't exist then it gets an empty string. This
> may be incorrect behaviour.
Intuitively if a / is placed at the beginning of a path it typically
means "it's an absolute path, don't fiddle with it". As long as this is
the default behaviour (and I understand it is) then it's fine.
Regards,
Graham
--
-----------------------------------------
[EMAIL PROTECTED] "There's a moon
over Bourbon Street
tonight..."
S/MIME Cryptographic Signature
