Closed Bug 32531 Opened 24 years ago Closed 24 years ago

Message does not receive until exit/relaunch for the latest first IMAP migrated mail account

Categories

(MailNews Core :: Backend, defect, P3)

defect

Tracking

(Not tracked)

VERIFIED FIXED

People

(Reporter: fenella, Assigned: Bienvenu)

Details

Linux (2000-03-20-08 M15)
Steps:
1. Launch messenger using the -mail option
2. Compose a message and send it to myself in this IMAP account
3. Click on Get Msg, no response, I have password saved
Actual result: No response, do not see new message. When I exit and re-launch, I
see the new message
4. Send a new message from Nova to this account, also, no new message is
received.
Expected result: I expect Message thread appears when new message is received.

This occurs on Linux only. Imap account only.
Win32 (2000-03-20-11 M15)
This problem now exists in the Win32 commercial trunk build. 
OS: Linux → All
Hardware: Other → All
more fallout from our fun with flags.
Assignee: phil → bienvenu
accepting
Status: NEW → ASSIGNED
Change QA contact to me.
I have tried for today's 03-27-09-M15 commercial build . It seems that problem 
only occurs  on the first time launch after the installation.
After the second time launch will receive mail as normal.
QA Contact: lchiang → huang
this works fine for me. What do you have selected when you click Get Msg? 
Nothing? Or the imap server account? This works for me if I have the imap server 
selected but not if I have nothing selected. If I have nothing selected, my 
guess is that somehow we don't know what the default server is, which is not an 
imap problem.
works for me. The front end code doesn't do anything if nothing is select when 
Get Msgs is pressed.
Status: ASSIGNED → RESOLVED
Closed: 24 years ago
Resolution: --- → WORKSFORME
Used today's build for migrated profile (removed mozregistry.dat & User50)

Problem still occurring on Windows if I am using today's first migrated IMAP 
mail account .....I cannot get the message after sent to myself (no matter save 
password or not?!) Anybody got the same problem as me?
I need to exit/relaunch to get the new message.
Problem won't occur after the second IMAP mail account.
It's so strange for today's build. bug#35029 also logged regarding to Linux 
abnormal Alert for today's build for migrated IMAP mail account.....
reopening this bug since problem still occuring and can be reproduced after  
remove the mozregistry & User50 and trying to get the first migrated IMAP mail 
account....
Status: RESOLVED → REOPENED
Resolution: WORKSFORME → ---
Updating this summary for narrow down this problem....
Summary: IMAP: Message does not receive until exit/relaunch → Message does not receive until exit/relaunch for the latest first IMAP migrated mail account
What is this bug's Target Milestone?
m17
Target Milestone: --- → M17
Seth says this is working for him now - does it work for you in today's build? 
(I've never been able to recreate it myself)
I'm not 100% convinced that the ClearFlags() fix has solved this problem.

give me a few days to convince myself that I no longer see the alert.
Problem is still occurring on today's 04-13-06-M15 commercial build.....
The received message is not displaying right away, but after you select the other 
folder and come back to Inbox folder or relaunch application, then messages will 
display on the thread pane. I remember there was another bug describe the same 
symptom, but I don't know which bug?!
fix checked in - problem was when we blew away an imap db because the uid 
validity was wrong, we weren't maintaining the flags (or anything else) across 
the dbs. When we open a folder for the first time, it looks like the uid 
validity has changed.
Status: REOPENED → RESOLVED
Closed: 24 years ago24 years ago
Resolution: --- → FIXED
>The received message is not displaying right away, but after you select the 
>other folder and come back to Inbox folder or relaunch application, then 
>messages will display on the thread pane.

It seems that this problem is still occurring by using this morning commercial 
build.....
Hmm....I was using yesterday's migrated profile...but after I used today's new 
migrated profile (removed User50 & mosregistry file today)....it seems this 
problem is not occurring on WinNT & Linux platforms but block by Mac37580 for 
Mac platform....I need to wait that bug fixed in order to verify this 
bug....still keeping this bug open....
I mean bug37580
Based on previous comment & bug 37580, this problem should be gone for a while.
Problem is currently not occurring on all the platforms either.
(Buils are: WinNT, Linux & Mac 07-20-08/09-M17 commercial builds)
Marking as verified!!
Status: RESOLVED → VERIFIED
Product: MailNews → Core
Product: Core → MailNews Core
You need to log in before you can comment on or make changes to this bug.