Closed Bug 202109 Opened 21 years ago Closed 19 years ago

Composed mail text entered after 'save' produces Error

Categories

(MailNews Core :: Composition, defect)

x86
Windows 2000
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED EXPIRED

People

(Reporter: bvdb, Assigned: bugzilla)

Details

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3) Gecko/20030312
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3) Gecko/20030312

When text has been entered in the compose window and 'save'-d (ctrl-s), the
system reports "a copy has been saved in draft". 
More text is entered to finish the mail and the 'Send' button pressed.
Mozilla then brings the pop-up message:
"The command did not succeed. Mail Server responded: Mailbox does not exist."

Pressing "Ok" closes the compose window, the saved version is really in 'Drafts'
- but the added text ist LOST. 

Reproducible: Always

Steps to Reproduce:
1. compose mail, enter some text
2. File-Save in compose window or ctrl-s
3. add more text
4. press 'Send'
Actual Results:  
The added text was lost.

Expected Results:  
Send the complete text as it was displayed in the compose window. 

ALternatively (but worse): Close the compose window after a 'Save' ( and pop-up
a message that the mail should be re-opened and edited from 'Drafts' ).
Summary: Composed mail text that was enterend after 'save' gets lost → Composed mail text that was entered after 'save' gets lost
Severity: critical → normal
Summary: Composed mail text that was entered after 'save' gets lost → Composed mail text entered after 'save' produces Error
Tested again and found that the mail _is_ sent correctly and copied to 'Sent'.
So the bug is restricted to the Error message being displayed. 
Product: MailNews → Core
This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/
This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → EXPIRED
Product: Core → MailNews Core
You need to log in before you can comment on or make changes to this bug.