188004 - 'server disconnected mesg' when doing a download/sync now with new mesgs on the server

Status: RESOLVED EXPIRED

(SeaMonkey :: MailNews: Backend, defect)

Description

[grylchan]

using commercial 
2003-01-06-08-trunk/ on xp.

If you do a file|offline|download&sync now and I have incoming
new mesgs on the server that are not yet in my inbox or folders
when I do a download/sync now I will see this alert mesg

 'Server blah has disconnected. The server may have gone down or there
  might be a network problemm'.

It only does that if there are new mesgs on the server and not in my inbox
or folder. If there are no 'new mesgs', you won't see this alert.

I'm guessing looking through lxr that the change on dec 15 (1.465) to
http://bonsai.mozilla.org/cvslog.cgi?file=mozilla/mailnews/imap/src/nsImapProtoc
ol.cpp

caused this.

steps
1.Open up imap mail acnt
2.Select inbox for downloading
3.Do a download/sync now, check work offline checkbox
4.Go back online
5.Send yourself a mail mesg
6.Do a download/sync now

result: alert mesg appears
expected: alert to not appear

Comment 1

[David :Bienvenu]

that change would make it less likely to get that message, not more likely.

Comment 2

[grylchan]

hmm...ok but I wonder why I am seeing the alert now

Comment 3

[Andy Ozment]

Note that this bug deals with the same error messages as bugs:
187395 <http://bugzilla.mozilla.org/show_bug.cgi?id=187395>
and
196095 <http://bugzilla.mozilla.org/show_bug.cgi?id=196095>

This comment indicates that the problem may be resolved in build 1.5:
<http://bugzilla.mozilla.org/show_bug.cgi?id=196095#c10>

Comment 4

[Robert Kaiser]

MASS-CHANGE:
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614

Comment 5

[Robert Kaiser]

MASS-CHANGE:
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614

Comment 6

[Robert Kaiser]

MASS-CHANGE:
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614

Comment 7

[Robert Kaiser]

MASS-CHANGE:
This bug report is registered in the SeaMonkey product, but still has no comment since the inception of the SeaMonkey project 5 years ago.

Because of this, we're resolving the bug as EXPIRED.

If you still can reproduce the bug on SeaMonkey 2 or otherwise think it's still valid, please REOPEN it and if it is a platform or toolkit issue, move it to the according component.

Query tag for this change: EXPIRED-20100420