This site will have limited functionality while we undergo maintenance to improve your experience. If an article doesn't solve your issue and you want to ask a question, we have our support community waiting to help you at @FirefoxSupport on Twitter and/r/firefox on Reddit.

Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

Thunderbird error: The STAT command did not succeed.

  • 3 replies
  • 1 has this problem
  • 1 view
  • Last reply by vdsass

more options

Mac OS X Mojave 10.14.2 Thunderbird 60.5.0 (64-bit)

Reading email from server elicits the following error message:

The STAT command did not succeed. Error getting message number and sizes. Mail server --- responded: Mailbox is in inconsistent state, please relogin.

OS X Mail client works without error. ISP Web Mail client works without error.

I need help finding a solution.

Mac OS X Mojave 10.14.2 Thunderbird 60.5.0 (64-bit) Reading email from server elicits the following error message: The STAT command did not succeed. Error getting message number and sizes. Mail server --- responded: Mailbox is in inconsistent state, please relogin. OS X Mail client works without error. ISP Web Mail client works without error. I need help finding a solution.

Chosen solution

On Thursday 7 February the TB client started downloading messages. Not sure where the problem was, but now it's working.

Read this answer in context 👍 0

All Replies (3)

more options

Who is the mail provider? The STAT command is a part of the POP mail protocol. Have you set the account up using IMAP mail server names perhaps?

more options

The ISP is cox.net The account has always been a POP account. Mail was being retrieved until early January, then stopped. Cox says nothing is wrong on their end - also can read mail with other email clients.

more options

Chosen Solution

On Thursday 7 February the TB client started downloading messages. Not sure where the problem was, but now it's working.