171197 - IMAP server (Exchange 2000) error on certain IMAP fetch commands, Unrecognized internal error: 0x8004011b

Status: RESOLVED INCOMPLETE

(MailNews Core :: Networking: IMAP, defect)

Description

[Neal Ziring]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.2a) Gecko/20020910
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.2a) Gecko/20020910

Setup: Mozilla 1.2alpha configured as IMAP client, IMAP server MS Exchange 2000 :-(

Behavior: connect to mail server okay, select a folder, get popup Alert with
message "The current command did not succeed: The mail server responded:
Unrecognized internal error: 0x8004011b".   Folder still seems to work, but
synchronization (File->Offline->Download/SyncNow) fails.

Note: using the same versions of Mozilla with Exchange 5.5 never had this
problem; the bug surfaced only with Exchange 2000 (in particular, Exchange 2000
at service pack 2 is the only edition I can test).


Reproducible: Always

Steps to Reproduce:
1. Start Mozilla
2. Pop up Mail/News window
3. Select Inbox

Actual Results:  
Alert dialog pops up: "The current command did not succeed: The mail server
responded: Unrecognized internal error: 0x8004011b"

The same dialog pops up when attempting to perform Download/Sync Now.

Expected Results:  
Expected same behavior with Exchange 2000 as observed for Exchange 5.5: 
correct operation with no Alert dialogs.

Note: I realize that this is certainly a bug in Exchange; I looked at the IMAP
message that Mozilla is sending using Ethereal sniffer, and the message looked
perfectly legal.  However, Exchange 2000 is such a widespread mail server that
I think it might be best if Mozilla incorporated a workaround for this problem.

I think this might be a duplicate of bug 114576, but that bug is marked 
resolved.

I took a IMAP log using NSPR_LOG_MODULES; I will attach the entire log, but
here are the killer lines:

1476[2520350]: twinkie:S-Received/exec-con:SendData: 4 UID fetch 232,244:245
(UID RFC822.SIZE FLAGS BODY.PEEK[HEADER.FIELDS (From To Cc Subject Date
Message-ID Priority X-Priority References Newsgroups)])

1476[2520350]: twinkie:S-Received/exec-con:CreateNewLineFromSocket: 4 NO
Unrecognized internal error: 0x8004011b

I haven't gotten to analyze this problem thoroughly, but I watched it occur
about a dozen times in Ethereal, and the offending fetch commands always
seem to include message ranges that are only 2 long, 
such as "1249:1250" or "244:245" or "1298:1299".  I've never
been able to make the error occur for a folder with only one message,
because the fetch always just lists that single message.   Watching
other traffic, identical fetch commands with ranges like "1:27" seem
to succeed.

Comment 1

[Neal Ziring]

Attachment: IMAP:5 NSPR log showing the bug occurring

The bug is shown in the very last lines of the protocol trace.

Comment 2

[Florian Leeber]

WFM with Exchange 2000 SP2 and Mozilla 1.2beta 2002101612

Sorry, works rather perfect here ;-)

Comment 3

[Johan De Meersman]

Occurs using "Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2.1) Gecko/20021130"
and I presume Exchange 2000, worked with 5.5.

Pretty annoying :)

Comment 4

[Steve]

Also received this in Mozilla 5.0 (rev 1.7.1), with Unrecognized internal error
0x80040108.

Comment 5

[daneel]

Attachment: Thunderbird log

Comment 6

[daneel]

Comment on attachment 170083 [details]
Thunderbird log

I'm getting the same error. Log file is attached showing the error at line:
2964[1fba9f0]: 20026e8:midway.msoe.edu:S-INBOX:CreateNewLineFromSocket: 9 NO
Unrecognized internal error: 0x8004050a

Comment 7

[daneel]

any news on this bug???

Comment 8

[Gervase Markham [:gerv]]

This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/

Comment 9

[Gervase Markham [:gerv]]

This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.

Comment 10

[risto.kankkunen]

As I report on bug 326833, I seem to have this same problem with Thunderbird 1.5 on Windows XP connecting to Exchange IMAP server (probably 2000).

Currently the only place I see this constantly is with one of my virtual folders. Manually accessing most of the folders seems to work just fine. I'll try to see, if I have folders with just 2 messages, that would trigger the problematic range request...

I'll see if I can take logs to verify the earlier reports...

Comment 11

[Wayne Mery (:wsmwk)]

anyone still see this problem?  (note: some of you state different error codes)

risto, the error code of this bug is 0x8004011b but yours is 0x8004050a 

Comment 12

[Wayne Mery (:wsmwk)]

see 2 logs attached.   daneel and neal might not be around anymore.

Comment 13

[Wayne Mery (:wsmwk)]

 bug 326833 is still open