Bug 332952 - when sent mail goes to the inbox, incoming mail is labelled by "To" field, not "From"
Summary: when sent mail goes to the inbox, incoming mail is labelled by "To" field, no...
Status: RESOLVED UNMAINTAINED
Alias: None
Product: kmail2
Classification: Applications
Component: folders (show other bugs)
Version: 4.12.3
Platform: unspecified Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-04-02 09:11 UTC by Diggory Hardy
Modified: 2017-01-07 22:38 UTC (History)
0 users

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 Diggory Hardy 2014-04-02 09:11:16 UTC
Instead of having sent mail placed in a 'sent' folder, I have it put in the inbox (this allows email threads to be shown together like Gmail; eventually I move the whole thread to an archive folder).

Bug: messages listed in the inbox are labelled with subject and recipient (To field), using the "Fancy" theme. It appears this happens in any folder where sent mail is placed, which makes sense for folders only containing sent mail but not for folders which are also inboxes.

What should happen: whether sender or recipient is shown should be configurable, or be the sender when in an inbox. ('Folder properties' → 'view' → 'show column' may be configuration intended for this, but doesn't work.) Or possibly the theme should show both "To" and "From" using abbreviations for common names or something.

Reproducible: Always

Steps to Reproduce:
Edit identity, set sent mail folder to the inbox. Restart if necessary, then view mails in your inbox.
Comment 1 Denis Kurz 2016-09-24 17:53:14 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 2 Denis Kurz 2017-01-07 22:38:33 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.