281019 - must restart Thunderbird to get new mail after No space left on device

Status: RESOLVED INCOMPLETE

(Thunderbird :: General, defect)

Description

[Simon Kissane]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0
Build Identifier: Thuderbird version 1.0 (20041206)

I am using IMAP to get my email from a Solaris box. Regularly (generally after I
have had Thundebird open for a while -- sometimes for just a few hours,
sometimes for days on end), I stop getting mail. Clicking on "Get Mail" says no
messages on the server. But if I exit thundebrird and start it again, suddenly
my mail is there. Also, when it gets like this (no new mail arriving),
Thunderbird will often hang for ages on openning new messages or deleting them,
and when I restart Thunderbird messages I deleted when Thunderbird was in this
state are not deleted any more.

I have used Microsoft Outlook from the same Windows PC, and PINE from Unix
systems, to access my IMAP mail box on the same Solaris box before, and never
had this problem with them.

Reproducible: Sometimes




I am trying to trace what happens with Ethereal, if that is any useful, and if I
can work out what happens I will let you know.

Comment 1

[Simon Kissane]

A trace in Ethereal indicates the following message:
   57  NO CHECK failed : Checkpoint file failure: No space left on device...
at the time this occurs. Consulting with the sysadmin indicates that at the time
this message occurs the /var filesystem on the Solaris box was full.

Suggestion: Thunderbird should detect this condition and give a friendly error
message...

Comment 2

[Gary Kwong [:gkw] [:nth10sd] (NOT official MoCo now)]

Reporter, does the issue still occur with the latest supported 2.0.0.x / Shredder trunk nightlies?

(1.5.0.x is now end-of-life and the latest supported Thunderbird version 2 is 2.0.0.16)

Comment 3

[Joshua Cranmer [:jcranmer]]

RESO INCO per lack of response to the last question. If you feel this change was made in error, please respond to this bug with your reasons why.