Bug 327384 - Contact editing dialogs case fold e-mail adresses toLower
Summary: Contact editing dialogs case fold e-mail adresses toLower
Status: RESOLVED UNMAINTAINED
Alias: None
Product: kdepimlibs
Classification: Applications
Component: akonadi (show other bugs)
Version: 4.11.2
Platform: unspecified Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-11-09 23:19 UTC by Johannes Mueller
Modified: 2017-01-07 21:51 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 Johannes Mueller 2013-11-09 23:19:02 UTC
When editing an e-mail address the e-mail addresses are case folded to lower, i.e. John.Doe@example.com is transformed to john.doe@example.com.

RFC 2821 (http://www.ietf.org/rfc/rfc2821.txt) says about this:
"The local-part of a mailbox MUST BE treated as case sensitive."

This causes problems for example, when KMail is looking up from-addresses from emails in the addressbook in order to display the picture of the sender. If the from-address contains capitals the lookup fails.




Reproducible: Always

Steps to Reproduce:
1. Start KAddressBook
2. Edit or create a contact
3. Add or change an e-mail address so that it contains capital letters
4. Click "O"K
Actual Results:  
The e-mail address is transformed to lower case.

Expected Results:  
Either: The e-mail address should *not* be transformed to lower case but remain as typed in. 
Or: The local-part of the e-mail address remains as typed in, the domain can be case folded to lower.
Comment 1 Denis Kurz 2016-09-24 20:55:34 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 kdepim (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:51:41 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.