Most sane place to fix this is in mimetreeparser / libkleo:
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
Advanced Search
Wed, Apr 1
Mon, Mar 30
I'm not sure if there is any way for the add-in to know which way it was installed.
Fri, Mar 27
yes, we should only ask for an update of the manifest if its content was changed. the message should indicate that.
Thu, Mar 26
Wed, Mar 25
Mon, Mar 23
Extended to show distinct messages for the cases:
Thu, Mar 19
Fixed in work/tfry/settings_dialog_tuning
Wed, Mar 18
Mon, Mar 16
Windows button order seems to be described, there: https://web.archive.org/web/20161013015954/https://msdn.microsoft.com/en-us/library/dn742499.aspx . I could not find a more up-to-date official reference. Likely, this still applies, though. This specifies (left to right): OK/[Do it]/Yes, [Don't do it]/No, Cancel, Apply (if present), Help (if present)
branch work/tfry/seclevel_ui
Mar 6 2026
Should be tested (but unclear, how): ability to read / send (with both organization/personal accounts)
Mar 5 2026
This is now a wontfix, because:
- mapping is no longer based on email
- if no matching secret key is available for that account, the native client shows a message ([T7684])
Suggested patch in work/tfry/connect_check_email :
Mar 4 2026
Mar 2 2026
Implemented in mimetreeparser master: https://invent.kde.org/pim/mimetreeparser/-/merge_requests/92
Feb 26 2026
Feb 23 2026
Feb 6 2026
Feb 5 2026
You are totally correct, confirmed with VSD 3.3.5.
I was curious: Similar to the kiosk/immutable feature of kconfig, gpgolconfig allows to flag values as immutable by appending a '!' to the value set in the registry. If autoencryptUntrusted is set to 0! via the registry then the checkbox should be disabled.