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 242499 - multiple TO: address separator should include a semicolon
multiple TO: address separator should include a semicolon
Status: RESOLVED OBSOLETE
Product: evolution
Classification: Applications
Component: Contacts
3.2.x (obsolete)
Other All
: Normal enhancement
: ---
Assigned To: evolution-addressbook-maintainers
Evolution QA team
: 242500 242501 244572 466959 485271 589572 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2003-05-07 14:13 UTC by MIke Scanlon
Modified: 2021-05-19 11:44 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description MIke Scanlon 2003-05-07 14:13:48 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 an email message
2. in the To: field enter several addresses separated by a ;
3. email gets sent, 

Actual Results:
Email gets sent to 1st address only. silently dropping the 2nd, 3rd, 4th
(etc) addresses. 


Expected Results:
I would have expected this email program to act like all other graphical
emailers I've ever used. (I've been sending email since 1988, but thats
besides the point).


How often does this happen? 
Always


Additional Information:
The world has been brainwashed to expect that ; will delimit email
addresses.  I know what the RFC says on the matter, but that too is besides
the point.  It pains me to say that the Microsoft convention of allowing ;
to separate email addresses is way into my DNA by this point and I would
argue that not recongising ; as an address delimiter is a bug.  Also I
would claim it is a bug not to warn the user that you are ignoring the rest
of the addresses on the line.

I'm hoping this is already fixed in a later version.  Thanks for your help.
Comment 1 Jeffrey Stedfast 2003-05-07 16:26:26 UTC
*** bug 242500 has been marked as a duplicate of this bug. ***
Comment 2 Jeffrey Stedfast 2003-05-07 16:26:48 UTC
*** bug 242501 has been marked as a duplicate of this bug. ***
Comment 3 Jeffrey Stedfast 2003-05-07 16:30:17 UTC
semicolon has a speacial meaning in email addresses

that said, this is really an addressbook feature request since the
addressbook can do whatever it wants in those text entry fields, so
long as it gives the mailer syntactically correct email address lists
Comment 4 MIke Scanlon 2003-05-07 20:57:36 UTC
Jeff thanks.  I agree, as long as being an "addressbook" issue
includes the functionality of entering an address(s) that isn't in any
addressbook, ie To: foo@bar.com; bar@foo.com; mike@bluejavelin.net
goes out correctly addressed to these three destinations (currently
the email will only go to foo@bar.com).  Thanks again.
Comment 5 Gerardo Marin 2004-08-19 19:31:31 UTC
*** bug 244572 has been marked as a duplicate of this bug. ***
Comment 6 André Klapper 2005-03-05 13:24:00 UTC
still valid in 2.1.6
Comment 7 Matthew Barnes 2008-03-11 00:22:07 UTC
Bumping version to a stable release.
Comment 8 André Klapper 2009-07-25 14:30:33 UTC
*** Bug 485271 has been marked as a duplicate of this bug. ***
Comment 9 André Klapper 2009-07-25 14:31:19 UTC
*** Bug 466959 has been marked as a duplicate of this bug. ***
Comment 10 Yan Li 2009-07-26 01:32:09 UTC
*** Bug 589572 has been marked as a duplicate of this bug. ***
Comment 11 Yan Li 2009-07-26 01:38:13 UTC
If we didn't want to bend towards an erratic behaviour and using ; as a separator, I'd propose adding a hint when the user uses ; as a separator like this: 

"Dear User, I've noticed that you've used ; as a separator, this is against Internet standard (insert the standard URL here) since someone may use ; as part of his email address. For this time I've changed all your ';' into ',', but please don't use ';' as mail separator any more.

(and a series of radio buttons follow:)

[x] OK, I got it.  
[ ] I love ';' and I wish to use it in the future, don't warn me anymore"

Silently dropping mails to 2nd, 3rd, 4th receivers is evil.
Comment 12 André Klapper 2012-06-20 12:10:37 UTC
Still in 3.2.3
Comment 13 Alexander van Loon 2012-08-08 08:47:40 UTC
I've noticed that bug #558037 and bug #563164 are duplicates of this bug, please mark them as such.

I encountered this bug because my mother copied many addresses from the "To:" field of a forwarded e-mail to a new e-mail she was writing with Evolution. After sending it she looked in the sent mail and noticed that all e-mail addresses except for the first had been dropped. I later figured out that this was caused by the forwarded message having the e-mail addresses separated by the semicolon. To solve it I copied all e-mail addresses to gedit and replaced all semicolons with commas, then sent the e-mail again. But I feel embarrassed, this isn't helping to convince my mother and the rest of my family that Linux is user friendly.

As they said in bug #558037 and the mailing list discussion linked there, it would probably be best if Evolution simply converted semicolons into commas when an e-mail gets sent. If that's not possible just warn the user that semicolons shouldn't be used and offer to convert them to commas immediately.

To be honest I'm surprised that this high impact bug is almost ten years old but still hasn't been solved, even with such simple solutions. Developers, please don't take this as user ungratefulness. I like Evolution and use it daily, but please fix this high priority bug.
Comment 14 Patryk Benderz 2017-11-07 11:02:20 UTC
I have just made test with Evolution 3.26.1-1 in Ubuntu 17.10, by sending an email with two "TO:" recipients delimited by ';' and this email reached both recipients.

Anyone else fancy to confirm it?
Comment 15 André Klapper 2021-05-19 11:44:55 UTC
GNOME is going to shut down bugzilla.gnome.org in favor of gitlab.gnome.org. 
As part of that, we are mass-closing older open tickets in bugzilla.gnome.org (resources are unfortunately quite limited so not every ticket can get handled).

If you can still reproduce the situation described in this ticket in a recent
and supported software version, then please follow
  https://wiki.gnome.org/Community/GettingInTouch/BugReportingGuidelines
and create a new enhancement request ticket at
  https://gitlab.gnome.org/GNOME/evolution/-/issues/

Thank you for your understanding and your help.