On the advice of a recent bug (https://bugs.kde.org/show_bug.cgi?id=259949#c154), I added the UseNepomuk=true stanza to my kpimcompletionorder config file. While this works like a charm for bringing up addresses, I think kmail or nepomuk needs to do extra work to sanitise addresses with commas in. Reproducible: Always Steps to Reproduce: 1. Add UseNepomuk=true to ~/.kde4/share/config/kpimcompletionorder 2. Restart kmail 3. Search for a name, nepomuk presents list of addresses, select one with a comma in the displayname 4. Send email, watch mail server reject it because the comma isn't quoted Actual Results: After selecting from 'Contacts Found in Your Data', kmail inserts: Surname, Firstname <firstname.surname@company.com> When pressing send, the mail relay rejects: 2013-08-05 11:29:01 unqualified recipient rejected: <Surname> H=client.company.com (client.localnet) [10.0.0.1] Expected Results: Kmail should wrap quotes around the description part of the address, and only present the <email@address> part to the mail relay.
Hi there, this bug is still present in kmail2 v. 4.12.0. Is it possible to address it? I note that the UseNepomuk=true line has disappeared from my kpimcompletionorder, but I still get address suggestions, implying this is now default behaviour, but strings aren't properly wrapped in quotes still.
Hello Paul, thank you for your report and sorry for the long delay in answering. It is about a version of KMail that is using KMail and is unmaintained. Can you still reproduce this issue with at least Baloo search based KDEPIM 4.14 and latest Akonadi 1.13 or even Akonadi search based (renamed Baloo) KDEPIM/Akonadi 15.08 if you can get it already? Note that there is no Nepomuk anymore in this, so the nepomuk related option will likely have no effect anymore. Thank you and greetings from KDE Randa Meetings, Martin
Hi there, this bug has been identified to be related to nepomuk, the semantic searching system in prior versions of KDE. Please note that nepomuk has been replaced by Baloo. I'm going to close this bug due to the use of the new Baloo system. Please do file a new bug for frameworks-baloo if you happen to continue having issues with search.