Bill Davidsen wrote:
No suggestion, but a thought: is this inbox set against an IMAP mail server?
Because the limitation might be on the server end if so, caused by some behavior
related to what is don't on first connect. Of course there could be a problem
with SM "forgetting" subfolders at that level, I haven't seen it happen with
POP3 mail servers, because I am down four levels below the inbox on one and have
been for years.
I have noted that in the past a subfolder did become broken in some way, but
that was back in 1.0.xx days, not in years.
This one is a "me too"... I'm having similar issues on a Windows
installation of Seamonkey. I started seeing it after I upgraded to
2.0.x. It seems to happen less frequently than it used to, and I don't
have it as frequently under Windows 7 as the report here is for running
under Ubuntu.
For me, the problem area is with a POP account. The first level folder
is one titled z-forums-traffic, and the folders contained there are
nearly all targets of rules.
One thing that I did test is that when the top-level folder's name is
shown in boldface, noting that at least one sub-folder has a new
message, use of the "n" command for "next unread folder" won't force the
container open -- it does require a restart of Seamonkey.
I posted a question about this back in April "Folders handling in SM2",
but never got any response. I did note in a follow-up that I see a lot
less of the problem following SM 2.0.4, but it still turns up
occasionally, although for me, it's something that happens infrequently
enough that it's an annoyance I can live with.
I haven't checked this behavior on my Ubuntu box.
Smith
_______________________________________________
support-seamonkey mailing list
[email protected]
https://lists.mozilla.org/listinfo/support-seamonkey
