Closed
Bug 77184
Opened 24 years ago
Closed 24 years ago
hang attempting to put mail in non-existent IMAP folder
Categories
(MailNews Core :: Backend, defect)
Tracking
(Not tracked)
People
(Reporter: loeb, Assigned: mscott)
Details
(Keywords: hang)
On my win98 machine, running build ID: 2001041804:
I do not have a "sent mail" folder on my IMAP drive, only on my local drive.
After sending a message, the client tries to write a copy to my IMAP "sent"
folder. When it doesn't see it there, it should default to my local "sent"
folder automatically. Instead, it simply hangs, causing me to have to
cntrl-alt-delete and re-boot the program.
Updated•24 years ago
|
Severity: normal → critical
Keywords: hang
Summary: Copying sent mail to sent folder → hang attempting to put mail in non-existent IMAP folder
Comment 1•24 years ago
|
||
I saw this on Jeremy's machine. In these cases, if a sent folder doesn't exist
in the target IMAP account, we should fail gracefully and default to a sent
folder thast does exist, the Sent folder in Local.
There's probably an older bug or two on this.
QA Contact: esther → sheelar
Comment 3•24 years ago
|
||
You might think so, but a search of all IMAP-related bugs (or messages with
IMAP in the summary) reveals no currently open bugs with this issue.
Also, confirmed on 2001050212-Trunk
Comment 5•24 years ago
|
||
Confirmed - Win2k 2001050204-Trunk - Nuke my IMAP sent-mail folder and the app
hangs on the next send.
Status: UNCONFIRMED → NEW
Ever confirmed: true
Comment 6•24 years ago
|
||
cc:ing bienvenu. mscott, bienvenu, what's the correct behavior here? Should we
build a new *Sent* folder (not Sent Items, is it?)if the user deletes it (or it
simply isn't there)?
Comment 7•24 years ago
|
||
yes, this is a dup of a bug assigned to racham, and a related bug assigned to me.
*** This bug has been marked as a duplicate of 23625 ***
Status: NEW → RESOLVED
Closed: 24 years ago
Resolution: --- → DUPLICATE
Updated•20 years ago
|
Product: MailNews → Core
Updated•16 years ago
|
Product: Core → MailNews Core
You need to log in
before you can comment on or make changes to this bug.
Description
•