Version: 1.6.82 (using KDE 3.2.1, SuSE) Compiler: gcc version 3.3.3 (SuSE Linux) OS: Linux (i686) release 2.6.5-7.53-smp When the address book contains e-mail addresses that include a realname, KMail will in spite of this add the realname again, resulting in an invalid TO: header. Example: BEGIN:VCARD CLASS:PUBLIC EMAIL;TYPE=PREF:Alfred E. Neumann <alfred.neumann@nowhere.com> FN:Alfred Neumann N:Neumann;Alfred;E;; UID:TRPahi25il VERSION:3.0 END:VCARD Pick this address from the address book, and you'll get Alfred Neumann <Alfred E. Neumann <alfred.neumann@nowhere.com>> which of course the MTA will reject. I am not sure how I got so many addresses like this in my std.vcf in the first place, but it seems to be full of them. But anyway KMail should not add the realname again if there already is one.
Tobias (the KAdressbook maintainer) tells me that that vcard is then invalid. EMAIL is supposed to only contain an email address, never a name part. KMail behaves correctly, as far as I can see.
That vcard may not be what KMail expects, but since older versions of KMail or the address book happily accepted such e-mail entries, LOTS and LOTS of users will have this problem. I could help myself - one single 'sed' over std.vcf, and I got rid of that problem. But this is clearly not an option for the great majority of KMail users. Many users who have been using KDE for a long time will without doubt have lots of such entries in their address books - even more so since older versions of KMail never added a realname, and it's hard to see in the "sent" mail folder who on earth that k7btadsf@yahoo.com was that I sent that mail to. Adding the realname to the e-mail address had been the only way to make that usable at all, and now you come and tell me that nobody cares about long-standing users who inherited their address books over generations of KDE? If you feel it too much trouble to do this check for each mail address that is inserted somewhere, at the very least provide an import filter for such old-style .vcf files that throws out that part that KMail can't handle! Folks, do you have any idea how many arguments we have with hardcore console mailer users who advocate their ancient "mutt" or "pine" about each and every glitch of KMail? Don't give them any more ammo - those are the people who install and configure user accounts for newbies, and they'll get "pine" and "mutt", too for the smallest of excuses!
I for one have not a single invalid EMAIL entry (even though I always run kdepim versions and KDE versions in sync) Perhaps we should clarify how you got these invalid entries before you claim that it will affect the majority?
I know some of these kind of entries I got simply adding the realname manually - to make illegible mail adresses like 47110815@yahoo.com or xy@suse.de human readable. I certainly didn't simply use a text editor to edit std.vcf manually - I did it all with the proper KDE dialogs. Some of those entries I got with "add to adress book" - maybe with very old versions of KMail. Maybe newer ones are intelligent enough to remove excess parts, but older ones for sure didn't. And I bet that many address book entries are created that way: I get a mail from somebody and click on "add to address book" in the context menu that appears upon right-click on a mail address.
I'm not sure about Tobias assumption that this would be an illegal vCard. The RFC isn't very specific about the content of this value and as it can be used to copy it into the To field of a mail client I would consider this as valid email address.
Thank you for taking the time to file a bug report. KMail2 was released in 2011, and the entire code base went through significant changes. We are currently in the process of porting to Qt5 and KF5. It is unlikely that these bugs are still valid in KMail2. We welcome you to try out KMail 2 with the KDE 4.14 release and give your feedback.