This forum has been archived. All content is frozen. Please use KDE Discuss instead.

Kontact 4.8.4 and cached IMAP

Tags: None
(comma "," separated)
ogodoy
Registered Member
Posts
7
Karma
0
OS

Kontact 4.8.4 and cached IMAP

Tue Sep 11, 2012 10:19 am
Hi,

I have been using KDE4 for some time (Kde in general before that), but yesterday was the first time I upgraded to a version of Kontact that fully utilise Akonadi. My main concern is that I have my emails on a IMAP server which I usually connect to using cached IMAP.

Earlier this was quite straightforward, I could fully control where the cached emails where lying. Essentially, due to system constraints in my working environment concerning size of disks that are backuped I put the email cache on a disk that is not taken backup of. The main reason for this is that the IMAP server of course is properly taken care of by our sysadmins. However, as Akonadi now is being used everywhere in Kontact, cached emails are filling up my home partition that is under the backup regime. This is not a good situation for me as other parts need to be in the backup regime

I am not quite sure that I fully understand how akonadi works, but if it works as an interface (as indicated by http://blogs.kde.org/node/4503) to other servers and files, then I would not risk anything by putting this database on another part of my disksystem. How can I do that?

All the best
Øystein
ogodoy
Registered Member
Posts
7
Karma
0
OS

Re: Kontact 4.8.4 and cached IMAP

Tue Sep 11, 2012 8:17 pm
Adding to the previous description, I have noticed that when I use the standard configuration with $HOME/.local/share/akonadi everything works fine. However, as noted above this eats my disk that is under backup for no use. When I try to put the akonadi directory on a other disk through a symbolic link from $HOME/.local/share akonadi fails to start and refers to ".. process not registred on D-bus". Anybody that knows a way to circumvent this?

All the best
Øystein
ogodoy
Registered Member
Posts
7
Karma
0
OS

Re: Kontact 4.8.4 and cached IMAP

Tue Sep 11, 2012 8:24 pm
Ahh, now I found this bug report... https://bugs.kde.org/show_bug.cgi?id=299483

It seems that using symbolic links does not work currently. Are there any other solution that could help me? I really cannot afford to keep double copies of email archives within the backup area.

Øystein
User avatar
einar
Administrator
Posts
3402
Karma
7
OS

Re: Kontact 4.8.4 and cached IMAP

Wed Sep 12, 2012 5:48 am
An alternative would be to put Akonadi under the system MySQL instance, or something of the such. Would that fit your use case?


"Violence is the last refuge of the incompetent."
Image
Plasma FAQ maintainer - Plasma programming with Python
ogodoy
Registered Member
Posts
7
Karma
0
OS

Re: Kontact 4.8.4 and cached IMAP

Wed Sep 12, 2012 7:34 am
einar wrote:An alternative would be to put Akonadi under the system MySQL instance, or something of the such. Would that fit your use case?


Yes, I think so (unless our sysadmin reject). Is there a recipe of how to do this?
User avatar
einar
Administrator
Posts
3402
Karma
7
OS

Re: Kontact 4.8.4 and cached IMAP

Wed Sep 12, 2012 3:36 pm
Most of the configuration is set in

Code: Select all
~/.config/akonadi/akonadiserverrc


And via GUI can be configured by using

Code: Select all
kcmshell4 kcm_akonadi


Then switching to the rightmost tab, unchecking the "use internal mysql server" and filling in the details of the server. Notice that the database needs to be set in advance and appropriate permissions need to be set up for the user to access it. This means creating a dedicated database for the DB user that will be used by Akonadi and ensuring said user has all permissions (GRANT ALL PRIVILEGES) on that specific database.


"Violence is the last refuge of the incompetent."
Image
Plasma FAQ maintainer - Plasma programming with Python
ogodoy
Registered Member
Posts
7
Karma
0
OS

Re: Kontact 4.8.4 and cached IMAP

Thu Sep 13, 2012 8:47 am
Thanks. I will look into this. I did however find a slightly dirty, but simpler solution yesterday. Instead of symbolic links, I used mounts and this seems to solve the problem for me in the short term. In the long term, I hope that the issue identified as a bug above is solved.


Bookmarks



Who is online

Registered users: Baidu [Spider], Bing [Bot], Google [Bot], Yahoo [Bot]