Bug 283638 - Sync with IMAP results in "Select failed, server replied: A000023 NO Unkown namespace."
Summary: Sync with IMAP results in "Select failed, server replied: A000023 NO Unkown n...
Status: RESOLVED FIXED
Alias: None
Product: Akonadi
Classification: Frameworks and Libraries
Component: IMAP resource (show other bugs)
Version: 4.7
Platform: Ubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: Christian Mollekopf
URL:
Keywords:
: 283820 (view as bug list)
Depends on:
Blocks:
 
Reported: 2011-10-09 09:09 UTC by Michael Holtermann
Modified: 2013-11-19 16:31 UTC (History)
6 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments
Output from Akonadi Debug Console (15.04 KB, application/octet-stream)
2011-10-09 09:09 UTC, Michael Holtermann
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Michael Holtermann 2011-10-09 09:09:48 UTC
Created attachment 64354 [details]
Output from Akonadi Debug Console

Version:           4.7 (using KDE 4.7.1) 
OS:                Linux

After upgrading from Kubuntu 11.04 to 11.10 (latest beta) I've created a new account and set up KMail2 using my mail account. The account is hosted by DomainFactory (Germany) using my own domain.

Unfortunately, KMail or Akonadi refuses to load messages. I see the folders, but on synchronizing I get an error message saying "Select failed, server replied: A000023 NO Unkown namespace.", the number is counting up.

Wasn't there a "namespace" setting in KMail < 4.7? Where is it gone?

Currently, this issue renders KMail completely unusable.

I'll attach the output of Akonadi Debug Console, please let me know if any additional information is needed.

Kind regards,
Michael

Reproducible: Always

Steps to Reproduce:
1. Create new IMAP account with kmail
2. Try to synchronize

Actual Results:  
Error message in notifier:
"Select failed, server replied: A000023 NO Unkown namespace."

Expected Results:  
Synchronizing of messages

Version information from apt-cache:
kmail: 4:4.7.2+git111007-0ubuntu1
akonadi-server: 1.6.2-0ubuntu1
Comment 1 Michael Holtermann 2011-10-11 18:03:37 UTC
Today I've made a second try (create new user, log in, create Akonadi-IMAP-resource)- same result.
Comment 2 Christophe Marin 2011-10-13 10:28:13 UTC
*** Bug 283820 has been marked as a duplicate of this bug. ***
Comment 3 Michael Holtermann 2011-11-12 09:56:48 UTC
The akonadiconsole shows ".INBOX" as remote identifier of the INBOX folder. Is this the correct value?

All other folders (Sent, Trash, some custom folders) are created below the INBOX folder.

I've played with the local folder subscription settings, but this does not help. The server side subscription window is empty.
Comment 4 Michael Holtermann 2011-11-20 12:04:28 UTC
Some new information:

DomainFactory provides two host names for IMAP services:

- imap.mydomain.invalid (will result in a certificate error if SSL is enabled, DomainFactory does not provide custom SSL certificates, at least not with my service plan)

- sslmailpool.ispgateway.de

As far as I can see the first host provides both plain and encrypted services at port 25, the second host is SSL only at 993.

Now the fact: Using the second host, I run into the "Unknown namespace". The first one works as expected.

With wireshark I see some SSL traffic on both hosts. If it could help to solve this issue and if it is possible to decrypt the traffic easily, I'll give it a try, but would need some advice how to do so.

Additionally, I'll open an issue at DomainFactory, but I doubt that this is a server side issue, since it worked with KDE 4.6 (pre-Akonadi era).

Regards, Michael
Comment 5 Michael Holtermann 2012-02-12 12:15:48 UTC
I've switched to GoogleMail which does not produce that error, so I'm no longer interested in a final solution.

But I guess other users might run into this issue, to (see #2), so at least a hint about the cause of that error message would be nice.

Thanks in advance!
Comment 6 Michael Bauer 2012-02-13 22:35:21 UTC
Exactly same trouble here.
Comment 7 reportbug 2013-04-15 20:27:51 UTC
Exactly same trouble here (KDE 4.10.2 + Akonadi 1.9.1).
Comment 8 reportbug 2013-04-15 21:26:02 UTC
I changed the IMAP host name to an incorrect value -> tried to connect -> did not work (of course) -> changed it back to the correct value -> no namespace error messages anymore.

The error messages occurred after an upgrade from a NON-Akonadi-KMail setup to a Akonadi setup. It seems that the IMAP namespace configuration (values) of the two different setups are not compatible and one has to trigger Akonadi after the upgrade to fetch the namespace again or so.

Open question (to me): what happens when the mail provider changes the namespace for some reasons. Does Akonadi updates its configuration automatically?

However, I'm happy that it works now.
Comment 9 Kevin Ottens 2013-11-16 07:31:47 UTC
The IMAP resource has a new maintainer, reassigning to him.
Comment 10 Christian Mollekopf 2013-11-19 16:31:51 UTC
Namespace changes are currently not handled, but the issue is tracked here: https://bugs.kde.org/show_bug.cgi?id=327822

If there are other existing problems please reopen or create a dedicated report for the issue.