I see in this thread,
http://dovecot.org/list/dovecot/2006-April/012918.html, that others had
simmilar problems with Mac OS client.
Anyone got a working Dovecot + Mac OS setup?
In particular with RC15.
Our setup
default_mail_env = maildir:Maildir
namespace private {
separator = .
prefix = INBOX.
inbox = yes
}
Would it help to use
hidden = yes ??
Reading the description doesn't say much to me.. in particular I guess I am
not familiar with the IMAP protocol to appreciate the explanation in the
config file.
The server is getting data originally coming from a Courier setup. I wrote a
couple of scripts to convert files names and delete old setup files.
So far we have moved 3 domains to this machine and the only one with the
problem so far is the customer with the Mac client. Unless we can solve this
soon, we will have to move him back to a courier server ... until we can
figure how to solve this problem.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Dec 27, 2006, at 9:07 AM, Francisco Reyes wrote:> I see in this thread, http://dovecot.org/list/dovecot/2006-April/ > 012918.html, that others had simmilar problems with Mac OS client. > > Anyone got a working Dovecot + Mac OS setup? > In particular with RC15.Francisco, I'm in the process of switching to Dovecot too, and here is my solution to the problem: http://www.dovecot.org/list/dovecot/2006-December/018301.html I don't know if it's "right" but so far it seems to work. - -Barry P.S. no, "hidden = yes" does not help. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (Darwin) iQCVAwUBRZKJiXEjvBPtnXfVAQKPCgP+MehadGJYzhhNvJa2zYhTj1XR7mPTroaX 1Eurr2oFko8n6SXwbZagrbBTZzuErpT+/fzttg2rL3rC44+CIPNJ+H+g4x7lkDec 6mk0hcZC/RreFe9eDSxiwSP27Yp52vtfEm56uJbytEb7nC9ER70kEZHnQDs4syDl RfMeH+l3Mw4=ZZff -----END PGP SIGNATURE-----
On 27.12.2006, at 16.07, Francisco Reyes wrote:> I see in this thread, http://dovecot.org/list/dovecot/2006-April/ > 012918.html, that others had simmilar problems with Mac OS client.I don't really understand this problem. I tried this myself now: If I set IMAP Path Prefix to "INBOX.", Mail.app totally ignores the setting. But since Courier requires having the same thing to work, it's probably somehow just not working right with me. Anyway even then I was able to use Dovecot just fine, I got the "unknown namespace" error only when trying to create a new root mailbox. It would be helpful to know what exactly is the difference between Courier and Dovecot. In Dovecot's side you could easily do it with rawlog (see http://dovecot.org/bugreport.html). In Courier's side you'd have to use something else. Anyway just seeing what command gives the "unknown namespace" error would help me figuring out what the problem is. -------------- next part -------------- A non-text attachment was scrubbed... Name: PGP.sig Type: application/pgp-signature Size: 186 bytes Desc: This is a digitally signed message part URL: <http://dovecot.org/pipermail/dovecot/attachments/20070103/d3c08c9a/attachment.bin>
> > I just tried it now, I can get invalid namespace on your setup. Let me > > know if you need me to hit it more > > Looks like Mail.app is just being broken and changes '.' characters to > '/' internally.. >How hard would it be to put in a workaround for Mail.app, to ignore the namespace being supplied by the client and to use the namespace defined by the server? -- Kenny Dail <kend at amigo.net>