| Summary | duplicate address prompt |
| Queue | IMP |
| Queue Version | HEAD |
| Type | Enhancement |
| State | Resolved |
| Priority | 1. Low |
| Owners | |
| Requester | vilius (at) lnk (dot) lt |
| Created | 08/30/2004 (7737 days ago) |
| Due | |
| Updated | 06/08/2005 (7455 days ago) |
| Assigned | 09/27/2004 (7709 days ago) |
| Resolved | 06/08/2005 (7455 days ago) |
| Milestone | |
| Patch | No |
State ⇒ Resolved
bug 1054.That means that either someone implemented this check already in the
meantime, or there is simply a bug in the code.
lines 1008-1058 of compose.php?
State ⇒ Accepted
State ⇒ Assigned
cleanly be done at this stage, ie. we would need a comletely new
template for the compose view just for that purpose.
Checking only for the email address is a good idea though.
Priority ⇒ 1. Low
Type ⇒ Enhancement
Summary ⇒ dublicate address prompt
Queue ⇒ IMP
State ⇒ New
turned on, and recipient's name (not email address) is different from
the stored, or there is no name at all, IMP creates new contact in
address book. I thought, maybe it is wiser to do only email address
check, and if contact with such email address is found, prompt user
what to do:
1) Overwrite stored name with current name.
2) Leave as is.
3) Create new contact.