Hi Dale,
On Sun, 9 Mar 2003, Dale Woolridge wrote:
>1.
> I haven't checked this on other systems, but on mine (fbsd 4.7),
> chdir("") return -1, setting ENOENT in the process. As a result,
> Mailbox { path = ""; } behaves incorrectly.
Okay. So perhaps path = "." works better?
>2.
> Not being familiar enough with the IMAP spec, I'm assuming that
> one can issue multiple LOGIN commands within the same session.
> On some systems, putenv() may fail if no value is specified,
> so putenv("BINC_USERID") fails on fbsd 4.7. I'm not sure why
> the getenv/putenv sequence is really necessary, when you can
> replace it all with a call to unsetenv().
putenv is SVID3, POSIX and BSD 4.3, but unsetenv is only BSD 4.3. Guess we
should test for unsetenv in configure and optionally use this.
>3.
> After more vmailmgr testing, I find that a bincimap-uidpwd
> modified to append MAILDIR to the cwd may lead to other problems.
> i.
> bincimapd still thinks of the "pwd" line as a home directory,
> so it looks for local config changes in .bincimap, which would
> have to live inside the Maildir.
> ii.
> By making a clear distiction between the "pwd" line actually
> being "home" and a subsequent (optional) line containing the
> relative/absolute [maildir] path, the difference between where
> control/config files live (in "home") and where mail lives
> would be clear.
True.
> On the other hand, not much can be done with local .bincimap anyway.
Right now - no. But it is definitely a good thing to have. Since each user
can typically decide where his/her Maildir is (in .qmail or similar), I
think it should among other options be configurable.
>Attached is patch to deal with 1 and 2.
Thanks. :-)
Andy
--
Andreas Aardal Hanssen | http://www.andreas.hanssen.name/gpg
Author of Binc IMAP | Nil desperandum
