Hey all!
I have no idea which category this should be in, but I use the libsecret backend of keepassxc. Unfortunately, whenever it locks mailspring fails to reconnect with my email unless I restart the mailspring process after unlocking the database.
OS: Manjaro Linux
Mailspring: v1.9.1
This should behave much better on current versions. Back in 1.9.x Mailspring looked each password up in the Secret Service (your KeePassXC database) every time it needed one, so a locked database meant no credentials until you restarted. Since 1.12 the passwords live in an encrypted blob inside Mailspring’s own config.json, and the Secret Service is only consulted for the encryption key, which Chromium fetches when the app starts. The requirement now is just that KeePassXC is unlocked when you launch Mailspring; locking it afterwards shouldn’t knock your accounts offline.
The flip side is that if the database is locked at launch, Mailspring can’t decrypt anything and will stop with a “could not read your saved passwords” dialog rather than silently losing them - unlock KeePassXC and start it again. More on how the keyring is used here: "Password Management Error" on Linux — Mailspring Documentation