Closed Bug 337276 Opened 18 years ago Closed 18 years ago

STATUS failed error when connected to IMAP server

Categories

(Thunderbird :: Mail Window Front End, defect)

x86
All
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: bugzilla, Assigned: mscott)

Details

Attachments

(1 file)

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.0.3) Gecko/20060426 Firefox/1.5.0.3
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.0.3) Gecko/20060426 Firefox/1.5.0.3

I'm not really sure where the root of this problem is.  Whether it's the server or the mail client.

The only conclusion I could come to is that Thunderbird is attempting to connect to the IMAP server and unable to get an appopriate status.  I don't know much about the IMAP protocol.

This happens even when I create a new profile.  I've reproduced this error in windows and linux.

The only thing of significant change was adding:
user_pref("mail.check_all_imap_folders_for_new", true);

I'm guessing that TB opens multiple ports to the one address and is getting a hickup.

Reproducible: Sometimes

Steps to Reproduce:
1. Add "user_pref("mail.check_all_imap_folders_for_new", true);" to user.js, per instructions included in http://www.mozilla.org/support/thunderbird/tips#beh_downloadstartup
2. Restart TB.
3. Wait for it...
4. "STATUS failed"

Actual Results:  
TB operates correctly.  I can still access my mail.  But any time I try to access a new folder, TB gives me the error "STATUS failed"

Expected Results:  
No error.
we use the STATUS command to check folders for new messages. Not sure why the command would fail. Perhaps it's unhappy with issuing STATUS on a particular folder. You can individually select folders to be checked for new messages using the folder property dialog, instead of checking all folders - if you don't have a huge number of folders, that would be something to try.

you can also generate an imap protocol log to see what folder is not working:

http://www.mozilla.org/quality/mailnews/mail-troubleshoot.html#imap
Selecting each folder to be checked would be synonmous as me enabling all of them.  (I use procmail to filter my mail.)

I've done the imap protocol log.  Here's the error:
-1283216464[94ca2b8]: 93a2aa0:mail.mikesoh.com:A:CreateNewLineFromSocket: 36 NO [ALERT] STATUS failed
what would be interesting is the command that generated the error.

Is it all folders that generate the error? I was hoping it was just one folder that was failing with the STATUS command.
3 megs big...be careful
yes, thx, looks like INBOX.archives.sent-mail is the folder that the server is unhappy about. The other folders all seem to be OK with the STATUS command.
thanks for debugging it!

I fixed the error...closing.
Status: UNCONFIRMED → RESOLVED
Closed: 18 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: