Closed Bug 281154 Opened 20 years ago Closed 20 years ago

"Send copy to" feature fails if message was not saved in drafts previously

Categories

(Thunderbird :: Message Compose Window, defect)

x86
Windows 2000
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: jens.b, Assigned: mscott)

Details

When in the compose window, activating the "Send copy to" on a new mail does
nothing if the message was not previously saved to the drafts folder. Note that
this is different from bug 199571, as I'm not complaining about the lack of
feedback, but about the necessity of saving the message first. That extra step
feels odd to me, and I don't understand why it's technically needed - especially
given the fact that once the "send copy to" feature is activated, sending the
message does save the final version of the mail, and not the one that was saved
earlier.

Reproduce:
1. Open a new mail
2. Click 'send a copy to', choose any folder.
3. Click 'Send'

Expected:
Mail ends up in the chosen folder.

Actual:
Mail ends up in the 'Sent' folder.

[Not sure whether this is front-end or back-end, please move to Core if it's the
latter]
Works for me. Mail pop ups up in both the sent mail and chosen folder. Still
using Thunderbird 0.9 though.
(In reply to comment #1)
> Works for me. Mail pop ups up in both the sent mail and chosen folder. Still
> using Thunderbird 0.9 though.

Works for me too in Thunderbird 1.0

Reproduction steps (which i've taken):

1. Click on the Write button to create a new e-mail
2. Fill in necessary fields and body
3. Clicked the "Send a Copy to" option in "Options"
4. Choose the folder in which the mail is to be saved

Expected: 
A copy of the mail ends up in the folder which was selected

Actual result:
A copy of the mail ends up in the folder which was selected (and the Sent folder
as usual)

Strange - somehow, I'm no longer able to reproduce this myself, either... It
even works without a body or a subject line. Resolving for now; should I find a
way to reproduce it again, I'll reopen this bug.
Status: NEW → RESOLVED
Closed: 20 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.