Open
Bug 165249
Opened 22 years ago
Updated 16 years ago
unify display names based on address book entries
Categories
(SeaMonkey :: MailNews: Address Book & Contacts, enhancement)
Tracking
(Not tracked)
UNCONFIRMED
People
(Reporter: mozilla0K2TY, Unassigned)
References
Details
Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.1) Gecko/20020826
When I enter a name/email in my address book, I typically put a prefix on
certain display names for the company. I have seen many others, especially in
Japan do this. But one problem is that this never agrees with what the
individual uses in their own display name. So whenever I get email from them,
the display name looks wrong. Even though it isnt, it loses the information I
added, which is typically there so that I am careful about what I say to whom,
especially outside my own company. The following is a suggestion for a feature
that would solve this problem for me.
Wherever there is a display name used for an email address, if the email address
is the same as one in my "default" address book, then I would like to always see
that display name rather than whatever may have come with the email itself.
This mechanism needs to look thru the alternate email addresses (and we need N
of them per address book entry, not just one) and map any of them to the desired
display name, rather than just the main one. An option to do this would be very
useful to me.
Updated•20 years ago
|
Product: Browser → Seamonkey
Yes, thanks for noticing this. In particular, I think what is described in bug
#243631 covers this exactly. I have added a few comments to that bug. Im not
sure whether to close this one or not since this is mozilla and that is TB. But
if you are someone who knows that that bug would get rolled into moz, then go
ahead and mark this as a dup of that. (Since that one seems to have more
attention than this one.)
Updated•16 years ago
|
Assignee: racham → mail
QA Contact: nbaca → addressbook
Updated•16 years ago
|
Assignee: mail → nobody
QA Contact: addressbook → addressbook
You need to log in
before you can comment on or make changes to this bug.
Description
•