61523 - Display user-specified headers

Status: RESOLVED DUPLICATE of bug 353193

(SeaMonkey :: MailNews: Message Display, enhancement)

Description

[Ben Bucksch (:BenB)]

Allow the user to customize the headers, which are shown in the header block
during msg display.
E.g. a user might want to see "Organization" or "X-Mailer" etc. in his standard
msg view, but not want to always see all headers.
Would be nice, if the user had freedom in the design of the header block, i.e.
if he could set (or remove) any header from any of the (currently 2, I think)
header "toolbars".

Comment 1

[scottputterman]

reassigning to mscott.

Comment 2

[Marko Macek]

What I'd like to see:

- default view-headers=none in 3-pane window (subject,sender alredy visible)
- default view-headers=normal in single-message window
- a key to cycle between possible view header modes (none, brief, normal, all)
- display everything inline (right now things often don't fit with many headers)

Comment 3

[Robert Wall]

*** Bug 157518 has been marked as a duplicate of this bug. ***

Comment 4

[Ben Clewett]

Please please fix this!!  The small header does not show the 'To' field, which
is vital with multiple accounts and mailing lists.  The large ugly header shows
so much my email dissapears out of view.

Ben

Comment 5

[Sameer Ajmani]

This feature would enable a very nice application of spam labellers like
spamassasin:  spamassassin adds several headers to each message, including
X-Spam-Status, X-Spam-Flag, and X-Spam-Level, which provide boolean, numeric,
and "number-of-stars" spam levels for the message.  It would be great to be able
to sort my Inbox and Trash folders by these spam levels, so that I can easily
identify spam that wasn't caught and good messages that were caught.

Comment 6

[Ben Bucksch (:BenB)]

This bug is about *display*, not filtering. You can already filter arbitary headers.

Comment 7

[Sameer Ajmani]

Ben: Yes, I already filter my spam based on the spam headers to a folder
(Trash).  But I also want to be able to glance at the trash to see whether any
valid messages were accidentally filtered as spam.  To do this, it would be
helpful to sort the messages by their spam level, since I expect mis-filtered
messages to be just above the threshold.

Comment 8

[Ben Bucksch (:BenB)]

Sort is yet another feature. This bug is merely about adding a line (or several)
like
X-Accept-Language:    de, en, fr
(with the header being configurable) to the message display in the message pane,
in the header area, below CC/BCC etc.. Nothing more.

Comment 9

[Jon Anhold]

Please add this! The ability to specify what headers are displayed in the
preview pane would be fantastic!

Comment 10

[Melynda Coxx]

(In reply to comment #2)
> - display everything inline (right now things often don't fit with many headers)

I came here to see if such an rfe existed, and am happy to find that others agree.  

I think it would be nice to have the option of *scrolling* the header as part of
the message, either with no separate header pane (i.e. inline), or with the
existing header pane that can be made part of the message display pane (i.e.
"the brown part" would stick to the top of the message and would scroll with the
message scroller).

-Just a New User

Comment 11

[Karsten Düsterloh]

> I think it would be nice to have the option of *scrolling* the header
> as part of the message, either with no separate header pane (i.e.
> inline), or with the existing header pane that can be made part of
> the message display pane (i.e. "the brown part" would stick to the
> top of the message and would scroll with the message scroller).

You can turn all headers on and limit the height of the header pane in your
userChrome.css by

/*
 * set maximum height of headerpane
 */
#msgHeaderView .header-part1
{
  overflow:   auto;
  max-height: 20em;
}

Or you can give the Addon http://mnenhy.mozdev.org/ a try.
I'm willing to get the stuff into the Mozilla core, but there's heavy background
work to do (see bug 236954), so don't hold your breath. ;-)

Comment 12

[Karsten Düsterloh]

*** Bug 243420 has been marked as a duplicate of this bug. ***

Comment 13

[Mike Cowperthwaite]

*** Bug 236574 has been marked as a duplicate of this bug. ***

Comment 14

[David :Bienvenu]

doesn't bug 353193 basically address this issue?

Comment 15

[Wayne Mery (:wsmwk)]

(In reply to comment #14)
> doesn't bug 353193 basically address this issue?

let's repeat the above question. does anyone say the answer is "no"?

Comment 16

[Ben Bucksch (:BenB)]

As the bug filer, I say "yes" :)