[#515] duplicate address prompt
Summary duplicate address prompt
Queue IMP
Queue Version HEAD
Type Enhancement
State Resolved
Priority 1. Low
Requester vilius (at) lnk (dot) lt
Created 2004-08-30 (5314 days ago)
Updated 2005-06-08 (5032 days ago)
Assigned 2004-09-27 (5286 days ago)
Resolved 2005-06-08 (5032 days ago)
Patch No

2005-06-08 14:07:36 Chuck Hagenbuch Comment #6
State ⇒ Resolved
Reply to this comment
Hah! I did a bounty without even knowing it. Duplicate of bug 1054.
2005-06-08 08:09:30 Jan Schneider Comment #5 Reply to this comment
Hm, looking at the code it looks to me like we already do this check. 
That means that either someone implemented this check already in the 
meantime, or there is simply a bug in the code.
2005-06-08 04:09:07 pstallworth (at) gmail (dot) com Comment #4 Reply to this comment
Am I being too simplistic or is this issue basically contained within 
lines 1008-1058 of compose.php?
2005-02-20 21:35:33 Jan Schneider Comment #3
State ⇒ Accepted
Reply to this comment
2004-10-07 09:28:42 Jan Schneider Summary ⇒ duplicate address prompt
2004-09-27 09:18:44 Jan Schneider Comment #2
State ⇒ Assigned
Reply to this comment
I am strongly against a confirmation check because this can not 
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.
2004-08-30 12:17:37 vilius (at) lnk (dot) lt Comment #1
Type ⇒ Enhancement
State ⇒ New
Priority ⇒ 1. Low
Summary ⇒ dublicate address prompt
Queue ⇒ IMP
Reply to this comment
If option "Save recipients automatically to default address book" is 
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.

Saved Queries