Closed
Bug 188271
Opened 22 years ago
Closed 21 years ago
next unread message goes to newsgroups instead of following mail account
Categories
(SeaMonkey :: MailNews: Message Display, defect)
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 201392
People
(Reporter: alanweber, Assigned: mscott)
Details
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.3b) Gecko/20030108 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.3b) Gecko/20030108 If you have already read all messages in your first main account and have some unread in your second one, pressing N to go to the next unread message offers to go to next unread message in newsgroups before the other mail accounts. Reproducible: Always Steps to Reproduce: 1. Let's have a profile with more than one mail account and at least a newsgroup. 2. Have unread messages in all accounts. 3. Read all messages in first mail account and press N to read next. Actual Results: Moz offers to switch to the newsgroup account Expected Results: Should travell next mail accounts before going to newsgroups. I think Moz should travel all account downward in the order they are displayed, and cycle from last -at bottom- to first -at top- if nessesary.
Reporter | ||
Updated•22 years ago
|
Component: Mail Back End → Mail Window Front End
I have seen this too with an IMAP, POP, and NNTP account on Windows. I'll be in account #2 (POP) and there's unread mail in that account but lower in the folder list. Hitting next message will take me to a folder in the IMAP account (#1), sometimes it will take me to the NNTP area (#3) if it's opened and showing unread messages.
Comment 2•21 years ago
|
||
Bug 201392 reports a similar symptom, with the key fact that the folders being skipped over must contain only one new message. Same thing?
Comment 3•21 years ago
|
||
*** This bug has been marked as a duplicate of 201392 ***
Status: UNCONFIRMED → RESOLVED
Closed: 21 years ago
Resolution: --- → DUPLICATE
Updated•20 years ago
|
Product: Browser → Seamonkey
You need to log in
before you can comment on or make changes to this bug.
Description
•