mailing list archives

Working with Yahoo's imap server, I have code that just does a bunch of 
FETCH commands of the
inbox, until they are all downloaded.  In one case, the inbox has 69000+ 
messages.  My code starts
at the highest, and works downward.  After 45 successful message 
downloads, Yahoo responds to
the fetch command with "BAD [CLIENTBUG] FETCH Bad sequence in the command".

Anybody know what this means?  I have had no problem with this code when 
connected to other
imap servers.

Could you show the FETCH command you're sending? 

Though, Yahoo IMAP server is known as one of the worst implementation. 

-- 
Hoa V. Dinh


On Wednesday, March 6, 2013 at 5:18 PM, Jeff McKay wrote:

> Working with Yahoo's imap server, I have code that just does a bunch of 
> FETCH commands of the
> inbox, until they are all downloaded. In one case, the inbox has 69000+ 
> messages. My code starts
> at the highest, and works downward. After 45 successful message 
> downloads, Yahoo responds to
> the fetch command with "BAD [CLIENTBUG] FETCH Bad sequence in the command".
> 
> Anybody know what this means? I have had no problem with this code when 
> connected to other
> imap servers.
> 
> _______________________________________________
> Imap-protocol mailing list
> Imap-protocol@u.washington.edu (mailto:Imap-protocol@u.washington.edu)
> http://mailman2.u.washington.edu/mailman/listinfo/imap-protocol
> 
> 


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman13.u.washington.edu/pipermail/imap-protocol/attachments/20130306/3772b1e3/attachment.html>

On 6 Mar 2013 20:20, "Jeff McKay" <jjmckay@comaxis.com> wrote:
>
> Working with Yahoo's imap server, I have code that just does a bunch of
FETCH commands of the
> inbox, until they are all downloaded.  In one case, the inbox has 69000+
messages.  My code starts
> at the highest, and works downward.  After 45 successful message
downloads, Yahoo responds to
> the fetch command with "BAD [CLIENTBUG] FETCH Bad sequence in the
command".
>
> Anybody know what this means?  I have had no problem with this code when
connected to other
> imap servers.

It mostly means that Yahoo is a crock.

I have a feeling we've seen this one recently, but I don't have the details
to hand. Is this a UID FETCH? And does the UID in the sequence set exist?
If not, then I think Yahoo might reject it, even if it certainly shouldn't
be doing so.

Yahoo will also sometimes not return data for messages that do exist, and
give an error message in the tagged OK (repeating the FETCH works), and
also refuse outright to tell you about other messages (particularly deleted
drafts).

Dave.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman13.u.washington.edu/pipermail/imap-protocol/attachments/20130307/27ebc2ea/attachment.html>

Here is the relevant portion of the log:

<send 38>A123 FETCH 69270 (FLAGS BODY.PEEK[])
<recv 56>A123 BAD [CLIENTBUG] FETCH Bad sequence in the command
<recv 36>* BYE IMAP4rev1 Server logging out

The fetch command is exactly the same as the previous 56, except for the 
message number.

On 3/6/2013 5:21 PM, Hoa V. Dinh wrote:
> Could you show the FETCH command you're sending?
>
> Though, Yahoo IMAP server is known as one of the worst implementation.
>
> -- 
> Hoa V. Dinh
>
> On Wednesday, March 6, 2013 at 5:18 PM, Jeff McKay wrote:
>
>> Working with Yahoo's imap server, I have code that just does a bunch of
>> FETCH commands of the
>> inbox, until they are all downloaded. In one case, the inbox has 69000+
>> messages. My code starts
>> at the highest, and works downward. After 45 successful message
>> downloads, Yahoo responds to
>> the fetch command with "BAD [CLIENTBUG] FETCH Bad sequence in the 
>> command".
>>
>> Anybody know what this means? I have had no problem with this code when
>> connected to other
>> imap servers.
>>
>> _______________________________________________
>> Imap-protocol mailing list
>> Imap-protocol@u.washington.edu <mailto:Imap-protocol@u.washington.edu>
>> http://mailman2.u.washington.edu/mailman/listinfo/imap-protocol
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman13.u.washington.edu/pipermail/imap-protocol/attachments/20130306/bd62191d/attachment.html>