Closed Bug 164881 Opened 22 years ago Closed 22 years ago

Wrong sender chosen after saving news message

Categories

(MailNews Core :: Composition, defect)

x86
Windows 2000
defect
Not set
normal

Tracking

(Not tracked)

VERIFIED DUPLICATE of bug 137701

People

(Reporter: tloehnert, Assigned: bugzilla)

Details

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; de-AT; rv:1.1b) Gecko/20020826
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; de-AT; rv:1.1b) Gecko/20020826

When creating a new news message (either through composing or replying) the
sender is correctly chosen - as definded in the news account settings. If the
message is "send now" or "send later" everything is fine. But if I chose to
"save" the message and then re-open it from the "drafts"-folder it contains the
sender address of the default account (which is in my case a mail-account). If I
correct this, save it again and reopen it, then again the wrong sender is put
in. My only chance now is: open message from "drafts", correct it, and chose
"send now" ore "send later" immediately

Reproducible: Always

Steps to Reproduce:
1. open a subscribed news group, choose an existing message + hit the reply button
2. the sender field contains the correct news-address
2. save the newly created message
3. re-open it from the "drafts" folder

Actual Results:  
the sender field always contains the sender address of the default account -
even if this is not a news account

Expected Results:  
the sender field should contain the sender address defined through the news
account settings (which of course *can* be the default account but normally is not)
A simple search for "draft account" would have brought up bug 137701. Please
search for existing bugs before filing new ones.

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