Bug 465815

+1

+1

Same problem in the latest Version.

This really breaks the usability of Kmail. As KDEWallet does not work with browsers its not a viable option for most users. Apart from that using the security service should be the right approach.
I believe it happens here: https://github.com/KDE/kdepim-runtime/blob/master/resources/imap/settings.cpp
Thank you!

KMail does store secrets into whatever Secret Service is "listening" when setting up an account or logging in but it will not -read- from anything but KDEWallet it seems. It also doesn't wait for the Secret Service to be unlocked.

I think perhaps all of Akonadi software might need updating, too. Tokodon and Neochat work correctly.

I recently got an update to 6.2.1 (24.08.1-1) and things are worse. Instead of it prompting for a password every time to maintain an IMAP connection (which also got to count for SMTP) it now won't even prompt me and doesn't allow synchronizing at all. I'm unable to send or receive any mail at all.

(In reply to Odin Vex from comment #7)
> I recently got an update to 6.2.1 (24.08.1-1) and things are worse. Instead
> of it prompting for a password every time to maintain an IMAP connection
> (which also got to count for SMTP) it now won't even prompt me and doesn't
> allow synchronizing at all. I'm unable to send or receive any mail at all.

The specific error message is:

-------------------
Resource [REDACTED] is broken.
Could not read the password: user rejected wallet access 
-------------------

I never rejected access and KeePassXC always grants without prompting (but does show a notification to me).

> I never rejected access and KeePassXC always grants without prompting (but
> does show a notification to me).

You seems to have kwallet disabled completely, so kmail cannot access it and shows incorrect error. Keepass, playing secret service part in this case, is never reached. 
Starting from 6.1.5 should be possible to enable kwallet and it's secret service support separately (restart akonadi and kmail after doing that). Doing that fixes kmail, remembering networks passwords, etc. I'd still prefer it used secret service though.

(In reply to kapsh from comment #9)
> > I never rejected access and KeePassXC always grants without prompting (but
> > does show a notification to me).
> 
> You seems to have kwallet disabled completely, so kmail cannot access it and
> shows incorrect error. Keepass, playing secret service part in this case, is
> never reached. 
> Starting from 6.1.5 should be possible to enable kwallet and it's secret
> service support separately (restart akonadi and kmail after doing that).
> Doing that fixes kmail, remembering networks passwords, etc. I'd still
> prefer it used secret service though.

I did disable kwallet as I had no need for it to be running. Thank you, I've temporarily re-enabled it and can use IMAP/SMTP/POP3 with no issues. It's a tolerable work-around for now. :)

(In reply to Odin Vex from comment #10)
> (In reply to kapsh from comment #9)
> > > I never rejected access and KeePassXC always grants without prompting (but
> > > does show a notification to me).
> > 
> > You seems to have kwallet disabled completely, so kmail cannot access it and
> > shows incorrect error. Keepass, playing secret service part in this case, is
> > never reached. 
> > Starting from 6.1.5 should be possible to enable kwallet and it's secret
> > service support separately (restart akonadi and kmail after doing that).
> > Doing that fixes kmail, remembering networks passwords, etc. I'd still
> > prefer it used secret service though.
> 
> I did disable kwallet as I had no need for it to be running. Thank you, I've
> temporarily re-enabled it and can use IMAP/SMTP/POP3 with no issues. It's a
> tolerable work-around for now. :)

I've discovered a side-effect. Re-enabling kwallet breaks Vorta (Backup) since it attempts to use KDE Wallet if it's enabled instead of Secret Service. I think the answer is to stop KMail from requiring kwallet. I can maintain patches for my own Vorta repo clone until their developer(s) consider removing special handling for kwallet.

The dependency is even more specific than described here.

On an LTS (read "outdated") setup I figured I'd install the Flatpak-flavored Kontact to give KMail a try without running into old bugs.
The discovery of the package heavily depending on the host setup was already unpleasant, didn't stop though, but I just couldn't set up even a single account. All I had was a "Could not access KWallet. It is necessary to store the password. Please activate it." error message with the wallet open in the background.

Hours of crashing (offense seems to be taken for removing the not even set up account) and pointless searching later I figured that there's no way around this non-working hard dependency, so I'd start looking into why isn't it working properly. Firing up `dbus-monitor` showed communication attempts with "org.kde.kwalletd6", but not with my "org.kde.kwalletd5".

I am hitting this same bug, or a similar issue, with the latest update from kde neon USER repo... Kmail doesnt call for kwallet anymore I get this same error "Resource [REDACTED] is broken.
Could not read the password: user rejected wallet access " so I tried disabling the secret service, but akonadi crashes and I cannot access the modify section of the email account to enter a password it simply crashes. Though first when disabling the secret service and kwallet I was prompted if I wanted to export kmail email passwords from kwallet, but that thing crashed as well.

Same here. After updating to 24.04, Thunderbird stopped working, so I thought giving KMail (4.23.08.5) another try. But the feature to use KeePassXC still does not exist, which is really really sad, as this is the only reason that keeps me from finally migrating away from TB.
 
 In that connection I support Witko's (comment 4) view: as KWallet does not support browsers, one would have to use two PW managers (pretty clumsy) or decide for the TB+KeePassXC bundle. 

Any chances this might get some improvement?