I've had my maildir setup this way for many months, as the first version
of Apple Mail also had a similar bug. No stability problems as far as I
can tell. Its a hack, but it seems to work. Courier shouldn't have any
problem with multiple access to the same mailbox under different names
because it uses locks on the files in the maildir, which should be valid
no matter how it got to them. I wouldn't think there'd be any security
implications, as it seems a fairly straightforward thing to do.
James
On Friday, November 9, 2001, at 02:42 PM, Ross Alexander Patterson
wrote:
xxx@xxx:~ $ ls -al Maildir/
total 32
drwx--S--- 7 xxx xxx 4096 Nov 8 11:07 .
drwsrws--- 9 xxx xxx 4096 Nov 9 10:07 ..
lrwxrwxrwx 1 xxx xxx 1 Nov 8 11:03 .Inbox -> .
drwx--S--- 5 xxx xxx 4096 Nov 8 11:03 .Out
drwx--S--- 5 xxx xxx 4096 Nov 8 11:06 .Trash
-rw-r--r-- 1 xxx xxx 15 Nov 8 11:07 courierimapuiddb
drwx------ 2 xxx xxx 4096 Nov 8 11:07 cur
drwx------ 2 xxx xxx 4096 Nov 8 11:07 new
drwx------ 2 xxx xxx 4096 Nov 8 11:07 tmp
The symlink shown above along with setting the "Location prefix:" in
the Eudora IMAP configuration to "INBOX." seems to offer the best of
both worlds, allowing the "proper" IMAP clients and the "incorrect"
IMAP clients to access ~/Maildir more appropriately. In Eudora at
least, all IMAP boxes in ~/Maildir show up at the root level of the
IMAP personality, and the ".Inbox" symlink causes Eudora to show the
contents of ~/Maildir as a IMAP box called "Inbox" also at the root
level of the personality.
Now I'm describing all this because I'm sure there must be a problem
with this. Any IMAP boxes created in INBOX.Inbox will not be visible
in Pine which refuses to show any IMAP box in "INBOX." that is named
any capitalization of "inbox". Also, folders created in "INBOX.Inbox"
show up only in "INBOX.Inbox" and not in "INBOX" since on the server
filesystem "INBOX.Inbox.xxx" is created as ~/Maildir/.Inbox.xxx and
not in the actual ~/Maildir/.Inbox maildir. Mulberry shows both
"INBOX" and "Inbox" as separate folders which have the same message
contents, of course.
But my biggest concern is the endlessly deep symlink. I've never done
that before and I'm ashamed to admit I have no idea how it might
affect the security or stability of the system.
Please do comment on this workaround.
2 messages in net.sourceforge.lists.courier-usersRe: [courier-users] Workaround for Eu...
