I'm wondering if this is a version issue with Mail.app? Are you on
OS X 10.3 or 10.4?
The reason I ask is that we also migrated from Courier IMAP to
Dovecot 1.0alpha5 and then beta3, and we did not have this problem
with Mail.app that either of you are describing.
I did have to remove the "INBOX." prefix from my Mail.app
configurations. I also renamed all of the existing folders in my
Maildir from INBOX.foldername to .foldername, because after removing
the "INBOX." prefix Mail.app could not see them.
Before I renamed all of the existing folders and changed the prefix
in Mail.app, I had also tried setting up alternate namespaces as
described in the wiki documentation for converting from Courier, but
that did not seem to work. Mail.app and Thunderbird clients could
not see their IMAP folders with the courier-style namespace
configuration.
-- Roger J. Weeks Systems & Network Administrator Mendocino Community Network
On Feb 14, 2006, at 8:45 AM, dovecot-request@dovecot.org wrote:
Date: Tue, 14 Feb 2006 08:44:53 -0800 From: Steve Pellegrin steve@convoglio.com Subject: Re: [Dovecot] Mail.app help To: Mike Garfias mike@garfias.org
Sorry to respond so late to this, perhaps my experience will help.
I believe that Mike's problem is caused by weird behavior in Mail.App. I had the same issue after switching from Courier IMAP to Dovecot 1.0beta2. (Courier requires the INBOX prefix).
I only experienced this problem for folders that I defined myself. In other words, the "standard" Sent, Trash and so on were OK. What I found was that if I had a custom folder, call it Dovecot, and a rule that directed mail list messages into that folder, Mail.App would insist on creating INBOX.Dovecot, even though .Dovecot already
existed.It's as if Mail.App had internalized the INBOX prefix in some secret place and would not let go of it even though I changed the prefix setting to be empty.
My solution was to delete my mail account, shut down Mail.App, re- launch it, and recreate the mail account. Now, everything works as expected.
-Steve