IMAP forever frustrated by bad gmail messages: "The current command did not succeed. The mail server responded:Some messages could not be FETCHed (Failure)."

NEW
Unassigned

Status

9 years ago
6 years ago

People

(Reporter: asuth, Unassigned)

Tracking

(Blocks: 1 bug)

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

9 years ago
For whatever reason, it is possible for gmail to end up in a state where it knows that a message exists and some things about the message, but experience failures when trying to find out more about the message.

The IMAP log looks like this:

S-INBOX:SendData: 10 UID fetch 1:* (FLAGS)
...
S-INBOX:CreateNewLineFromSocket: * 1488 FETCH (UID 1609 FLAGS (\Seen))
...
S-INBOX:CreateNewLineFromSocket: 10 OK Success

S-INBOX:SendData: 11 UID fetch 1609 (UID RFC822.SIZE FLAGS BODY.PEEK[HEADER.FIELDS (From To 
Cc Bcc Subject Date Message-ID Priority X-Priority References Newsgroups In-Reply-To Content-Type)])

S-INBOX:CreateNewLineFromSocket: 11 NO Some messages could not be FETCHed (Failure)


It is possible to figure out who the message is by checking the .msf file and finding out who the adjacent messages are, and then using them to find the bad message.

When I investigate the message in the gmail UI, the message (or rather its conversation) is displayed in the Inbox.  The sender is listed as is the subject.  There is a message snippet displayed, but it is encoded gibberish.  Worth noting is that the sender is listed as the pure e-mail address (automated@newegg.com) while every other message from that address is just displayed as "automated".

From a user perspective, they get an annoying alert dialog once, followed by a growing list of the messages in the activity manager (which eventually make the activity manager extremely lethargic in opening).

While I think the root problem is gmail's and we should try and ask them about this, it would be nice if we could just blacklist the message so we could stop asking after it.
(Reporter)

Comment 1

9 years ago
Forgot to mention.  If I click on the message/conversation in gmail to attempt to display it, it fails to display.  It does its error message thing at the top of the window and goes into an amusing exponential back-off mode of operation that unfortunately still affects the rest of the gmail UI when you get tired of watching it count.
(In reply to comment #0)
> S-INBOX:SendData: 11 UID fetch 1609 (UID RFC822.SIZE FLAG
S BODY.PEEK[HEADER.FIELDS (From T
o Cc Bcc Subject Date Message-ID Priority X-Priority References Newsgroups In-Reply-To Content-Type)])
> S-INBOX:CreateNewLineFromSocket: 11 NO Some messages could not be FETCHed
(Failure)
(In reply to comment #1)
> If I click on the message/conversation in gmail to attempt to display it, it fails to display. 

It looks same Gmail's problem as one reported to Bug 510318, with bad mail pinpointed.

(1) Move the bad conversation to Trash via Gmwil Web Interface.
(Q1) Can the bad conversation in Trash be viewed?
(2) Access [Gmail]/Trash by Thunderbird via Gmail IMAP.
(Q2) Does same FETCH error occur? 
(3) Move the bad conversation to Spam via Gmwil Web Interface.
(Q3) Can the bad conversation in Spam be viewed?
(4) Access [Gmail]/Spam by Thunderbird via Gmail IMAP.
(Q4) Does same FETCH error occur? 

If problem still occurs, report the problem to Google, please.

Note: If the mail is kept in Trash([Gmail]/Trash via Gmail IMAP), the bad mail(evidence) is lost after 30 days because Gmail purges mail in Trash after 30 days, and it can be purged by "Empty Trash" and/or compact operation(EXPUNGE) by Tb for [Gmail]/Trash".
Blocks: 402793
Duplicate of this bug: 510318

Comment 4

6 years ago
All  messages deleted over the last three days cannot be fetched.
You need to log in before you can comment on or make changes to this bug.