User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; rv:1.9.1b3pre) Gecko/20090111 SeaMonkey/2.0a3pre Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; rv:1.9.1b3pre) Gecko/20090111 SeaMonkey/2.0a3pre When viewing mail, although I can see mail in inbox in preview window by selecting them from list in folder, sent emails intermittently will all appear blank. Rebooting SeaMonkey will intermittently correct the problem. It is occurring on two different machines, and has been for several weeks. It occurs in all accounts, even those with few sent messages. Yet the messages can be seen on subsequent sessions (I can't figure out what determines this.) Attempting to double click messages in folder to open them in separate window, attempting to forward them, attempting to edit them as new, all just act as if message were blank. Reproducible: Sometimes Steps to Reproduce: 1.open email 2. select sent mail folder from an account 3. click on one of the sent emails displayed on the list 4. maybe you see something in the preview window, maybe you don't Actual Results: I can't consistently reproduce it, though it is happening more often than not. Expected Results: The from, to, subject and message body should display

This is an Duplicate of Bug 472116, which was Duped to Bug 471682. Here it works to rightclick -> Properties -> Rebuild Summary-File to get the Messages displayed again.

There would be fewer duplicate bugs if the search function worked better. Searches seem to deal with the search terms using "OR" rather than "AND," so there are a large number of unrelated results for other products to sort through. In this case, I searched using quite a few different terms, thinking it highly unlikely no one would have reported it, but I couldn't see one that sounded like my problem. The title and original description of bug 471682 did not match the problem I was seeing, but the subsequent discussion did. I would suggest that active bugs have a summary statement, revised as information is sorted out, that describes the behavior users will see (and which describes it in such a way that it can be identified without knowing the files being written, etc.). And I would suggest the search function have the kind of decision tree used in the reports themselves, so one would choose SeaMonkey/2.0a3pre, then choose email, then search within those results, having a choice of "AND" or "OR" operands, and being able to sort results by date reported, severity, etc.