STEPS TO REPRODUCE 1. Reply to a message. 2. Click Send. > A dialog appears (this is probably server-dependent and doesn't always occur even on my server, although it is quite frequent): The current command did not succeed. The mail server responded: Command unrecognised: UID SEARCH 3. Click OK. > Another dialog appears: The message was sent, do you want to return to the compose window? 4. Click OK. 5. Click Save (saves to draft not sent but whatever). 6. Close the window. > Yet another dialog: Message has not been Sent. Do you want to save the message in the Drafts Folder? The bug is: The message has already been sent, so the dialog is incorrect. That dialog should only appear if the message has been modified since it was sent.

don't you usually get the message sent notification if mozilla can't write the file copy?

Note to self: Ok, so this bug is for when you _return to the compose window_ after having Sent a mail.

timeless: you mean the > after step 3? Yes, oddly enough, as I mentioned...

I have a slight variation on this problem on Mac OS X 10.1.2 2002011008. I have fcc set to save sent mail to a "Sent" folder in my IMAP account. The message is sent successfully, but when Mozilla tries to save the message to the Sent folder I get the "UID SEARCH" dialog described above. I then get a dialog saying that sending of the message succeeded but the message could not be saved to the Sent folder. However, going to the Sent folder shows that the fcc did succeed. This problem did not occur with 20020107 build.

Sorry, my comment applies to bug 119154.

hixie please note that in the other bugs you filed your step 3 had the correct error message, in this bug you didn't write it verbatim (or even close).

...which is fine since this bug has nothing to do with that error message...

I am not able to reproduce this problem. Reporter, as you still seeing it using a recent build?

I think so. If a mail fails to copy to my Sent folder (which happens on a regular basis for me although I can't work out why) then when I close the message I seem to remember it says it hasn't been sent. I'll check this next time I hit the problem.

still see this problem in a current release or trunk build?

RESO INCO per lack of response to last question. If you feel this change was made in error, please respond to the bug with your reasons why.