After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 252165 - Evolution Mailer contact selection sometimes forces primary address
Evolution Mailer contact selection sometimes forces primary address
Status: RESOLVED NOTABUG
Product: evolution
Classification: Applications
Component: Contacts
2.0.x (obsolete)
Other All
: Normal minor
: ---
Assigned To: evolution-addressbook-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2003-12-14 22:51 UTC by bbigby
Modified: 2013-09-10 14:02 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description bbigby 2003-12-14 22:51:44 UTC
Please fill in this template when reporting a bug, unless you know what you
are doing.
Description of Problem:


Steps to reproduce the problem:
1. Create a contact that has 3 e-mail addresses -- primary, email 2, and
e-mail 3.  Make sure that each e-mail address begins with the same user
name but ends in a different domain.  Use the same display name for all
addresses.
2. Compose a new message.
3. Type the first few letters of the e-mail -- enough so that the e-mail
list appears.
4. Select e-mail 2.
5. Verify that the To: field contains e-mail 2 by right clicking on the
name in the To: field.
6. Right-click on the name in the To: field again and observe what appears
as the address.

Actual Results:
The mailer shows the primary address.

Expected Results:
The mailer should show the E-Mail 2 address.

How often does this happen? 
Everytime.

Additional Information:
The odd thing is that when I choose the E-Mail 3 address and repeatedly
right-click on the name in the To: field, the e-mail address remains as the
E-Mail 3 address, which is correct behavior.
Comment 1 Jeffrey Stedfast 2004-01-04 23:03:25 UTC
sounds like an addressbook issue
Comment 2 André Klapper 2005-01-12 17:25:40 UTC
i can reproduce this running
evolution-2.0.3.0.200501070910-0.snap.ximian.10.1.

i setup a new contact with four email addresses and do as described.
when choosing the last (=fourth) one from the dropdown menu, it always
remains the same and does not matter how often i right-click on it
with the mouse. however, the second and the third email address become
the primary one after looking for two times into the right-click menu
in the to-composer field.
Comment 3 Sushma Rai 2005-08-29 08:09:21 UTC
is this about re-ordering the e-mail addresses in the right click menu?
this menu just lists all the e-mails of the contact and not the selected one.

I think you wanted the re-ordering of email ids, to know which email has
been put in to To: list by, autocompletion. 
Actually, showing the e-mail id along with name in the TO list will
solve this issue.

so marking this as a duplicate of 272391


*** This bug has been marked as a duplicate of 272391 ***
Comment 4 bbigby 2005-08-29 23:54:28 UTC
This bug doesn't appear to be a duplicate.  Let me be clear.  After selecting
"New" to compose a new message, if you select (left-click) the 2nd or 3rd choice
in the list and you right click more than once on the name in the "To:" field to
verify the selection, you will see the choice change back to the Primary.  The
problem is that my choice changed. It should have remained as choice 2,
regardless of the number of times that I right click on the name in the "To:" field.
Comment 5 Sushma Rai 2005-08-30 05:03:17 UTC
when you autocomplete a name with 3 address and select one of them (not primary)
the mail is sent from the selected address only (not from primary id).

and the right-click menu on the autocompleted address doesn't list the
ids with selected id at the top, it lists in the sorted order.
Comment 6 Devashish Sharma 2006-02-01 05:51:09 UTC
Checked with evo 2.5.5.
Doesn,t happen for me. The choice remians the same no matter what you do.
Closing this as notabug, please reopen if it is found to happen again.
Comment 7 André Klapper 2006-02-01 09:09:01 UTC
this is not "NOTABUG", this has been "FIXED". i remember that issue pretty well, and i cannot reproduce it either with 2.5.90. cool.