No code commits on Kube in 6 months. Is anyone still working on it? https://invent.kde.org/pim/kube/-/branches
- Queries
- All Stories
- Search
- Advanced Search
Advanced Search
Feb 8 2024
Sep 12 2020
Aug 27 2020
It's possible that this is because insecure apps have not been enabled or so.
Aug 9 2020
This looks like something on your system is broken and you can't launch the shell in the flatpak at all. You should definitely be running the command as user (it's not installed as root),
but it looks like that LD_PRELOAD error is fatal, and a quick google search pointed me to some ubuntu related issues (I didn't find anything directly related to flatpak though).
Thank you.
Does this help at all?
Aug 8 2020
With the latest flatpak you can run a connection test like so
Aug 7 2020
Yes, I'm running the flatpak.
Aug 6 2020
This looks like the resource has no server url whatsoever configured... Are you running the flatpak?
Jul 20 2020
Jul 19 2020
Jun 18 2020
The latter comment regarding use of git:// goes for a bunch of repos referred to in the manifest.
Jun 11 2020
Further, in replying to invitations also appears to be left to the server (tested with both web client and CalDAV client) and therefore Kube should probably not submit a reply via IMAP too
I have tested Apple Calendar again with both Fastmail and Kolab Now accounts
Apple's calendaring apps leave this functionality to the CalDAV server. This means that an invitation gets sent out by the server (tested with Fastmail and Kolab) but I don't believe it's placed in the sent items folder as the mail app and Calendar app are separate from each other.
Jun 10 2020
I don't know what's going on, but we seem to have moved on to a new error.
FWIW, it's now possible to specify which authentication method to use, so you could experiment with alternatives.
I'll close this as I currently don't have any intention of separating this in the UI.
I'm not sure what the rfc's have to say about it, but I agree it would be better if it was one or the other.
I agree that this would be a better approach, thanks for the suggestion.
Jun 6 2020
I just took a look at mailo online:
Jun 5 2020
Ah, yes, a restart is unfortunately required atm.
Ah it doesn't apply the authentification mode without a restart.
If you can send mail, that's just smpt working. The IMAP part is separate.
Well that's interesting, I can send mails though ;) I just created one and sent it to myself and got it (in a different client).
So I will write this while I experiment due to the fact that I do make progress and identify possible ux problems.
I suggest you try the flatpak at https://kube-project.com/getit.html
Jun 4 2020
\n in your domain is clearly not normal or correct. One slash only is also incorrect, it's always smtps:// or imaps://.
\n in your domain is clearly not normal or correct. One slash only is also incorrect, it's always smtps:// or imaps://.
Jun 3 2020
Warning: {4f753f1e-1199-4b51-bea8-fd909b626645}.synchronizer : Synchronization failed: Error: 5 Msg: "Invalid server url: smtps://\nmail.mailo.com:465" Warning: {4f753f1e-1199-4b51-bea8-fd909b626645}.synchronizer : Error during sync: Error: 5 Msg: "Invalid server url: smtps://\nmail.mailo.com:465" Log: {4f753f1e-1199-4b51-bea8-fd909b626645}.synchronizer : All requests processed. Log: {c5e63138-a611-43d3-bd52-53d7232c6f2e}.org.kde.pim.kimap2 : "Socket disconnected. false" Warning: {c5e63138-a611-43d3-bd52-53d7232c6f2e}.org.kde.pim.kimap2 : "Socket error: QAbstractSocket::HostNotFoundError" Warning: {c5e63138-a611-43d3-bd52-53d7232c6f2e}.org.kde.pim.kimap2 : "Connection to server lost QAbstractSocket::HostNotFoundError" Warning: {c5e63138-a611-43d3-bd52-53d7232c6f2e}.imapserverproxy : Job failed: "Host not found." KIMAP2::LoginJob 105 Log: kube.sinkfabric : Received notification: Notification(Type: "status" , Id: "sync" , Code: 3 , Message: "Synchronization has started." , Entities: () ) Warning: {c5e63138-a611-43d3-bd52-53d7232c6f2e}.synchronizer.changereplay : Change replay failed: Error: 2 Msg: "Host not found." Last replayed revision: 1 Warning: {c5e63138-a611-43d3-bd52-53d7232c6f2e}.synchronizer : Changereplay failed: Error: 2 Msg: "Host not found." Warning: {c5e63138-a611-43d3-bd52-53d7232c6f2e}.synchronizer : Error during sync: Error: 2 Msg: "Host not found."
Jun 2 2020
mailo also doesn't advertise which authentication method it does support in it's capabilities. If you know, I'm sure we can fix this with a bit of work.
In the case of mailo imaps://mail.mailo.com:993 should be correct. I don't have an account there but I'm getting "Warning: {09573c96-3a6f-40f6-87fe-c4e89c339edb}.imapserverproxy : Job failed: "Login failed, server replied: A000002 NO Authenticate mechanism PLAIN unknown ", which seems to indicate that the server does not support imap PLAIN authentication, which is currently the only one that is supported (due to lack of a configuration option for it).
Still not working.
Jun 1 2020
Of course, and as you have a workable solution it's not of critical importance now.
We are not yet using SPECIAL-USE yet, simply because we didn't get to implementing it yet.
May 28 2020
Why by its name @cmollekopf?
May 24 2020
May 23 2020
Apr 5 2020
Thanks for the update. I think I'll wait until Kube has the interface,
until then Thunderbird is working OK for me.
Apr 4 2020
The configuration UI is rather limited at the moment I'm afraid. I'll reproduce some information here from a recent mail exchange that should give you a starting point at least:
Available now.
It's possible that this is because insecure apps have not been enabled or so.
Apr 2 2020
Feb 9 2020
Dec 1 2019
Nov 30 2019
The sent mail folder is nothing special, it's just a folder that is synchronized over IMAP as all others. Do you see one in webmail, and does it have a name other than "sent"?
The only "magic" that happens is that a sent mail folder is recognized as such via it's name (which will currently fall apart with other languages), and that information is then used to store sent messages in that folder. You should be able to see it in any case though.
What we meanwhile have that we use a weekday+time format for the past week, and a time only for the current day. While not exactly what you requested I think it addresses the issue well enough (it makes it easy to spot what's recent and what isn't), so I'll close this issue for now.
Nov 29 2019
Thanks for the report, I can reproduce the issue.
Additional information: I just sent an e-mail from Kube with an attachment. The attachment is also not shown in the Kube Sent folder, but it is actually attached when I receive it in KMail (at a different e-mail address), and in KMail it is also attached to the originally sent message in the Sent folder.
Yes, I totally agree with 3) (easy setup). I set up an account yesterday. I'm quite an experienced user, but somehow managed to ignore the grey syntax provided by Kube for IMAP and SMTP. I fiddled around for 20 minutes before I noticed this information. Then it worked well.
Nov 10 2019
Oct 1 2019
Aug 29 2019
[spam comment removed by sysadmin]
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?
Aug 20 2019
Thanks for the report, I'll try to reproduce the issue.
Aug 19 2019
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 13 2019
Out of interest, would this require the same password to be used for the CardDAV and CalDAV servers as well?
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.
IMAP is enabled on my account, I use it with a few clients succesfully, one of which is Kmail. Ofcourse, server and port are only some of the parameters for IMAP (and SMTP) auth, the other I am able to set in Kmail for instance being auth-type (plain, ntlm, cram-md5, and some others). Could it be this?
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 23 2019
Thanks! For IMAP, I tried 'imap(s)://imappro.zoho.eu:993' but that still gives me the same error. Do you know what I should do to configure IMAP correctly?
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 17 2019
Jul 15 2019
Here I have the full log obtained after the above steps, running an updated kube (as of 3 minutes ago), and quitting right after. I censored the email adres just in case spammers have found the KDE phabricator instance, but there was no mistake in it ;)
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.
Flatpak, right from the kube website.
Jul 13 2019
There is no UI for this usecase.