Closed Bug 6413 Opened 25 years ago Closed 21 years ago

IMAP logout problem on interrupt

Categories

(MailNews Core :: Networking: IMAP, defect, P3)

defect

Tracking

(Not tracked)

RESOLVED WORKSFORME
Future

People

(Reporter: jefft, Assigned: Bienvenu)

References

Details

Subject:
             Re: Question regarding the status of a connection
        Date:
             Fri, 14 May 1999 11:20:15 -0700
       From:
             jfriend@netscape.com (John Friend)
 Organization:
             Netscape Communications
         To:
             Jeff Tsai <jefft@netscape.com>
         CC:
             David Bienvenu <bienvenu@netscape.com>
  References:
             1 , 2 , 3 , 4




BTW, is 5.0 going to finally fix the IMAP logout problem on interrupt?  This
still causes problems with the UW server as there are
still users losing the flag changes on UW (not as bad as in 4.0x, but still
there).  What we really need to do is issue the IMAP
logout and wait for the BYE response before opening another connection.  I know
that was near impossible in 4.x, but is this now
possible in 5.0?

--John
Status: NEW → ASSIGNED
QA Contact: 4080 → 4098
Target Milestone: M10
Target Milestone: M10 → M13
Moving to m13 - we don't have a stop button to interrupt, and we don't interrupt
otherwise, so there's not much to do here yet.
Target Milestone: M13 → M12
Seems like we need a Stop button for B1. Moving to M12
Blocks: 11091
(target milestone is M11 or M12 - add to mail beta tracking bug)
QA Contact: scurtis → huang
Change QA Contact to me since it's my feature now.
Blocks: 18471
Target Milestone: M12 → M13
Target Milestone: M13 → M14
M14 ...
Keywords: beta1
Need to confirm...beta1 or beta2 or out?
Putting on PDT- radar for beta1.  No worse than 4.x...
Whiteboard: [PDT-]
Keywords: beta1
Whiteboard: [PDT-]
Target Milestone: M14 → M17
moving to future milestone.
Target Milestone: M17 → Future
No longer blocks: 18471
reassigning jefft's bugs to naving
Assignee: jefft → naving
Status: ASSIGNED → NEW
this is related to some issues discussed in bug 58657
closing, file a new bug. this bug does not apply to the current code. 
I meant lot of things have changed. wfm
Status: NEW → RESOLVED
Closed: 23 years ago
Resolution: --- → WORKSFORME
>closing, file a new bug. this bug does not apply to the current code. 

Navin, can you tell me what's the new bug for this problem which apply to the 
current code?
I misread the bug. reopening. 

Status: RESOLVED → REOPENED
Resolution: WORKSFORME → ---
mass re-assign.
Assignee: naving → sspitzer
Status: REOPENED → NEW
taking - is this still a problem in Moz 1.5 or later? I haven't heard any
complaints in a while.
Assignee: sspitzer → bienvenu
Component: Mail Back End → Networking: IMAP
I use mozilla to debug my hobby mail server I've been writing and I haven't 
seen this bug for months.
thx, marking wfm.
Status: NEW → RESOLVED
Closed: 23 years ago21 years ago
Resolution: --- → WORKSFORME
Product: MailNews → Core
Product: Core → MailNews Core
You need to log in before you can comment on or make changes to this bug.