Version: (using KDE KDE 3.3.91) OS: Linux When one clicks on the "..." next to the To: textfield one can chose addresses, including the recently used ones. You get all the categories you have in KAddressbook plus the recently used one. This leads to the assumption that these addresses are part of the kaddressbook and the category can be chosen from the drop-down menu in kaddressbook as well. Unfortunately this is not the case. To access the recently used addresses the user has to right-click the textfield, which is really too hidden! A user would either expect to be able to access them through the kmail composer settings, or the addressbook. Expected behaviour would be: Kaddressbook gets a default-resource called "recently used addresses". This resource gives easy access to the addresses (in order to move them to other resources), as well as to the settings such as, how many should be kept or a "delete all" functionality and so on.
How can you add a resource to kaddressbook that includes all the "recently used addresses" as they are shown in kmail's composer?
Well, kaddressbook contains a directory "recently used adresses" for me. I can access these adresses from the composer completer too.
From within kaddressbook or from within kmail's composer? If I open kaddressbook on its own the resources are shown at the bottom-left and there is no "recently used" resource. If I click on the "+" to add one there no such resource either.
Ah, now I got what I are thinking of.
*you* are thinking of.
having a recently used addresses resource in akonadi/kaddressbook would be very useful
Would actually be useful – still!
Thank you for your feature request. Kmail1 is currently unmaintained so we are closing all wishes. Please feel free to reopen a feature request for Kmail2 if it has not already been implemented. Thank you for your understanding.
Instead of creating a new feature request, please confirm here if the wishlist is still valid for kmail2.
still valid
Thank you for the bug report. As this report hasn't seen any changes in 5 years or more, we ask if you can please confirm that the issue still persists. If this bug is no longer persisting or relevant please change the status to resolved.