@knauss Did any development occur? On NLNet I see the project is still at 'Open' status.

Separate keyrings is indeed what I meant, it's what at least some clients do. I don't think gpg supports multiple keyrings though, so you'd need to include a lib.

@knauss Thanks for your elaboration.

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?

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?

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 ;)

Flatpak, right from the kube website.

Encouraged by the Junior label and heliosmartins reference, I'm looking into the Autocrypt spec to see if this is something I could do (I do not know what the Junior label specifically means or how it was determined). Adding a header to all outgoing emails seems fairly straightforward. For retrieving mails, which was classified as 'advanced' in the task, I'm trying to flesh out the work needed a bit more. I have zero Kmail or KDE coding experience (a bit of C++ I do). The Autocrypt spec does seem quite well worked out such that I only have to think about the best integration into Kmail.

Could be, but even if I fill out URLs for card/caldav (which indeed would require different credentials from the imap/smtp account) I still get the same error. In both cases: there is nothing wrong with the server URL(s),. Due to the limited error/debug info I can't narrow it down further for a clearer bug report.