Summary: | pop-up address box in Kmail whensending message is confusing | ||
---|---|---|---|
Product: | [Applications] kmail | Reporter: | Daniel Moyne <dmoyne> |
Component: | general | Assignee: | kdepim bugs <kdepim-bugs> |
Status: | RESOLVED WAITINGFORINFO | ||
Severity: | wishlist | CC: | luigi.toscano, webmaster |
Priority: | NOR | ||
Version: | 1.6.1 | ||
Target Milestone: | --- | ||
Platform: | unspecified | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: |
Description
Daniel Moyne
2004-04-04 15:41:53 UTC
This has changed a lot with the new reciptients editor, it would be great if you test it and report back if you feel it improves things for you. did you try out the new editor? it would be great if you could report back your findings. thanks in advance Matt, is the new editor the one that makes a difference between Person <email> and email (Person) If so, the recent addresses list should *not* contain addresses already in the addressbook: the duplicates are confusing as I keep selecting the "email (Person)" one which doesn't know about encryption preferences et cetera: very, very annoying. that looks like you are describing the autocompletion, which works that way so that you can autocomplete on both email and name I dont have any encryption issues with autocompletion, are you saying that if you choose the wrong one it wont encrypt? On Monday April 11 2005 4:41 pm, Matt Douhan wrote:
> I dont have any encryption issues with autocompletion, are you saying that
> if you choose the wrong one it wont encrypt?
The problem is slightly more complex: when I select the "email (Name)" variant
instead of "Name <email>", it will not automatically pick up encryption
preferences for that recipient from the addressbook, so I have to choose the
key again, etc. etc. If I do encryption works fine.
So I suppose the problem only exists for contacts in the addressbook whose
e-mail address starts with their first name, but I bet it's still rather
confusing for anyone who hasn't read the above clarification.
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. |