Closed Bug 67267 Opened 23 years ago Closed 22 years ago
Sent/Unsent/Drafts should not be saved as Read Items
From Bugzilla Helper: User-Agent: Mozilla/4.73 [en] (WinNT; I) BuildID: 2001012404 I think it is good idea to save a draft as unread message into drafts folder. because allmost all other Email softwares follow this behaviour. Similar case with Templates and Sent folders too .. I don't think this behaviour is needd for Unsent Messages folder because every time when user exits the browser or starts the browser an alert will be shown to send unsent Messages. Reproducible: Always Steps to Reproduce: Open New Message composition window do the following 1. File -> save as -> draft 2. File -> save as -> Template 3. File -> send Actual Results: Message should be saved in the respective folders as Unread items Expected Results: Messages are getting saved as Read Items
I get the Unknown error in Linux on build 2001012706. I will try in Windows tommorow.
Adding jglick and myself to CC.. this sounds like a UI decision
I just checked Eudora and OE and neither of them save Sent messages as unread (the versions I have anyway). Webmail apps seem to more commonly save sent messages as unread though. I'm not really sure what the benefit of doing this is though. Sent, Drafts and Templates really aren't "Unread" since you are the one who generated them.
Seems decent enough and i can confirm it. Marking NEW.
Per bug 127281, marking this WONTFIX. User generated messages, Sent, Unsent and Drafts shouldn't be marked as unread.
Status: NEW → RESOLVED
Closed: 22 years ago
Resolution: --- → WONTFIX
verified invalid. If you compose it, you know the message, so I also see no reason for it being marked unread.
Status: RESOLVED → VERIFIED
*** Bug 188814 has been marked as a duplicate of this bug. ***
*** Bug 240048 has been marked as a duplicate of this bug. ***
*** Bug 198087 has been marked as a duplicate of this bug. ***
I've reopened bug 198087 to address the Unsent/Drafts issue. Put yourself on the CC there if you want to see that happen.
You need to log in before you can comment on or make changes to this bug.