Bug 330581

Summary:	Composer auto-completed address entry with recipient name not valid for mail sending
Product:	[Applications] kmail2	Reporter:	Lassi Väätämöinen <lassi.vaatamoinen>
Component:	composer	Assignee:	kdepim bugs <kdepim-bugs>
Status:	RESOLVED UNMAINTAINED
Severity:	major	CC:	kde, montel
Priority:	NOR
Version:	4.12
Target Milestone:	---
Platform:	Kubuntu
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Lassi Väätämöinen 2014-01-30 14:12:19 UTC

During message composing, when adding recipients, composer offers auto-completed recipient entries from "Contacts found in your data" with format

Surname, First <first.surname@mymail.com>

Message sending with such entries fail. 

Reproducible: Always

Steps to Reproduce:
1. Start KMail with previously received messages (and message sender info added to DB)
2. Start composing new message
3. Add a recipient of format: Surname, First <first.surname@mymail.com>
Actual Results:  
Error message pops up:

"Surname@host
The email address you entered is not valid because it does not contain a '.'. You will not create valid messages if you do not change your address."

(Previously the message actually got sent, and user received "invalid recipient" messages from the mailing system.)

Expected Results:  
Message could be sent successfully.

Considering this is a major, as very basic use case is not working, causing very annoying issues in daily use.

Comment 1 Malte Dik 2014-11-07 15:05:39 UTC

I could also observe email addresses of the format <'aaron@zhitomirsky'> (note the quotation marks) showing up. These also lead to frustration.

Is there a workaround to just kill/limit the indexer?

Comment 2 Malte Dik 2014-11-07 15:07:06 UTC

PS: Kubuntu 14.04, KMail version 4.13.3

Comment 3 Laurent Montel 2015-04-10 10:47:04 UTC

Yep now in 4.14.6 we can exclude some email address from completion
and exclude some domain name too.

Comment 4 Denis Kurz 2016-09-24 18:24:16 UTC

This bug has only been reported for versions before 4.14, which have been unsupported for at least two years now. Can anyone tell if this bug still present?

If noone confirms this bug for a Framework-based version of kmail2 (version 5.0 or later, as part of KDE Applications 15.12 or later), it gets closed in about three months.

Comment 5 Denis Kurz 2017-01-07 21:33:16 UTC

Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.0 aka 15.08), please open a new one unless it already exists. Thank you for all your input.