Feb 8 2024
No code commits on Kube in 6 months. Is anyone still working on it? https://invent.kde.org/pim/kube/-/branches
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.