Bug 119791

Summary: can't reply to mail which includes semicolon separated To/Cc list
Product: [Unmaintained] kmail Reporter: Martin Koller <martin>
Component: generalAssignee: kdepim bugs <kdepim-bugs>
Status: RESOLVED FIXED    
Severity: normal CC: winter
Priority: NOR    
Version First Reported In: 1.9.1   
Target Milestone: ---   
Platform: unspecified   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Martin Koller 2006-01-09 11:56:26 UTC 
Version:           1.9.1 (using KDE 3.5.0, compiled sources)
Compiler:          gcc version 3.4.3
OS:                Linux (i686) release 2.6.7

I got a mail which includes To and Cc headers of the form:
To: axxx@yyyyy.com; exxx@yyyy.at; axxx@yyyy.at
Cc: gxxx@yyyyy.com; vxxx@yyyy.com; kxxxx@yyyy.at

When I hit reply-all and create an answer mail, kmail gives me the following error dialog when trying to send this mail:

gxxx@yyyyy.com; vxxx@yyyy.com; kxxxx@yyyy.at

The email address you entered is not valid because it contains more than one @. You will not create valid messages if you do not change your address.

Also, in the composer window, in the list of addresses, the names from the Cc/To fields are not splitted into separate input fields but are given exactly as in the To/Cc header fields from the mail.
Comment 1 Martin Koller 2006-10-28 20:45:13 UTC 
I can't find any mail (even oldest mails) which contain the above pattern any more. Either I removed those mails or kmail rewrote the headers (all multi addresses are now separated with a comma; even when the quoted original mail included a semicolon).
Comment 2 mrudolf 2007-02-16 21:46:58 UTC 
Still happens in KDE 3.5.6 when clicking on HTML pages with mailto tags.

For example:
<a href="mailto:one@gmail.com?cc=two@kde.org; three@somewhere.com&subject=Bug">
Comment 3 Martin Koller 2009-07-28 19:53:58 UTC 
Also in KDE 4.3
Comment 4 Allen Winter 2009-07-29 15:30:24 UTC 
A fix for this was committed into trunk a few days ago.  not backported into the 4.3 branch yet, however.  Most likely we'll have this backported for 4.3.1 however.  Check back in 4.3.1 and let me know if it works for you.