[Bug 257969] imap akonadi resource stuck on "connection established"

[Cristian Tibirna]

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





--- Comment #11 from Cristian Tibirna <tibirna kde org>  2011-09-17 20:23:08 ---
OK. Thanks for your attention. Finally this discussion (and today's actions on
this bug report) are concluding for me a rather bitter and long wait. I now
know exactly what happens.

The problem with that generic UW imapd (university of washington imap server,
was once one of the most used in the category) is that by default it is
programmed to give access to the whole user directory on a LISTDIR request.
Changing this rather lame default would require modifying and recompiling the
server code and this is not an option.

I remembered finally (damn this makes me feel old...) that I always had
problems with kmail and that each time that I reconfigured my user account, I
needed to pay very careful and special attention to kmail wanting to suck all
my (50G) user data from the imap server through access to my (workplace) home
directory. The trick was to correctly set the "Namespaces" in the old kmail
versions to point to the right directory in my home account on the server.

Unfortunately the new kmail2 (well, akonadi...) doesn't offer this option
anymore. Or at least I don't find it.

There are for now two eventual workarounds: 
- serverside subscription before hitting for the first time the OK button on
that (faulty) server configuration (this is possible but tedious and the final
result is subpar)
- local subscription, but this requires transferring all home directory data
first and this is too heavy on the akonadi server (chicken and egg...).

Then OK, this all makes my problem unrelated to this bug report.

I will score through the bug reports see if I find something related.

Thanks for listening.

-- 
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.