After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 772754 - "Sent by" header is too verbose
"Sent by" header is too verbose
Status: RESOLVED DUPLICATE of bug 714078
Product: geary
Classification: Other
Component: ux
master
Other Linux
: Normal normal
: ---
Assigned To: Geary Maintainers
Geary Maintainers
Depends on:
Blocks:
 
 
Reported: 2016-10-11 13:29 UTC by Adam Dingle
Modified: 2016-10-22 02:26 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Adam Dingle 2016-10-11 13:29:25 UTC 
With recent changes, Geary sometimes displays a "Sent by" header, e.g. when a message is sent by a mailing list.  This looks approximately like this:

  Adam Dingle adam@medovina.org
  Sent by: geary-list  geary-list-bounces@gnome.org
  [Geary] Heads up: widget conversion branch landed
  To: Geary  geary-list@gnome.org

I think this "Sent by" line is so distracting that I'd be happier without it.  There may be some value in presenting this information, but it would be better to be more compact.  Gmail, for example, would display this like this:

  Adam Dingle via gnome.org
  ...
Comment 1 Michael Gratton 2016-10-22 02:26:07 UTC 
I don't disagree, but the current UI is there mainly because of two factors:

There are cases where the domain may be the same: e.g. when sent on behalf of another person: serf@company.com on behalf of boss@company.com, which I feel makes sense to display the full sent address. In these cases, it might be worth using the address label if it exists, rather than the full email address or domain name.

It's also possible to have multiple addresses in From header values, but only a single Sender address, which doesn't work well visually with the current approach of using a GtkFlowBox unless it is on a separate line (a terrible excuse, I know).

In any case, this is a duplicate of Bug 714078, I'm happy to discuss it further over there, but it does need some design work that takes these additional cases into account.

*** This bug has been marked as a duplicate of bug 714078 ***