Closed Bug 121593 Opened 24 years ago Closed 23 years ago

Subfolders of the Sent folder show the "Recipient" column

Categories

(SeaMonkey :: MailNews: Message Display, defect)

Product:
SeaMonkey
Component:
MailNews: Message Display
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
VERIFIED WORKSFORME

People

(Reporter: ridgway, Assigned: sspitzer)

References

Details

Moving mail that is in the Sent folder to a sub folder of Sent, changes the recipient to the person who sent the email not the person who received the email.
not movemail.
Assignee: adam → sspitzer
Component: Movemail → Mail Window Front End
QA Contact: esther → sheelar
confirming using 2002-01-23-06 on win98.. We show the recipient in the sent folder. Moving a message to any other folder or subfolder changes the recipient and changes to the sender name. I guess that is because we display recipient in sent folder but other folder displays the sender column.
oops! forgot to confirm
Status: UNCONFIRMED → NEW
Ever confirmed: true
*** Bug 123973 has been marked as a duplicate of this bug. ***
This needs to be moved up in the priorities from a business point of view this is a show stopper to moving from Netscape 4.7x. My business needs certain features from Netscape 4.7x to move to Netscape 6.x ( Mozilla ).
I get this problem in Linux as well as Windows 2000.
*** Bug 135418 has been marked as a duplicate of this bug. ***
*** Bug 136353 has been marked as a duplicate of this bug. ***
is this the same issue as in bug 114533?
This effects all OS and Platforms, can the owner change this, this was verified on Bug 123973
OS: Windows 2000 → All
Hardware: PC → All
Verified on Linux (RC2) and Win98 (RC1). Indeed that gives people who work with heavy correspondence a hard time - I agree that it should move up the priority list.
Summary: Moving mail to folders changes recipient → Subfolders of the Sent folder show the "Recipient" column
*** Bug 146718 has been marked as a duplicate of this bug. ***
*** Bug 149143 has been marked as a duplicate of this bug. ***
Nominating since a lot of people want it and since it showed up as a problem in the Beta feedback.
Keywords: nsbeta1
QA Contact: sheelar → huang
marking nsbeta1-
Keywords: nsbeta1 → nsbeta1-
We're getting lots of dups on this one, and it's kind of ironic when you notice that it's a deliberate change - see bug 61651. Seth put this code in almost a year ago. Is this wontfix, or should we revert it? CC bienvenu for opinion.
Here's the whole checkin message, for reference: 1.177 <sspitzer@netscape.com> 01 Aug 2001 20:18 fix for #61651: subfolders of special folders have those special folder properties. thanks to elrod@liquidmetal.com for the initial patch
I thought Seth fixed this on the trunk not too long ago, so that we'd show the sender column and actual sender for sub-folders of the sent folder.
No, but we can change it back to that. It seems to be as easy as reverting his patch to IsSpecialFolder()... Would that be OK?
This bug is critical for entreprise users. Raising severity.
Severity: minor → normal
Per Sheela, this bug should belong to Gregg since scenario is covered from "Send" area.
QA Contact: huang → meehansqa
*** Bug 154613 has been marked as a duplicate of this bug. ***
Bienvenu, what do you think of the fix sketched out in comment 19?
I have no idea - does that work? One very goofy thing I noticed is that doing a quick search based on recipient in a sub-folder of the sent folder actually works, even though we're displaying the sender and not the recipient. So at least some code knows that it's a sub-folder of the sent folder.
*** Bug 159408 has been marked as a duplicate of this bug. ***
nominating for next release -- we get a lot of reports for this.
Keywords: nsbeta1- → nsbeta1
*** Bug 160335 has been marked as a duplicate of this bug. ***
*** Bug 160367 has been marked as a duplicate of this bug. ***
*** Bug 161123 has been marked as a duplicate of this bug. ***
*** Bug 161171 has been marked as a duplicate of this bug. ***
The bug only exist in mozilla1.0(20020530) or before version. And current trunk works well. People who file the duplicated bugs seems are using versions before 1.0.
The bug do not exist in new build.
Status: NEW → RESOLVED
Closed: 23 years ago
Resolution: --- → WORKSFORME
Product: Browser → Seamonkey
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.