88398 - not all new mail shows up

Status: RESOLVED WORKSFORME

(MailNews Core :: Networking, defect)

Description

[--disabled--Steve A Fink]

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux 2.4.5 i686; en-US; rv:0.9) Gecko/20010505
BuildID:    2001050521

I have an IMAP account, and quite frequently when I either start up Mail from
scratch, or click on another folder and then back to my inbox, only some of my
new mail appears. The mail is in the correct file on my server, and Netscape
4.76 does not display this problem. (I've switched back to it for mail.)

If I keep retrying over and over, I generally get more of it. Not sure if I get
all of it.

I will often get later messages before earlier.

I have mostly noticed it when I have large batches of messages sent in rapid
succession (they're per-file change logs generated by CVS), but that's most
likely just because it's easiest to notice it happening.

Unfortunately, it's rather sporadic.

I use server-side mail filtering (procmail)

Reproducible: Sometimes
Steps to Reproduce:
1. Generate several bursts of mail
2. Filter the mail via procmail into an mbox on the server
3. Start up Mozilla's Mail
4. Curse
5. Repeat


Actual Results:  Some of the messages showed up in the inbox

Expected Results:  All of the messages should show up in the inbox

Comment 1

[Keyser Sose]

Reporter do you have the mail log from the times you had the problems?

Comment 2

[--disabled--Steve A Fink]

Where would I find the logs? (It just happened again yesterday.)

btw, I'm not sure if this really constitutes data loss; I eventually get all the
messages.

Comment 3

[Christopher Aillon (sabbatical, not receiving bugmail)]

I don't use IMAP, but I see this on POP as well with recent linux builds.  It
rarely happens but it's happened on a few occasions with bugzilla mail.  This
isn't critical, but I will leave at major because many people rely on mail. 
Also removing dataloss keyword and sending to networking general since this
isn't just imap.

Comment 4

[Wayne Mery (:wsmwk)]

do you still see this problem?

Comment 5

[--disabled--Steve A Fink]

Not that I've noticed.

Comment 6

[Wayne Mery (:wsmwk)]

WFM then.