254637 - Only 2 Received mail header lines are displayed in full view

Status: RESOLVED FIXED

(SeaMonkey :: MailNews: Message Display, defect)

Description

[Marc Mongenet]

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8a2) Gecko/20040714
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8a2) Gecko/20040714

The full headers view in the mail window shows only 2 Received headers. By
saving the mail to a file, it is possible to view more of them (but not all).

Reproducible: Always
Steps to Reproduce:

Actual Results:  
Received: from freesurfsm4.sunrise.ch (194.230.0.98) by mail-fs.sunrise.ch
(7.0.028)        id 40FD53B10032EE17; Fri, 6 Aug 2004 16:49:06 +0200
Received: from [62.220.137.58] (authenticated as bdrayer) by mail.hebweb.net
(MessageWall 1.0.8) with SMTP; 6 Aug 2004 14:43:42 -0000

Expected Results:  
Received: from freesurfsm4.sunrise.ch (194.230.0.98) by mail-fs.sunrise.ch (7.0.028)
        id 40FD53B10032EE17; Fri, 6 Aug 2004 16:49:06 +0200
Received: from shakotay.alphanet.ch (shakotay.alphanet.ch [80.83.46.147])
        by freesurfsm4.sunrise.ch (8.12.10/8.12.10) with ESMTP id i76Emxkd001640;
        Fri, 6 Aug 2004 16:49:01 +0200
Received: by shakotay.alphanet.ch (Postfix, from userid 1022)
	id 1516F370489; Fri,  6 Aug 2004 16:47:25 +0200 (CEST)
Received: from shakotay.alphanet.ch (localhost [127.0.0.1])
	by shakotay.alphanet.ch (Postfix) with ESMTP
	id A03A83703AE; Fri,  6 Aug 2004 16:46:08 +0200 (CEST)
Delivered-To: [e-mail]
Received: by shakotay.alphanet.ch (Postfix, from userid 1022)
	id 9D335370290; Fri,  6 Aug 2004 16:45:55 +0200 (CEST)
Received: from mail-unsh.hebweb.net (mail-unsh.hebweb.net [62.220.136.33])
	by shakotay.alphanet.ch (Postfix) with SMTP id AB4E43701B4
	for <[e-mail]>; Fri,  6 Aug 2004 16:45:26 +0200 (CEST)
Received: (qmail 24628 invoked from network); 6 Aug 2004 14:43:42 -0000
Received: from unknown (HELO mail.hebweb.net) (62.220.136.33)
  by mail-unsh.hebweb.net with SMTP; 6 Aug 2004 14:43:42 -0000


I am not sure the "Expected Results" is really the good one: it looks like
Mozilla also loses Received: lines when saving an email to a file. But at least
it looks better and contains more informations. Other mail headers may be
affected, I didn't check.

Other bugs concerning Received header are #49305 (FIXED) and #187580 (NEW).

Comment 1

[Frank Wein [:mcsmurf]]

Well, if all headers would be visible there would be no message view anymore.
And you can always look at the message source to get all the headers.
WONTFIX?

Comment 2

[Marc Mongenet]

I didn't know that "Message source" existed, thanks. And it took me several
hours to discover that the "full view" is, well, partial. That's so
counter-intuitive, if it's not at least a major UI bug, then nothing is.

Of course the UI problem can be solved either by displaying a real full view or
by making clear that the full view is not really full.

Anyway I'll never again in my life use this broken "full view", so now I don't care.

Comment 3

[Mike Cowperthwaite]

This symptom is mentioned in bug 106358 comment 7, but otherwise I have not been 
able to find a dupe under Seamonkey.  I'm surprised, because I'm sure I've seen 
this reported in the past.  
Thunderbird bug 254177 describes this same problem.

Reproduced with
  Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.8a3) Gecko/20040806

See also bug 248917.

Comment 4

[Frank Wein [:mcsmurf]]

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

Comment 5

[Marc Mongenet]

I missed the following line in the saved mail:
Received: from [62.220.137.58] (authenticated as bdrayer) by mail.hebweb.net
(MessageWall 1.0.8) with SMTP; 6 Aug 2004 14:43:42 -0000
So it appears that the saved mail is complete and that only the first and last
Received lines are displayed in the "almost full view".

Yes, bug 106358 comment 7 reports exactly this problem. I don't know if it makes
a dup; bug 106358 seems to be about "beautifying" the display and nobody
responded to comment 7.

It looks like reporter of bug 248917 sees many Received headers in random order.
I can only see two headers, but in the correct order.

Comment 6

[Glen Gibb]

(In reply to comment #1)
> Well, if all headers would be visible there would be no message view anymore.
> And you can always look at the message source to get all the headers.
> WONTFIX?

I have to agree with Marc Mongenet that it seems counter-intuitive that view all
headers doesn't display all of the headers. I'd vote for at least following
through with the suggestion about indicating in full view that some header
fields are not shown.

An alternative suggestion is to display one or two Received fields with an
expandable plus symbol next to them like what is done with multiple addresses in
the To: field. (Sorry I don't know enough about the Mozilla internals to
actually implement this myself.)

Comment 7

[Mike Cowperthwaite]

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

Comment 8

[Phil Endecott]

Aaaarrgghhhhhhh!!!!!!!

I have been trying to debug what is going wrong with my mail system and was
totally confused.  I couldn't understand why changes that I was making in exim,
fetchmail etc. did not seem to reflected in the Received: headers of the
messages.  I have spent ages trying to work out why messages were not being
routed how I thought they would be.  Finally it became clear that actually they
were being routed as I wanted, it was just that Thunderbird was hiding all but
two of the Received: headers from me.

Please try to imagine how frustrating this is.

In Evolution and Balsa, "View all headers" does exactly what it says.  What does
Outlook do?

I'd vote for having "View All Headers" actually showing all the headers.  Add a
scrollbar if necessary.  If for some reason you object to that, PLEASE make a UI
change, i.e. replace "View -> Headers -> All" with something like "View ->
Headers -> Most" or "More".

Comment 9

[David :Bienvenu]

Attachment: proposed fix

I think index is only auto incremented for for loops in js...

Comment 10

[David :Bienvenu]

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

Comment 11

[Mike Cowperthwaite]

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