GNOME Bugzilla – Bug 536342
nautilus-sendto for evolution can't send email if comma from lastname, firstname is added
Last modified: 2008-06-05 21:47:21 UTC
Please describe the problem: Sorry guys, this is a nautilus-sendto bug, but I couldn't find that in bugzilla. This bug was originally reported to ubuntu launchpad: https://bugs.launchpad.net/ubuntu/+source/nautilus-sendto/+bug/210917 My Evolution addressbook has its contents sorted in the "Lastname, Firstname"-scheme. When I select contacts from the addressbook as recipients for mail, Evolution simply writes a comma-separated list of "Firstname Lastname". So far everything is fine. However, when I try to send a file via nautilus-sendto, the intended recipient's name (of course even if it is just one person) appears as "Lastname, Firstname" in the "to" field. If not corrected manually, this leads to Evolution considering "Lastname" and "Firstname" separate addresses - which results in a failure to send the mail. Steps to reproduce: 1. right-click a file and hit 'send to' 2. select evolution and start typing the recipients name 3. press enter once a name like 'lastname, firstname <username@domain.com> 'appears Actual results: Evolution will think that there are two recipients. 'lastname' and 'firstname <username@domain.com>'. This will lead to evolution failing to send the email. Expected results: The email address should probably be quoted when it is sent to evolution. eg: evolution 'mailto: "lastname, firstname" <username@domain.com>' works correctly. Does this happen every time? yes Other information: https://bugs.launchpad.net/ubuntu/+source/nautilus-sendto/+bug/210917
-> nautilus-sendto
Already fixed in SVN. 2008-05-29 Bastien Nocera <hadess@hadess.net> * src/plugins/evolution.c (contacts_selected_cb): When a contact is selected, try getting the name from different fields, and don't use E_CONTACT_NAME_OR_ORG, as it could add a comma in the name, causing problems when sending e-mails. Should fix: https://bugzilla.redhat.com/show_bug.cgi?id=448880
*** Bug 536897 has been marked as a duplicate of this bug. ***