[Bug 282245] New: namespaces configuration still required

[Cristian Tibirna]

https://bugs.kde.org/show_bug.cgi?id=282245

           Summary: namespaces configuration still required
           Product: Akonadi
           Version: 4.7
          Platform: openSUSE RPMs
        OS/Version: Linux
            Status: NEW
          Severity: normal
          Priority: NOR
         Component: IMAP resource
        AssignedTo: ervin at kde.org
        ReportedBy: tibirna at kde.org
                CC: vkrause at kde.org, kdepim-bugs at kde.org


Version:           4.7 (using KDE 4.7.1) 
OS:                Linux

In older kmail it was possible to manually configure the namespaces for which
the imap mailserver was to be inquired. This allowed for a workaround in
configuring old (buggy?) servers like the UW imapd which by default serve up
the whole user home directory upon a LISTDIR request with default
configurations. The workaround was to manually specify a subdirectory in user's
home directory to selectively be checked for (imap) mailboxes.

The latest akonadi version does not provide this configuration option anymore.
This can render kmail unusable in some situations. More precisely, when first
configuring an account for a faulty imap server (as described above), the
potentially huge data transfer required bogs down the akonadi server and makes
it seem to be frozen (this includes other ressources fetching and even the GUI
of akonadi clients like kmail).

Expected solution:
Provide a configuration option for indicating the path in which mailboxes to be
searched on the server (eventually displayed only for known faulty server
versions).




Reproducible: Always

Steps to Reproduce:
Configure an account for an UW imapd server with default configuration (maildir
== ~) and with a few GB of non-mailbox data stored in the user account on the
imap server.

Actual Results:  
Akonadi freezes. Restart is required and it only temporarily stores
functioning. It will freeze again after a few minutes. Faulty account doesn't
appear in kmail. The faulty ressource appears as in "Connection established"
state in "Akonadi Configuration" and it never goes to synching or to "Ready".

Expected Results:  
Akonadi doesn't freeze. Ressource finishes synching and becomes "Ready".

-- 
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.