Closed Bug 149273 Opened 23 years ago Closed 22 years ago

get new mail: no result at all (IMAP)

Categories

(MailNews Core :: Networking: IMAP, defect)

x86
Linux
defect
Not set
major

Tracking

(Not tracked)

RESOLVED INVALID

People

(Reporter: fl, Assigned: mscott)

Details

(I found some similar entries, but none really seems to be exactly what I am experiencing here with 1.0 RC3 Linux) After the first login to IMAP, where the inbox is correctly retrieved, *never again* (until complete restart) getting new mail succeeds. (There really is new mail, and it can be retrieved with other clients) Some info that might help: - Server: * OK <host> IMAP4rev1 v12.250 server ready - Listening on ethereal and comparison to old NS4.7: The first noop and fetch-command, including answers, are totally identical (mozilla and ns4). But after that, where ns4 goes on with another noop and lots of fetches to other IDs, mozilla simply does nothing more, it stops here. Last packet is: Response: 6 FETCH (UID 12345 FLAGS (\Seen)) Hope that helps and Thanks for your work!
1. As 1.0 came some hours after this report, of course the problem is still in there 2. Meanwhile I tested another, external IMAP-Server (web.de). It worked. So this problem *could* be the fault of the server (but then all other clients I know tolerate it)
QA Contact: huang → gchan
Reporter: Can you reproduce this bug with a recent build of Mozilla (for example, 1.4rc3)? If so, then please comment again with details. If not, then please resolve this bug as WORKSFORME. Thanks.
We do not have the above IMAP-server running anymore, so I cannot test it. As noone else was reporting here, I guess we can close this. Just don't know what status is appropriate here: its not fixed, invalid, worksforme or wontfix (maybe it is, maybe not..) - more of a "we'll never know" :) Guess some of you have the right to simply set it "closed". Thanks for caring.
comment 3, closing
Status: UNCONFIRMED → RESOLVED
Closed: 22 years ago
Resolution: --- → INVALID
Product: MailNews → Core
Product: Core → MailNews Core
You need to log in before you can comment on or make changes to this bug.