Open Bug 208013 Opened 22 years ago Updated 4 months ago

Get messages/get msgs on newsgroup displays no new messages on server after new message headers are displayed

Categories

(SeaMonkey :: MailNews: Message Display, defect)

x86
All
defect
Not set
minor

Tracking

(Not tracked)

People

(Reporter: mrmazda, Unassigned)

References

(Blocks 1 open bug)

Details

Test builds: 2003052113 OS/2 trunk; OS/2 1.4rc1; W32 1.4rc1 Longer summary: fetching messages on newsgroup displays "There are no new messages on the server" as and after arriving/new message headers are displayed. "No new messages" should only display if there were in fact no new messages. To reproduce: 1-Open any newsgroup 2-Sort headers by messages ascending 3-Scroll to bottom of header pane 4-Wait for new messages to arrive on server 5-Click get msgs Actual results: 1-New message headers display in header pane 2-"There are no new messages on the server" displays briefly on the status bar 3-Message area of status bar goes blank Expected results 1-New message headers load in header pane 2-As message headers are loaded, a status message somewhere indicates downloading progress 3-On completion, message somewhere indicates # of messages that "arrived"
Product: Browser → Seamonkey
Assignee: sspitzer → mail
Maybe a dupe of bug 20548? Once all messages are loaded, the Get New command clears the New flag for all items, so "no new items" is arguably correct.
Assignee: mail → nobody
QA Contact: esther → message-display
I have not found this problem in earlier versions, only in 2.5. I had 2.4.1 installed, with myltiple email and newsgroup accounts set up and working. I downloaded 2.5 and installed it as an update. Mail still worked perfectly, but I then found that although newsgroup headers displayed, and new headers were fetched as expected, I could not see the content of the messages, previously read or new. Running a Wireshark trace suggested that whilst the headers were being retrieved, nothing was getting the message content. Uninstalling 2.5, and reverting to 2.4.1 fixed the problem.
Blocks: 1955121
You need to log in before you can comment on or make changes to this bug.