- User Since
- Apr 12 2015, 7:57 AM (231 w, 3 d)
Tue, Sep 17
Sun, Sep 15
Fri, Sep 13
Tue, Sep 10
Sun, Sep 1
Sat, Aug 31
Thu, Aug 29
The above commit wasn't it (reverted it locally), but still can't reproduce atm.
Can't reproduce, might have been fixed by the recent 1b416946f7c06ff075c7a7d2abacf05705500c3f
The situation might have improved as the treeview has been reimplemented with qtquickcontrols2, but I haven tested it.
The basic strategy has been implemented in da4b74e593f1b1262e83824cc499bd855f1b4e3e
I can't reproduce this in Mac OS High Sierra.
Which os version are you running and did you try starting kube from a console so we get it's log output?
Tue, Aug 20
Thanks for the report, I'll try to reproduce the issue.
Aug 17 2019
The kube codebase currently indeed makes that assumption and sets the same password on all sink resources of the same account during regular usage.
This should be fixed, thanks for the heads up.
Aug 15 2019
Aug 14 2019
Aug 13 2019
Aug 12 2019
Jul 28 2019
Jul 24 2019
It shouldn't. Kube is currently always using PLAIN authentication, but from the capabilities that seems to be correct for zoho (capabilities contains AUTH=PLAIN). You could try to gather another log with the fixed imap server url so we can see what's going on.
Unfortunately I cannot help you much more. I've tried signing up for a free testaccount and setting it up as recommended in their documentation https://www.zoho.com/mail/help/imap-access.html, but I always end up with an "Invalid credentials" error (visible only on the console).
You may have to generate an app specific password and you have to enable imap. Anyways, the "Invalid Credentials" error means that kube does successfully connect to the IMAP server, it just can't login with the given credentials. Maybe that was also just because I used a free account, who knows..
Jul 22 2019
Jul 21 2019
Your server configuration should be something along the lines of: "imaps://imappro.zoho.eu:993" and "smtps://smtp.zoho.eu:465".
Kube and Kontact are entirely separate projects and supporting other akonadi backends means writing a new backend for Sink. I have no plans to work on an EWS backend, so unless somebody steps up that won't be happening anytime soon.
I'll close this request as a wontfix because we won't be doing anything about it at the moment. Of course, if somebody else is willing to do the work then have at it =)
Jul 18 2019
Jul 14 2019
I just tried setting up a fresh account without caldav/carddav and it works for me insofar that email starts syncing. There will indeed be configuration errors with an empty url because kube will blindly try to setup caldav/carddav from the urls given.
Jul 13 2019
There is no UI for this usecase.
The user visible errors are indeed rather limited/useless. You can get more detailed output by starting kube from the commandline. With flatpak this would be: