203217 - Number of lines is always shown as 1

Status: RESOLVED EXPIRED

(SeaMonkey :: MailNews: Message Display, defect)

Description

[Abhishek]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.3) Gecko/20030312
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.3) Gecko/20030312

When I post a message to a newsgroup using mozilla, it shows the "Lines" in each
of the messages. Mozilla shows the line numbers of all the messages on the
newsgroup correctly except the one which was posted by me.

When I post a message using mozilla and it appears on the ng, mozilla shows that
message as having 1 line. even though the message has many lines. But for
messages posted by others, it shows the line numbers correctly.

Reproducible: Always

Steps to Reproduce:
1. post a message on use net with multiple lines
2. in the main window make sure that the "Lines" is present along with "subject,
sender, data etc"
3. when the message appears on the newsgroup the number of lines is shown
incorrectly only for this message. mozilla shows the lines correctly for all
other messages posted by other users.

Actual Results:  
when the message appears on the newsgroup the number of lines is shown incorrectly.


Expected Results:  
Shown the correct number of lines as it does for all the other messages.

Comment 1

[Mike Cowperthwaite]

Unable to duplicate this with 1.3 Final, Windows 2000.

Can you provide a pointer to a message that does this?  Post one to
 netscape.test

Comment 2

[Abhishek]

I got your message about not being able to duplicate the problem.

Unfortunately, when I use mozilla to post messages on the news server, I have to
go thru my company firewall which allows the visibility to only a few news
servers and netscape is not one of them. (though I can read and post to netscape
groups using google).

Now to duplicate the problem I have posted one test message on microsoft.test 
newsgroup (sorry about that ... but that is one test group which our firewall
allows).

The subject of the message is "[Abhishek] Test for Mozilla news reader problem"
posted on 30th April 4:39 PM. It contains many lines of junk... but mozilla
shows only 1 as line number.

Hope this will help you in observing this problem.

Comment 3

[Mike Cowperthwaite]

OK, I found that message.  Reading the group with either 1.3 Final or 1.4b 
(0430), and looking at the "Lines" column, it shows has having 12 lines, which 
matches what I see looking at the message.

However, looking at the source for message (Ctrl-U), the 'Lines' header is '1'.

Looking for comparison at messages I have posted, the 'Lines' header in those is 
set to the correct number.

I have saved your message to a file, and will attach it to this bug.

Confirming.

Comment 4

[Mike Cowperthwaite]

Attachment: The message posted by Abhishek

Shows 'Lines: 1' header despite the dozen lines in the file.

Retrieved from group microsoft.test, server news1.toast.net

Comment 5

[Robert Kaiser]

MASS-CHANGE:
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614

Comment 6

[Robert Kaiser]

MASS-CHANGE:
This bug report is registered in the SeaMonkey product, but still has no comment since the inception of the SeaMonkey project 5 years ago.

Because of this, we're resolving the bug as EXPIRED.

If you still can reproduce the bug on SeaMonkey 2 or otherwise think it's still valid, please REOPEN it and if it is a platform or toolkit issue, move it to the according component.

Query tag for this change: EXPIRED-20100420