Paul,
Thank you for the response. I will submit a bug report today. Can you
suggest any workarounds in the mean time? I tried getting around the
issue by changing my mailbox structure like so:
Problem:
INBOX/Outgoing/2006/01
Attempted Solution
Outbox/2006/01
I tried this approach since according to my testing, mailboxes 3 levels
deep are not affected by this issue. However, I can't seem to work with
the newly created 'Outbox' the way I'd expect. Perhaps I'm opening a can
of worms with this workaround :)
Best,
Adam
Paul J Stevens wrote:
Adam,
The DELETE command handling in imap does not check the mailbox
permissions at all atm, other than determining whether the user issuing
the command is the owner.
I'll look into this. Please file a bug report so I won't forget.
Adam Kosmin wrote:
Hello again,
I haven't heard anything back about this so I thought I'd attempt to
explain the problem one more time.
I've noticed that I can delete mailboxes that have been marked as
read-only (e.g. permissions=1 in dbmail.dbmail_mailboxes).
This seems to only affect mailboxes 4 levels deep. For example,
INBOX/foo/bar is fine but INBOX/foo/bar/foobar suffers from this problem.
It's probably worth mentioning that I can not delete mail residing in
that mailbox. However, If I select the mailbox itself and attempt to
delete it, the mailbox and all of its messages are blown away.
Does anyone have any insight on this?
--
Adam Kosmin
GNU/Linux SA
Visual Trading Systems, LLC
Empire State Building
350 Fifth Avenue, Suite 6420
New York, NY 10118, USA
Email [EMAIL PROTECTED]
Phone 1 (212) 871-1747 ext. 340
