Bug 332493 - KAddressbook doesn not allow to create case sensitive E-Mail addresses
Summary: KAddressbook doesn not allow to create case sensitive E-Mail addresses
Status: RESOLVED UNMAINTAINED
Alias: None
Product: kaddressbook
Classification: Applications
Component: general (show other bugs)
Version: 4.12.3
Platform: Arch Linux Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-03-24 07:48 UTC by Philipp Schmidt
Modified: 2017-01-07 21:48 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Philipp Schmidt 2014-03-24 07:48:01 UTC
KAddressbook should allow the creation of case sensitive e-mail addresses even is most providers do not distinguish between them and even treat them as the same mailbox. On a technical level however the E-Mail should be stored as the user enters it, as we do not know if the e-mail provider indeed follows convention.

Relevant parts of RFC2821 (Section 2.4, page 13):
> The local-part of a mailbox MUST BE treated as case sensitive.

> However, exploiting the case sensitivity of mailbox local-parts impedes interoperability and is discouraged.

Reproducible: Always

Steps to Reproduce:
1. Create a new Contact in the Addressbook
2. Enter e-mail address Foo.Bar@host.com
3. Save contact

Actual Results:  
e-mail address of new contact was saved as foo.bar@host.com

Expected Results:  
e-mail address of new contact should have been saved as Foo.Bar@host.com
Comment 1 Denis Kurz 2016-09-24 20:52:39 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 kaddressbook (version 5.0 or later, as part of KDE Applications 15.08 or later), it gets closed in about three months.
Comment 2 Denis Kurz 2017-01-07 21:48:05 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.