Bug 309848

Summary:	EMail address reported as invalid - but I use it since years now...
Product:	[Applications] kmail2	Reporter:	grueffelokatze
Component:	config dialog	Assignee:	kdepim bugs <kdepim-bugs>
Status:	RESOLVED UNMAINTAINED
Severity:	normal	CC:	craig.magina, kdenis
Priority:	NOR
Version:	4.8.5
Target Milestone:	---
Platform:	openSUSE
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description grueffelokatze 2012-11-10 10:16:00 UTC

One of my email addresses is of the form
a.b.c.@provider.de
This EMail is reported as invalid when I try to use it while creating a new identity in KMail2.
When creating an identity using an EMail that has a "." before the "@" character, KMail2 reports this EMail address as invalid. When closing the identity creating dialog an error box pops up mentioning "invalid EMail addess".

For sure, the "." before the "@" character is something very special. I already know, that lot of provides are having problems with it (so some people can't send me an email). But I use this address already more than 10 years without some other major problems.
Maybe it's not what the EMail standard expects, but it works for me.

Could we please make KMail more tolerant to such EMail addresses? Maybe showing a warning instead of an error box? So that I can close the identity creation dialog and KMail just uses this address?

It seams only to be an issue with the identity creation dialog, because when adding this EMail using an text editor to files ~/.kde4/share/config/emaildefaults and ~/.kde/share/config/emailidentities, KMail2 works fine, as long as I'm not changing that identity using the identity creation dialog ;)

Reproducible: Always

Steps to Reproduce:
1.Open KMail Setup Dialog.
2.Choose page to manage your identities.
3.Add a new identity with EMail address a.b.c.@gmx.de
Actual Results:
EMail is reported as invalid. When using a.b.c@gmx.de everything works as expected.

Expected Results:
KMail should be more tolerant with EMail addresses containing a "." character before the "@" character. If this is realy a non standard conform EMail address, KMail could show a warning message, but it should not deny using such an EMail address.

Comment 1 Craig Magina 2012-11-12 14:21:20 UTC

I can confirm this is occurring in Kmail2, KDE 4.9.80, although it doesn't seem to be an issue with the '.' but in the way the latest kmail2 is handling the identity e-mail config box. I use kmail2 in KDE 4.9.2 without issue using an e-mail address of a.b@c.com. I also tried to enter an simpler e-mail of the form a@b.com and it still gives the error.

Comment 2 Craig Magina 2012-11-12 14:23:40 UTC

I forgot to mention the packages I am using are the latest (as of 2012.11.22) Kubuntu Project Neon packages installed in Kubuntu 12.10 (Quantal).

Comment 3 Denis Kurz 2016-09-24 18:13:50 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 4 grueffelokatze 2016-10-03 19:00:22 UTC

I just retried the problem on my openSUSe leap system running
KDE v4.14.18
KMail v4.14.10
Are these version new enough?

The issue still happens. KMail does not allow to set an email address of the form a.b.c.@provider.de.
When changing the email address to a.b.c@provider.de, it works, but I don't have this address. For me the '.' is important ;(

Comment 5 Denis Kurz 2016-10-12 09:01:34 UTC

(In reply to bergwerk from comment #4)
> Are these version new enough?

I'm afraid they are not. A lack of manpower constantly forces us to move on and abandon old versions. We can only consider bugs if there's some reason to believe that they are still present in the latest version.

I think I read somewhere that recent openSUSE (was it 42.2?) offers Frameworks-based versions of the KDEPIM suite as well, and that there's no fully automated upgrade path to switch from 4.14 to 5.x on leap. Maybe a manual upgrade is an option for you? I cannot give any support for openSUSE, though

Comment 6 Denis Kurz 2017-01-08 00:01:19 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.