[Dovecot] ios clients and namespace trouble
We migrated to dovecot from courier and maintained a courier compatible namespace configuration. This resulted in ios clients needing to be manually configured in order to use the special folders correctly (delete messages, save drafts, etc) either by being given the correct "Path Prefix" or by manually selecting the special folders.
I can't fathom why apple has chosen not to support or can't detect namespace correctly and require manual configuration but if they haven't done it by now they must have some reason for it and aren't going to fix it any time soon.
Are there any creative solutions to fixing the i-clients and preventing them from needing manual configuration?
-K
Am 24.04.2013 19:39, schrieb Kelsey Cummings:
We migrated to dovecot from courier and maintained a courier compatible namespace configuration. This resulted in ios clients needing to be manually configured in order to use the special folders correctly (delete messages, save drafts, etc) either by being given the correct "Path Prefix" or by manually selecting the special folders.
I can't fathom why apple has chosen not to support or can't detect namespace correctly and require manual configuration but if they haven't done it by now they must have some reason for it and aren't going to fix it any time soon.
Are there any creative solutions to fixing the i-clients and preventing them from needing manual configuration?
-K
Apple has a long history with bugs on imap, they are focused in using their own services, so they might never fix outside stuff, but however why not ask Apple for help, you paid a lot to them
Best Regards MfG Robert Schetterer
-- [*] sys4 AG
http://sys4.de, +49 (89) 30 90 46 64 Franziskanerstraße 15, 81669 München
Sitz der Gesellschaft: München, Amtsgericht München: HRB 199263 Vorstand: Patrick Ben Koetter, Axel von der Ohe, Marc Schiffbauer Aufsichtsratsvorsitzender: Joerg Heidrich
On 2013-04-24 10:54, Robert Schetterer wrote:
Apple has a long history with bugs on imap, they are focused in using their own services, so they might never fix outside stuff, but however why not ask Apple for help, you paid a lot to them
I've never paid them a dime to them in my life but I probably have many thousands of their devices talking to my imap servers and this issue leads to a support burden on our end. I recognize that their client is apparently broken on this point and that asking apple to fix it is pointless. Perhaps ironically, the local apple store knows about this problem but views it as "our" problem and not theirs - they only know that they get a people in the store on a regular basis asking for help because they can't delete their mail on their sonic.net mail accounts.
I was curious if anyone else had come up with a work around for this before or if they had tried and failed. Perhaps a hidden namespace with folders linked to the real special folders or might that have unintended consequences?
-K
On 4/24/2013 12:05 PM, Kelsey Cummings wrote:
before or if they had tried and failed. Perhaps a hidden namespace with folders linked to the real special folders or might that have unintended consequences?
This seems to kinda work with the only oddity being that the ios client, if not manually configured with the correct prefix, ends up creating new folders in the hidden one and initially displaying them at the same level as the inbox. Once the app is restarted it sees them in the "correct" namespace as a folder under the inbox. However, looks like some other clients might get confused, but maybe Windows Live Mail is going to get confused anyway. ;)
namespace { type=private separator = . prefix = INBOX. inbox = yes mailbox Trash { auto = create special_use = \Trash } ... }
namespace FAKE { type=private separator = . hidden = yes list = no mailbox Trash { special_use = \Trash } ... }
-- Kelsey Cummings - kgc@corp.sonic.net sonic.net, inc. System Architect 2260 Apollo Way 707.522.1000 Santa Rosa, CA 95407
participants (2)
-
Kelsey Cummings
-
Robert Schetterer