Closed Bug 781543 Opened 12 years ago Closed 12 years ago

"system error (failure)" on my GmailImap account Tb 14.0, Xubuntu 12.04 Gmail IMAP

Categories

(MailNews Core :: Networking: IMAP, defect)

x86
Linux
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED INVALID

People

(Reporter: castrop, Unassigned)

References

()

Details

(Whiteboard: [GS])

Attachments

(2 files)

User Agent: Mozilla/5.0 (X11; Ubuntu; Linux i686; rv:14.0) Gecko/20100101 Firefox/14.0.1
Build ID: 20120730163036

Steps to reproduce:

nothing or better:just opened Thunderbird as usual


kind regards


Actual results:

On my Gmail Imap account I got this error message when opening my in incoming messages folder: l'opération courante "courrier entrant n'a pas abouti. Le serveur de courrier pour le compte xxx@gmail.com a répondu: system error (failure)".
 Sending messages is ok, reading and sending ok in my other Tb accounts.

Suddenly happened yesterday after years of fine working; I mean: no new installation of Ubuntu 12.04 neither Tb 14.0. Erasing inbox.msf didnt change anything


Expected results:

no idea
please see the TbTracer log in attachment
It may be a Google failure, if I trust https://getsatisfaction.com/mozilla_messaging/topics/gmail_server_system_error_failure#reply_9706669
Component: General → Networking: IMAP
Product: Thunderbird → MailNews Core
Whiteboard: [GS]
we got 12 people reporting this problem on GSFN, which is quite high!
This really looks like gmail failure :(
Do we wait that Gmail solve this issue to close this bug report or can we do that already (as INVALID)?
(In reply to caméléon from comment #5)
> Do we wait that Gmail solve this issue to close this bug report or can we do
> that already (as INVALID)?

I thought I had.
Status: UNCONFIRMED → RESOLVED
Closed: 12 years ago
Resolution: --- → INVALID
topic cited earlier was getting complicated, and I have terribly short memory - so I've made https://getsatisfaction.com/mozilla_messaging/topics/system_error_failure canonical
You need to log in before you can comment on or make changes to this bug.