[Dovecot] unknown namespace with Mac OS client
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-----
Barry Warsaw writes:
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
Thanks. Made the change and let the customer know to try again.
I don't know if it's "right" but so far it seems to work.
Will know the results once the customer calls/writes back.
Also agree that if this works it should be on the wiki, or even better in the sample dovecot.conf file.. that way anyone that needs to support multiple domains (ie ISPs) would know to have those settings.
I am even wondering if there would be any drawbacks to have those settings as defaults.
Barry Warsaw writes:
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.
Heard back from the customer. That setting change worked.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Dec 28, 2006, at 12:25 AM, Francisco Reyes wrote:
Barry Warsaw writes:
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.
Heard back from the customer. That setting change worked.
Cool, same here. Works for both Mail.app and Thunderbird.
One weird thing I've noticed though since switching to Dovecot. It
used to be that Mail.app would move junk messages from my inbox to
the Junk folder, and they would be deleted from my inbox. Now it
seems that, while they're still moved, they aren't removed from inbox
until I expunge all deleted messages. Seems a little weird, and I
can't say for sure it's because of the change to Dovecot, but that's
the only thing that's different now.
Oh well.
- -Barry
-----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (Darwin)
iQCVAwUBRZNl1nEjvBPtnXfVAQLnOQP/Va0W6ZkVfUSyncuIE61e1vUXpPofmDTT kLKKlwTXbrGQfQBXC3SEx8jidAgFdFZUjVG0QldGzQEms+3Ecy3akKp5sm+LcF+e Ft+dsDoLPUlDiTmqejXNF0Tf580a79c9encyaVZIu4oJf2lREy79OVSLCxikMA03 B5I7MGBfAaI= =WyZ+ -----END PGP SIGNATURE-----
On Thu, 2006-12-28 at 01:36 -0500, Barry Warsaw wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Dec 28, 2006, at 12:25 AM, Francisco Reyes wrote:
Barry Warsaw writes:
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.
Heard back from the customer. That setting change worked.
Cool, same here. Works for both Mail.app and Thunderbird.
One weird thing I've noticed though since switching to Dovecot. It
used to be that Mail.app would move junk messages from my inbox to
the Junk folder, and they would be deleted from my inbox. Now it
seems that, while they're still moved, they aren't removed from inbox
until I expunge all deleted messages. Seems a little weird, and I
can't say for sure it's because of the change to Dovecot, but that's
the only thing that's different now.
I had tried this a while ago with rc5, and I couldn't remember why I reverted, but now I do. Both Evolution and IMP have problems. Evolution shows NO folders at all. IMP takes the first namespace as personal, and the second as shared, so you end up with two sets of all the folders :(
I guess I'm still stuck with courier on an alternate port for my Mail.app users :(
Rick
Oh well.
- -Barry
-----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (Darwin)
iQCVAwUBRZNl1nEjvBPtnXfVAQLnOQP/Va0W6ZkVfUSyncuIE61e1vUXpPofmDTT kLKKlwTXbrGQfQBXC3SEx8jidAgFdFZUjVG0QldGzQEms+3Ecy3akKp5sm+LcF+e Ft+dsDoLPUlDiTmqejXNF0Tf580a79c9encyaVZIu4oJf2lREy79OVSLCxikMA03 B5I7MGBfAaI= =WyZ+ -----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.
Timo Sirainen writes:
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.
I used the solution from Barry Warsaw which he explained at: http://www.dovecot.org/list/dovecot/2006-December/018301.html
Since making that change the mail.app client was able to subcribe/see all folders.
On 3.1.2007, at 20.00, Francisco Reyes wrote:
Timo Sirainen writes:
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 ignoresOn 27.12.2006, at 16.07, Francisco Reyes wrote: the setting.
I used the solution from Barry Warsaw which he explained at: http://www.dovecot.org/list/dovecot/2006-December/018301.html
Since making that change the mail.app client was able to subcribe/ see all folders.
I don't see why that would change anything for the "unknown
namespace" issue, but anyway that solution is a pretty ugly kludge,
that won't necessarily work in future Dovecot versions.
Timo Sirainen writes:
I used the solution from Barry Warsaw which he explained at: http://www.dovecot.org/list/dovecot/2006-December/018301.html
Since making that change the mail.app client was able to subcribe/ see all folders.
I don't see why that would change anything for the "unknown
namespace" issue, but anyway that solution is a pretty ugly kludge,
that won't necessarily work in future Dovecot versions.
So what do you recommend then? We are migrating to Dovecot and we don't have a mail.app application to test, so we depended on the users from one domain to let us know something is wrong. Since we changed them to Dovecot they could not use folders. They could only see the INBOX.
If there is some debugging that we could turn on to send to you? I would be more than happy to do it.
Why would future version "break" that setup?
On 4.1.2007, at 1.48, Francisco Reyes wrote:
Timo Sirainen writes:
I used the solution from Barry Warsaw which he explained at: http://www.dovecot.org/list/dovecot/2006-December/018301.html
Since making that change the mail.app client was able to
subcribe/ see all folders. I don't see why that would change anything for the "unknown
namespace" issue, but anyway that solution is a pretty ugly
kludge, that won't necessarily work in future Dovecot versions.So what do you recommend then? We are migrating to Dovecot and we don't have a mail.app
application to test, so we depended on the users from one domain to
let us know something is wrong. Since we changed them to Dovecot
they could not use folders. They could only see the INBOX.
Hmm. That's a bit weird.
If there is some debugging that we could turn on to send to you? I
would be more than happy to do it.
I'd like to know what causes the "Unknown namespace" error to occur.
That'd require you to have rawlogging enabled for the user (http://
dovecot.org/bugreport.html) and remove the other namespace.
Why would future version "break" that setup?
Hmm. Actually now that I think of it, it's not necessarily that much
broken. I originally thought that they'd have identical namespace
prefixes, but since they're INBOX. and INBOX/ they're a bit
different. :) Anyway you should mark one of them with hidden=yes so
clients that support namespaces won't show all the mailboxes twice.
Also make only one of them have inbox=yes.
Still I don't see why/where Mail.app would be trying to use / separator.
Timo Sirainen writes:
I'd like to know what causes the "Unknown namespace" error to occur.
That'd require you to have rawlogging enabled for the user (http:// dovecot.org/bugreport.html) and remove the other namespace.
I likely will need to see if one of our workers has a Mac at home. Can't be making the change on the production machine as it will impact paying customers.
Hmm. Actually now that I think of it, it's not necessarily that much
broken. I originally thought that they'd have identical namespace
prefixes, but since they're INBOX. and INBOX/ they're a bit
different. :) Anyway you should mark one of them with hidden=yes so
In my original email I asked if putting that setting would help and Barry Warsaw replied that it would not help. I think he tried it.
clients that support namespaces won't show all the mailboxes twice.
Also make only one of them have inbox=yes.
Ok, will try that with the next machine before it goes into production, but I guess I will need to find out if someone at work uses mail.app at home and can help me with the testing.. or perhaps see if someone on this list is willing to help with this. I could give them a test account on the next machine we are setting up this week.. This was not easy for us to troubleshoot/test/diagnose because we don't have a machine with Mail.app to test.
Hmm. Actually now that I think of it, it's not necessarily that much
broken. I originally thought that they'd have identical namespace
prefixes, but since they're INBOX. and INBOX/ they're a bit
different. :) Anyway you should mark one of them with hidden=yes soIn my original email I asked if putting that setting would help and Barry Warsaw replied that it would not help. I think he tried it.
clients that support namespaces won't show all the mailboxes twice.
Also make only one of them have inbox=yes.Ok, will try that with the next machine before it goes into production, but I guess I will need to find out if someone at work uses mail.app at home and can help me with the testing.. or perhaps see if someone on this list is willing to help with this. I could give them a test account on the next machine we are setting up this week.. This was not easy for us to troubleshoot/test/diagnose because we don't have a machine with Mail.app to test.
I have a Mac - and I also run Thunderbird, Evolution and Horde/IMP. The last two I had issues with when I had those 'funky' namespace settings that fixed Mail.app.
I have some of my own server work to do - but I might not even get that far this month. I do have a Horde/IMP beta site that I could redirect to test that out.
On Jan 4, 2007, at 8:22 AM, Rick Romero wrote:
Hmm. Actually now that I think of it, it's not necessarily that much broken. I originally thought that they'd have identical namespace prefixes, but since they're INBOX. and INBOX/ they're a bit different. :) Anyway you should mark one of them with hidden=yes so
In my original email I asked if putting that setting would help
and Barry Warsaw replied that it would not help. I think he tried it.clients that support namespaces won't show all the mailboxes twice. Also make only one of them have inbox=yes.
Ok, will try that with the next machine before it goes into
production, but I guess I will need to find out if someone at work uses mail.app
at home and can help me with the testing.. or perhaps see if someone on
this list is willing to help with this. I could give them a test account on the
next machine we are setting up this week.. This was not easy for us to troubleshoot/test/diagnose because we don't have a machine with
Mail.app to test.I have a Mac - and I also run Thunderbird, Evolution and Horde/ IMP. The last two I had issues with when I had those 'funky' namespace settings that fixed Mail.app.
I have some of my own server work to do - but I might not even get
that far this month. I do have a Horde/IMP beta site that I could redirect to test that out.
Actually, I can't test it out. I've upgraded to OSX 10.4, and the
problem with Mail.app (now 2.0.7) appears to be fixed.
Rick
Actually, I can't test it out. I've upgraded to OSX 10.4, and the
problem with Mail.app (now 2.0.7) appears to be fixed. Interesting... Because it's broken on my systems with 10.4 and Mail 2.1Kenny Dail kend@amigo.net
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Jan 11, 2007, at 6:58 AM, Kenny Dail wrote:
Actually, I can't test it out. I've upgraded to OSX 10.4, and the problem with Mail.app (now 2.0.7) appears to be fixed. Interesting... Because it's broken on my systems with 10.4 and Mail
2.1
Same here.
- -Barry
-----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (Darwin)
iQCVAwUBRaY6UXEjvBPtnXfVAQJCgwP/YUN4GVvXYzTooCL3XtiNPTNuuo33JnPn 2ajMvtk57aQoyheVpe3gj/OB01lRXDIUXplznayJ+8TCLq/gHc2ytxyBvtsxOaep IkAjZuIFn/CunhD/pdWMx0cTmmaRI+X8o9sTS6AdJ8xkrCAOQlNGKqzpY91p/79F gOx0oFQLQP0= =AxSk -----END PGP SIGNATURE-----
On Thu, 2007-01-11 at 08:23 -0500, Barry Warsaw wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Jan 11, 2007, at 6:58 AM, Kenny Dail wrote:
Actually, I can't test it out. I've upgraded to OSX 10.4, and the problem with Mail.app (now 2.0.7) appears to be fixed. Interesting... Because it's broken on my systems with 10.4 and Mail
2.1Same here.
Well what the heck? I'm still on RC7 if that makes any difference.
And why, if I have no updates in queue, is my version of Mail.App older?
Hmm
Here's my config, for sh*ts and giggles:
base_dir = /var/run/dovecot/ protocols = imap imaps listen = * disable_plaintext_auth = no shutdown_clients = yes log_path = /var/log/dovecot/dovecot.log info_log_path = /var/log/dovecot/dovecot_info.log log_timestamp = "%b %d %H:%M:%S "
ssl_cert_file = /usr/local/share/courier-imap/mail-vfemail-godaddy.crt ssl_key_file = /usr/local/share/courier-imap/mail-vfemail-godaddy.key # These certs suck, FYI :)
verbose_ssl = no
login_dir = /var/run/dovecot/login
login_user = nobody
login_greeting = VFEmail IMAP Dovecot ready.
namespace private { separator = . prefix = INBOX. inbox = yes }
mail_debug = no
verbose_proctitle = yes
first_valid_uid = 89 last_valid_uid = 0
protocol imap { mail_plugins = quota imap_quota imap_client_workarounds = outlook-idle }
protocol pop3 {
}
protocol lda { postmaster_address = admin@vfemail.net
}
auth_verbose = no auth_debug = no
auth default { mechanisms = plain
passdb checkpassword { args = /usr/local/vpopmail/bin/vchkpw } userdb prefetch { }
user = vpopmail
}
dict { }
plugin { quota = maildir
}
On Jan 11, 2007, at 6:59 AM, Rick Romero wrote:
On Thu, 2007-01-11 at 08:23 -0500, Barry Warsaw wrote:
On Jan 11, 2007, at 6:58 AM, Kenny Dail wrote:
Actually, I can't test it out. I've upgraded to OSX 10.4, and the problem with Mail.app (now 2.0.7) appears to be fixed. Interesting... Because it's broken on my systems with 10.4 and Mail 2.1
Same here.
Well what the heck? I'm still on RC7 if that makes any difference. I'm on RC15 still. I wouldn't mind setting up an account on my server
for you to see if that client works with my setup, to check if the
version matters.
And why, if I have no updates in queue, is my version of Mail.App
older?
are you up to 10.4.8? But then if yours is working, I maybe want to
get that version ;)
Hmm
Here's my config, for sh*ts and giggles:
and my config: protocols = imap imaps pop3 pop3s disable_plaintext_auth = no login_greeting = amigo.net ready. mail_location = maildir:%h/Maildir namespace private { separator = . prefix = INBOX. inbox = yes hidden = no } mail_extra_groups = mail mmap_disable = yes lock_method = dotlock first_valid_uid = 465 valid_chroot_dirs = /var/mail/virtual maildir_copy_with_hardlinks = yes protocol imap { mail_plugins = quota imap_quota trash login_greeting_capability = yes imap_client_workarounds = outlook-idle } protocol pop3 { pop3_uidl_format = %08Xu%08Xv mail_plugins = quota pop3_client_workarounds = outlook-no-nuls oe-ns-eoh } protocol lda { postmaster_address = postmaster@amigo.net } auth_default_realm = amigo.net auth_username_translation = %@ auth_username_format = %Ln@%d auth_worker_max_count = 60 auth default { mechanisms = plain login apop digest-md5 cram-md5 passdb sql { args = /etc/dovecot/dovecot-sql.conf } userdb prefetch { } user = vmail count = 1 socket listen { master { path = /var/run/dovecot/auth-master mode = 0660 user = postfix group = mail } client { path = /var/run/dovecot/auth-client mode = 0660 } } } plugin { quota = maildir trash = /etc/dovecot/dovecot-trash.conf }
On Thu, 2007-01-11 at 07:49 -0700, Ken Dail wrote:
On Jan 11, 2007, at 6:59 AM, Rick Romero wrote:
On Thu, 2007-01-11 at 08:23 -0500, Barry Warsaw wrote:
On Jan 11, 2007, at 6:58 AM, Kenny Dail wrote:
Actually, I can't test it out. I've upgraded to OSX 10.4, and the problem with Mail.app (now 2.0.7) appears to be fixed. Interesting... Because it's broken on my systems with 10.4 and Mail 2.1
Same here.
Well what the heck? I'm still on RC7 if that makes any difference. I'm on RC15 still. I wouldn't mind setting up an account on my server
for you to see if that client works with my setup, to check if the
version matters.
I could do that - but I won't be able to access it until tonite.
Just for giggles, you could create an account on vfemail.net and see
what happens with your client on my server.
And why, if I have no updates in queue, is my version of Mail.App
older?are you up to 10.4.8? But then if yours is working, I maybe want to
get that version ;)
Hmm I don't believe my 10.4 is that high. What's odd though is that an intermediate version of Mail.app would work, then break again in the next version....
Rick
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Jan 11, 2007, at 10:11 AM, Rick Romero wrote:
Hmm I don't believe my 10.4 is that high. What's odd though is
that an intermediate version of Mail.app would work, then break again in the next version....
FTR, I'm still on rc15, OS X 10.4.8, Mail.app 2.1.1 (752.3). AFAIK,
these are the most current versions available. I'm not really able
to install and test a newer Dovecot release atm, but I could probably
connect to a test server if someone wants to set one up. I generally
also have access to Thunderbird (both OS X and Linux), Evolution,
Claws, Entourage and Outlook (some are easier to get to than others).
- -Barry
-----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (Darwin)
iQCVAwUBRaZlb3EjvBPtnXfVAQLsWgP+OIub7w8I4mORcSuX1afo17DLUFk9/peX aASU5PlJ0x5UnkLZ1WdrHgzsprFBrd2Sy0rL7XMm4FtbOW5R255ddSeoShMG4CUF ycsb0yOzDDrljyJpiNgr40f5K1enh5ekU8gOEs0TSmTmgs1p/1A47eMlLAwYMniD /RkrPhW5iK8= =L8BX -----END PGP SIGNATURE-----
On Thu, 2007-01-11 at 11:27 -0500, Barry Warsaw wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Jan 11, 2007, at 10:11 AM, Rick Romero wrote:
Hmm I don't believe my 10.4 is that high. What's odd though is
that an intermediate version of Mail.app would work, then break again in the next version....FTR, I'm still on rc15, OS X 10.4.8, Mail.app 2.1.1 (752.3). AFAIK,
these are the most current versions available. I'm not really able
to install and test a newer Dovecot release atm, but I could probably
connect to a test server if someone wants to set one up. I generally
also have access to Thunderbird (both OS X and Linux), Evolution,
Claws, Entourage and Outlook (some are easier to get to than others).
If you want to try out my server, I have an old test account that disallows SMTP - server: mail.vfemail.net user: test@vfemail.net pass: 123
As an aside - to get quota's to work, I had to use the vchkpw binary for
auth, but vchkpw assumes it's called by POP. So if I disable POP
access, dovecot IMAP (or webmail) doesn't work either :/
Not really a big deal for me, just FYI. I'll ask the vpopmail guys if
they can determine auth type for vchpw based on the name, and have
vchkpw-smtp, vchkpw-imap, vchkpw-pop...
Rick
- -Barry
-----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (Darwin)
iQCVAwUBRaZlb3EjvBPtnXfVAQLsWgP+OIub7w8I4mORcSuX1afo17DLUFk9/peX aASU5PlJ0x5UnkLZ1WdrHgzsprFBrd2Sy0rL7XMm4FtbOW5R255ddSeoShMG4CUF ycsb0yOzDDrljyJpiNgr40f5K1enh5ekU8gOEs0TSmTmgs1p/1A47eMlLAwYMniD /RkrPhW5iK8= =L8BX -----END PGP SIGNATURE-----
hi,
did anybody read my first email about shared folder on this list?
Mfg. Stefan Klatt
On Jan 11, 2007, at 9:36 AM, Rick Romero wrote:
On Thu, 2007-01-11 at 11:27 -0500, Barry Warsaw wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Jan 11, 2007, at 10:11 AM, Rick Romero wrote:
Hmm I don't believe my 10.4 is that high. What's odd though is that an intermediate version of Mail.app would work, then break again in the next version....
FTR, I'm still on rc15, OS X 10.4.8, Mail.app 2.1.1 (752.3). AFAIK, these are the most current versions available. I'm not really able to install and test a newer Dovecot release atm, but I could probably connect to a test server if someone wants to set one up. I generally also have access to Thunderbird (both OS X and Linux), Evolution, Claws, Entourage and Outlook (some are easier to get to than others).
If you want to try out my server, I have an old test account that disallows SMTP - server: mail.vfemail.net user: test@vfemail.net pass: 123
Well I gave that test account, as well as one I signed up for, a try
real quick and I can get the invalid namespace. so it would
definitely appear to be a client issue and not a Dovecot issue. As an
additional factor maybe, all my clients are are still on PPC machines.
On Thu, 2007-01-11 at 14:05 -0700, Ken Dail wrote:
On Jan 11, 2007, at 9:36 AM, Rick Romero wrote:
On Thu, 2007-01-11 at 11:27 -0500, Barry Warsaw wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Jan 11, 2007, at 10:11 AM, Rick Romero wrote:
Hmm I don't believe my 10.4 is that high. What's odd though is that an intermediate version of Mail.app would work, then break again in the next version....
FTR, I'm still on rc15, OS X 10.4.8, Mail.app 2.1.1 (752.3). AFAIK, these are the most current versions available. I'm not really able to install and test a newer Dovecot release atm, but I could probably connect to a test server if someone wants to set one up. I generally also have access to Thunderbird (both OS X and Linux), Evolution, Claws, Entourage and Outlook (some are easier to get to than others).
If you want to try out my server, I have an old test account that disallows SMTP - server: mail.vfemail.net user: test@vfemail.net pass: 123
Well I gave that test account, as well as one I signed up for, a try
real quick and I can get the invalid namespace. so it would
definitely appear to be a client issue and not a Dovecot issue. As an
additional factor maybe, all my clients are are still on PPC machines.
Ahh yes PPC - Good thought, but so is my client ;)
So it must just be my version that isn't broken. I wonder if I can just post it on a website and someone can try it out without really installing it...
That's the way all the other programs on the Mac seem to work. :/
Rick
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Jan 3, 2007, at 6:56 PM, Timo Sirainen wrote:
I'd like to know what causes the "Unknown namespace" error to
occur. That'd require you to have rawlogging enabled for the user
(http://dovecot.org/bugreport.html) and remove the other namespace.
Oh, my previous post only removed the INBOX/ namespace. Do you want
me to run it again without the INBOX. namespace, and/or without both
namespaces?
Why would future version "break" that setup?
Hmm. Actually now that I think of it, it's not necessarily that
much broken. I originally thought that they'd have identical
namespace prefixes, but since they're INBOX. and INBOX/ they're a
bit different. :) Anyway you should mark one of them with
hidden=yes so clients that support namespaces won't show all the
mailboxes twice. Also make only one of them have inbox=yes.
It doesn't seem to matter since Mail.app appears to only care about
INBOX/ and Thunderbird only cares about INBOX. At last AFAICT, the
two don't interfere at all.
Still I don't see why/where Mail.app would be trying to use /
separator.
Maybe there's some hidden Mail.app configuration variable floating
around in a plist or something?
One other thing: I just this morning hit the "too many open files"
bug that someone else just mentioned. Dovecot's been running
flawlessly for at least a week now, but starting and stopping the
dovecot executable didn't seem to help. I had to reboot the box to
get things to work again.
- -Barry
-----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (Darwin)
iQCVAwUBRZ5fOHEjvBPtnXfVAQLddgP+Occ70uDtJFd+qwg7LQjK1P3OrXOOMuru f0u1sNFRGQnvYUzZ1KGF+c6hUl4SVCGcmQ2PFlMS32cnm4FtpSkflIVZttmZYAiY B/no/77u1w1Ft+W5O8pPHD2Ga0ryulw40m06yGa7L9QsRXphddz5e5inZh7isnQv HJ5m26TfpUA= =dHqI -----END PGP SIGNATURE-----
Timo Sirainen writes:
On 4.1.2007, at 1.48, Francisco Reyes wrote:
Timo Sirainen writes:
I used the solution from Barry Warsaw which he explained at: http://www.dovecot.org/list/dovecot/2006-December/018301.html
Since making that change the mail.app client was able to
subcribe/ see all folders.
Enabling the second name space make the mail.app work, but caused all kind of strange problems.. with Squirrelmail and Horde. In particular directories were listed twice.
Don't know why it didn't seem to affect mail clients, but customers were calling to complain about on webmail (squirrelmail) and our new Horde setup.
For now we simply will keep mail.app customers in Courier.
This was on a RC15. Will try again on another server with RC19 and see if mail.app works with just one singlespace.
What we kept... #courier-imap compatibility/Thunderbird namespace private { separator = . prefix = INBOX. inbox = yes }
What solved the mail.app, but broke webmail.. and we commented out today. #-------------------------- # For MAC OS Mail.app ##namespace private { ## separator = / ## prefix = INBOX/ ## inbox = yes ##}
On Jan 30, 2007, at 9:08 PM, Francisco Reyes wrote:
Timo Sirainen writes:
On 4.1.2007, at 1.48, Francisco Reyes wrote:
Timo Sirainen writes:
I used the solution from Barry Warsaw which he explained at: http://www.dovecot.org/list/dovecot/2006-December/018301.html
Since making that change the mail.app client was able to
subcribe/ see all folders.Enabling the second name space make the mail.app work, but caused
all kind of strange problems.. with Squirrelmail and Horde. In
particular directories were listed twice.Don't know why it didn't seem to affect mail clients, but customers
were calling to complain about on webmail (squirrelmail) and our
new Horde setup.For now we simply will keep mail.app customers in Courier.
This was on a RC15. Will try again on another server with RC19 and
see if mail.app works with just one singlespace.What we kept... #courier-imap compatibility/Thunderbird namespace private { separator = . prefix = INBOX. inbox = yes }
What solved the mail.app, but broke webmail.. and we commented out
today. #-------------------------- # For MAC OS Mail.app ##namespace private { ## separator = / ## prefix = INBOX/ ## inbox = yes ##}
That's pretty much the situation I saw several different clients
behaved poorly with this kind of setup. Mail.app is just broken Maybe
Timo can put in a workaround for ignore invalid namespaces provided
by broken clients.
Ken Dail writes:
That's pretty much the situation I saw several different clients
behaved poorly with this kind of setup. Mail.app is just broken Maybe
Timo can put in a workaround for ignore invalid namespaces provided
by broken clients.
So few of our clients use mail.app that it just didn't make sense to inconvenience the majority trying to help just a handfull of clients.
Given that we have many server it is not too much of an issue to make sure we leave a couple of courier boxes behind as we migrate.. but for people who only have one server, this is likely a problem.
On Tue, 2007-01-30 at 23:08 -0500, Francisco Reyes wrote:
# For MAC OS Mail.app ##namespace private { ## separator = / ## prefix = INBOX/ ## inbox = yes ##}
hidden = yes and inbox = no would make this invisible to all but those clients that forcibly try to use / separator.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Jan 3, 2007, at 9:15 AM, Timo Sirainen wrote:
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.
I'm not sure I can help with the Courier side as it's not installed
on my new imap box. But I turned on raw logging for Dovecot, removed
the Mail.app namespace hack and started up Mail.app. Here's one
example of the .in and .out files. Sure looks like Mail.app wants an
INBOX/ namespace. Does this information help?
% less 20070105-091347-9316.in 2 CAPABILITY 3 SELECT INBOX/Python/Dot-Org 4 SELECT INBOX/Python/Humor 5 SELECT INBOX/Python/Friends 6 SELECT INBOX/Python/History 7 SELECT INBOX % less 20070105-091347-9316.out
- OK [RAWLOG TIMESTAMP] 2007-01-05 09:13:47
- CAPABILITY IMAP4rev1 SASL-IR SORT THREAD=REFERENCES MULTIAPPEND
UNSELECT LITERAL+ IDLE CHILDREN NAMESPACE LOGIN-REFERRALS 2 OK Capability completed. 3 NO Unknown namespace. 4 NO Unknown namespace. 5 NO Unknown namespace. 6 NO Unknown namespace. - FLAGS (\Answered \Flagged \Deleted \Seen \Draft $NotJunk
JunkRecorded $Junk) - OK [PERMANENTFLAGS (\Answered \Flagged \Deleted \Seen \Draft
$NotJunk JunkRecorded $Junk \*)] Flags permitted. - 1467 EXISTS
- 0 RECENT
- OK [UIDVALIDITY 1093060105] UIDs valid
- OK [UIDNEXT 296237] Predicted next UID 7 OK [READ-WRITE] Select completed.
- -Barry
-----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (Darwin)
iQCVAwUBRZ5eQHEjvBPtnXfVAQIFxAP/WWs1G3sHYWLSrRIDRhSHRGUNrYoE4PdJ IpXHQRw8ZrcPQDDrr2gdRsiWqdcG7Wpqc6A4TPjXThiWvAzhit7lh18r4sL3Bcrz ATfdB/iqRcdYWoHOM4BIc7OkmHkai+f8FZZQka/azXopag7R1shnw2Eqgawl+JVw 5rKfzWCNJtE= =6ryJ -----END PGP SIGNATURE-----
On Fri, 2007-01-05 at 09:18 -0500, Barry Warsaw wrote:
I'm not sure I can help with the Courier side as it's not installed
on my new imap box. But I turned on raw logging for Dovecot, removed
the Mail.app namespace hack and started up Mail.app. Here's one
example of the .in and .out files. Sure looks like Mail.app wants an
INBOX/ namespace. Does this information help?% less 20070105-091347-9316.in 2 CAPABILITY 3 SELECT INBOX/Python/Dot-Org 4 SELECT INBOX/Python/Humor 5 SELECT INBOX/Python/Friends
So it's not issuing even a LIST command, which means it has cached those mailbox locations earlier, which means it probably also has then seen those '/' character in the separators..
I'd guess that if you recreated the account it would work, or at least issue the LIST command. :)
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Jan 19, 2007, at 3:01 PM, Timo Sirainen wrote:
On Fri, 2007-01-05 at 09:18 -0500, Barry Warsaw wrote:
I'm not sure I can help with the Courier side as it's not installed on my new imap box. But I turned on raw logging for Dovecot, removed the Mail.app namespace hack and started up Mail.app. Here's one example of the .in and .out files. Sure looks like Mail.app wants an INBOX/ namespace. Does this information help?
% less 20070105-091347-9316.in 2 CAPABILITY 3 SELECT INBOX/Python/Dot-Org 4 SELECT INBOX/Python/Humor 5 SELECT INBOX/Python/Friends
So it's not issuing even a LIST command, which means it has cached
those mailbox locations earlier, which means it probably also has then seen those '/' character in the separators..I'd guess that if you recreated the account it would work, or at least issue the LIST command. :)
I wouldn't be surprised if you're right about the caching. Maybe a
"resynchronize" of the account would do the same. If I can some time
and some guts I may give that a shot.
- -Barry
-----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (Darwin)
iQCVAwUBRbEp8HEjvBPtnXfVAQLWFgP/f0ZqW3TJN4JOfNd86mW/h0/qnuz2Qnc2 fZ6cmJDlFQQGoJfW9MX0aAswJd9sB4YyaTIhJ2W8UbjkP44jPa/bYThB8wpGMAJf r/vdb+tBThkYDPB5APRQsDjmm1aMnmL3jPV0Vonu0PulvmAPulZcG4UG5jp7qmPb lTi3C6znjew= =Hjap -----END PGP SIGNATURE-----
participants (8)
-
Barry Warsaw
-
Francisco Reyes
-
Ken Dail
-
Kenny Dail
-
Rick Romero
-
Rick Romero
-
Stefan Klatt
-
Timo Sirainen