Bug 361719 - show mail sender MUA wen viewing a message
Summary: show mail sender MUA wen viewing a message
Status: RESOLVED INTENTIONAL
Alias: None
Product: trojita
Classification: Unmaintained
Component: Desktop GUI (show other bugs)
Version: git
Platform: unspecified All
: NOR wishlist
Target Milestone: ---
Assignee: Trojita default assignee
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-04-13 13:35 UTC by Aleksandar Kostadinov
Modified: 2016-04-13 18:21 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 Aleksandar Kostadinov 2016-04-13 13:35:34 UTC
Show sender MUA similar to thunderbird:
https://addons.mozilla.org/en-US/thunderbird/addon/display-mail-user-agent/

Reproducible: Always
Comment 1 Thomas Lübking 2016-04-13 15:32:33 UTC
You can inspect all headers of the mail (ctrl+u) where the "User-Agent" field is listed *iff* the sender MUA added that information.
I frankly fail to see why that out of all header fields should be exposed in the normal header display. You hardly ever care about that information.
Comment 2 Aleksandar Kostadinov 2016-04-13 15:51:17 UTC
Quick measure of sender intelligence :)
Might be a plug-in or optional. For example I learned about `trojita` only because I saw it as the MUA of a person that I respect.
Comment 3 Jan Kundrát 2016-04-13 18:21:59 UTC
Hi Aleksandar, thanks for this feature suggestion. I agree that the User-Agent could provide "interesting information", a piece of data which is important for curious people.

However, Trojita's design is aimed at not getting into the user's way that much, which means that we try to minimize the visual clutter. In addition to that, we also care about speed and minimal data transfers which means that we don't load all headers unless really needed. Right now, the User-Agent is only fetched when the user decides to show the e-mail headers or its source.

If you (or someone else) wants to implement this in a non-intrusive manner, patches are welcome. In the meanwhile, I'll close this bug as out-of-scope.