Mail pops up a dialog asking 'Advance to next unread message in ___?' after I've clicked Next through all the unread messages in the current folder. Unfortunately, when I click 'Ok,' Mail jumps to the next unread, but the message view remains blank. The message does appear if I reselect it after viewing a different item.

More information needed: What build were you using? Does this happen frequently, is it reproducible? What kind of account was this, and was it going to next unread within the account or in another account? Was the destination folder set to any particular message view? (View|Messages|...) Was there anything special about the message which didn't display (web page attached, etc.)?

This bug is present in at least 0.9.2.1 and 2001100408, and it's 100% reproducible. The account is a POP account, and both folders check mail from the same account (one is the Inbox, and the other contains filtered messages.) Both folders are using the threaded view, and this occurs for all messages -- there's nothing special about the e-mails, as far as I know.

I just tried POP with win98 and linux rh6.2, oct5 0.9.4 branch. I'm seeing this on and off -- sometimes it will display content, sometimes not. I tried using Next button, spacebar and N shortcut -- all seem equally inconsistent as to whether the message content loads or not.

Happens only with cross folder navigation. I have not yet gotten a failure to load the content in this POP filter scenario when navigating Next/spacebar/N within folder or using mere select folder, select message to avoid cross folder navigation.

Confirmed it's also in 6.1 rtm, any (move or copy manually or via filter) POP cross folder navigation may or may not load the message content.

nominating for next release

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

This bug smells like bug 59638, but I'll let you all make the final call.

Yes, sounds like bug 59638, and since that one is approved nsbeta1+, I'm calling this a duplicate. Will hit various scenarios on all platforms anyway when verifying. *** This bug has been marked as a duplicate of 59638 ***

I don't think it is the same as bug 59638, although it is probably related. I *never* have problems moving between newsgroups, and almost always have problems when moving about my local folders where I have my incoming mail filtered to.

I think this is also the same as bug 82833.

Seeing the same in Mozilla 0.9.8 Win32 (build 2002020406).

I was searching Bugzilla and accidentally found this bug. It looks very similar to the one that I have reported for OFFLINE reading news across newsgroups - http://bugzilla.mozilla.org/show_bug.cgi?id=127625 In my case it often appears for offline mode and never for online. Menu View->Reload always helps. Selecting other message and then back also helps. With previous buids was always reproducible, but now appears in approx. 9 cases of 10. I am not a programmer, so don't lynch me. I have a suggestion. Reading POP mail and reading news in offline are similar situations - in both cases message first stored to disk and then loaded. Maybe somewhere here the problem is hidden.

Have had this very problem persistantly ever since installing Mozilla 20020222 (at least)... VERY reproducible...even on RC1. :( Workaround is to select the previous message, allow it to start loading, then switch to the message you should have seen. Like Victor, I'm not a programmer (yet) so can't really offer any constructive ideas on how to stop this cold. I will note, however, that I've never seen this on Netscape 4.xx, and don't recall seeing it back in Mozilla M12-M16 days, although those builds would often crash out due to my (then) marginal RAM, so have no clear idea of when I first truly noticed the problem.

I have just noticed, that this bug is still present in Mozilla 1.0 RC3. Although I have to admit, that the bug is not critical, it is still annoying.

I've noticed that this seems to work in 1.1a, I think I remember it working in 1.0 release, too. Still not resolved?

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

Even though news might not be affected (as for me), this is definately bug 59638. pi

*** This bug has been marked as a duplicate of 59638 ***

marking verified duplicate.