Closed Bug 197798 Opened 22 years ago Closed 22 years ago

IMAP: "Copying message to Sent folder" hangs after sending the message

Categories

(MailNews Core :: Backend, defect)

x86
Linux
defect
Not set
major

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 123063

People

(Reporter: german, Assigned: mscott)

Details

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2.1) Gecko/20021130
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.3) Gecko/20030312

While working with IMAP, after sending a message, on the stage of copying it
into "Sent" folder on the server, MailNews hang. It is possible to press
"Cancel", however when attemting to send the message again the sintuation
repeats. When attempting to close the window and choose "Save the message to
Drafts" - MailNews hangs too. So the only choice to quit is to close the
Composer choosing "Don't save" the message. The message is delivered to the
recipient but is not saved in sender's folders.

The same email configuation works just fine in 1.2.1.



Reproducible: Always

Steps to Reproduce:
Setup an IMAP server email account. Setup the MailNews so that it should store
the copies of sent messages on the server, in "Sent" folder.

IMAP server is UW. SSL is on.

Choose "Compose", then write a message and send it. It is sent fine via smtp,
but the stage of message's copying to imap server fails.

1.2.1 worked fine under the same circumstances.
Actual Results:  
The mail is delivered to the recipient but is not saved in sender's folders.
User has to interrupt copying the message to "Sent" folder manually. 

This does not lead to loss of data (sent email) but is VERY inconvenient
(because you have to save it explicitly, in some unobvious ways).

Expected Results:  
The message should be copied to "Sent".
I can confirm this. It's true.

*** This bug has been marked as a duplicate of 123063 ***
Status: UNCONFIRMED → RESOLVED
Closed: 22 years ago
Resolution: --- → DUPLICATE
Product: MailNews → Core
Product: Core → MailNews Core
You need to log in before you can comment on or make changes to this bug.