Re: Added ~/.<program>rc as a config file.

[Sergey Poznyakoff]

> I don't know anything about the other namespace, particularly. What's
> the setup?

Well, basically, imap4d allows to access mailboxes in three separate
namespaces: a) user's private namespace, where the user usually has
all the rights over the files, b) shared namespace, which may or may
not be writable by the user and c) other namespace, which is generally
not writable neither for the user nor for the group. The setup is
described in detail in RFC 2342. The problem arises when imap4d is
trying to open (and consequently lock) a mailbox which is located
in other (and sometimes in shared) namespace.

> My spool was writeable only by group mail, I had to change that to
> use mailutils to open my spool file. I want to add a flag to the
> locker that will cause the locker to behave the same, but call dotlock 
> instead of doing the locking itself. dotlock can be setgid mail,
> or setuid root, and it will lock the file even in a directory the
> user doesn't have write permission to (after appropriate permissions
> checks).
> 
> Will this address the problem you're talking about?

I guess it will. Do you plan to make the path to dotlock
hardcoded, or specifiable via a command-line option?


Regards,
Sergey