On Monday, December 20 at 08:40 PM, quoth James Smith: > Sorry that I didn't explain my setting clear enough.. > I am using bincimap with qmail-ldap and I have created an account called > vmail to hold all my users' maildir > under /var/qmail/maildirs/
Ahh, fun.
Hmm... it's possible that qmail-ldap (I don't know much about it) will
create those directories when it is delivering (I'm pretty sure vanilla
qmail will not). I assume that it's set up correctly and delivers to the
Maildir folder correctly, but it's worth checking.
> Below is my bincimap.conf:
Heh, surely not the whole thing.
> Mailbox {
> depot = "IMAPdir",
>
> type = "Maildir",
>
> path = "IMAPdir",
>
> auto create inbox = "no",
>
> auto subscribe mailboxes = "INBOX",
>
> umask = "077"
> }
Hmm... looks right to me.
> I created a user called user1 with 2 folders (IMAPDir and Maildir) in
> his directory /var/qmail/maildirs/user1/
> and do a link:
>
> ln -s var/qmail/maildirs/user1/Maildir
> var/qmail/maildirs/user1/IMAPDir/INBOX
Probably a piddly point, but you know you're missing the initial /'s
there, right? That makes it a relative link, rather than an absolute
link.
> Correct me if I am wrong, bincimap will access all the mails in
> /var/qmail/maildirs/user1/IMAPdir/INBOX and any folder
> created will be in /var/qmail/maildirs/user1/IMAPDir
That's correct as far as I'm aware.
> the INBOX and any folder created will consists of new, cur and tmp...
As far as I'm aware.
> but why is new, cur and tmp created in
> /var/qmail/maildirs/user1/IMAPdir/ whenever bincimap access the INBOX?
Very good question. First, make sure Binc is doing it and not some other
part of your system. Then send along your entire bincimap.conf and your
run file for it (I assume you're using daemontools).
Good luck,
~Kyle
--
Memory is like an orgasm---it's better when you don't have to fake it.
-- Seymour Cray
signature.asc
Description: Digital signature
