Closed Bug 542261 Opened 15 years ago Closed 15 years ago

Recipient column wrongly shows Sender if recipient not specified in template/draft messages

Categories

(Thunderbird :: Folder and Message Lists, defect)

defect
Not set
minor

Tracking

(Not tracked)

VERIFIED DUPLICATE of bug 187798

People

(Reporter: dima, Unassigned)

Details

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2) Gecko/20100115 Firefox/3.6 Build Identifier: If you create a template message and not specify a recipient (the "To:" field), *your* name is shown in Recipient column in Templates folder. Reproducible: Always Steps to Reproduce: 1. Create a new message, and do not fill the "To:" field; 2. Save it as Template; 3. Click on Templates folder to see your saved template message. Actual Results: *Your* (sender) name is shown in Recipient column. Expected Results: Recipient column should be empty. Maybe Sender column should be displayed instead.
Confirmed on Windows Vista (Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.1.7) Gecko/20100111 Lightning/1.0b1 Thunderbird/3.0.1 ThunderBrowse/3.2.8.1 ID:20100111101938). (In reply to comment #0) > Expected Results: > Recipient column should be empty. > Maybe Sender column should be displayed instead. Sender column can be shown, if you like (and Thunderbird will remember that preference for later), but I don't think the sender column should be shown by default, especially not in preference to Recipient.
Status: UNCONFIRMED → NEW
Ever confirmed: true
OS: Windows XP → All
Hardware: x86 → All
Version: unspecified → 3.0
Same bad behaviour for saved draft messages. Core bug 187798, dating back to 2003, that's 7 years ago.
Depends on: 187798
Summary: Sender shown as Recipient if recipient not specified in template message → Recipient column wrongly shows Sender if recipient not specified in template/draft messages
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → DUPLICATE
V.Duplicate
Status: RESOLVED → VERIFIED
No longer depends on: 187798
You need to log in before you can comment on or make changes to this bug.