Bug 341513 - wrong contact photo shown
Summary: wrong contact photo shown
Status: RESOLVED UNMAINTAINED
Alias: None
Product: kontact
Classification: Applications
Component: mail (show other bugs)
Version: unspecified
Platform: Arch Linux Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-12-03 00:15 UTC by Tim Ruffing
Modified: 2018-02-01 09:48 UTC (History)
3 users (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 Tim Ruffing 2014-12-03 00:15:15 UTC
I regularly get emails from "post+EXAMPLE@EXAMPLE.de", where I substituted "EXAMPLE" for privacy reasons.

I don't have this email address in my address book. Still, a contact photo is displayed when I read mails from this address. The photo belongs to an unrelated contact with "post@ANOTHEREXAMPLE.de". If I remove the email address from the contact, kontact displays the photo of yet another contact with "post@YETANOTHEREXAMPLE.de".

I guess the plus sign in the email address is the problem.

Reproducible: Always
Comment 1 Laurent Montel 2014-12-03 09:23:11 UTC
Indeed it's very wierd :)
I add to my todo
Comment 2 Martin Burnicki 2016-01-24 14:58:42 UTC
Sounds like the problem is the same as in
https://bugs.kde.org/show_bug.cgi?id=349727
Comment 3 Denis Kurz 2017-06-23 21:01:27 UTC
This bug has never been confirmed for a KDE PIM version that is based on KDE Frameworks, except possibly a Technology Preview version 5.0.x. Those Framework-based versions differ significantly from the old 4.x series. Therefore, I plan to close it in around two or three months. In the meantime, it is set to WAITINGFORINFO to give reporters the opportunity to check if it is still valid. As soon as someone confirms it for a recent version (at least 5.1, ideally even more recent), I'll gladly reopen it.

Please understand that we lack the manpower to triage bugs reported for versions almost two years beyond their end of life.
Comment 4 Denis Kurz 2018-02-01 09:48:56 UTC
Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.1 aka 15.12; preferably much more recent), please open a new one unless it already exists. Thank you for all your input.