Closed Bug 1852428 Opened 2 years ago Closed 2 years ago

Messages in outbox not shown as unread (by default) in Thunderbird 115.2.0

Categories

(Thunderbird :: Folder and Message Lists, defect)

Thunderbird 115
defect

Tracking

(thunderbird_esr115 fixed, thunderbird121 fixed, thunderbird122 fixed)

VERIFIED FIXED
122 Branch
Tracking Status
thunderbird_esr115 --- fixed
thunderbird121 --- fixed
thunderbird122 --- fixed

People

(Reporter: bazzaman, Assigned: john)

References

(Regression)

Details

(Keywords: regression)

Attachments

(1 file, 1 obsolete file)

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/116.0.0.0 Safari/537.36

Steps to reproduce:

Compose message and select Send Later.

Actual results:

Message is saved in Outbox but has Read status (and so Outbox folder is not emboldened to signify Outbox message(s) awaiting sending).

Expected results:

When using Send Later (e.g. via CTL+Shift+Enter) or Send Later extension, prior to V115.2.0 Outbox messages were shown as Unread by default (and so it was obvious that there messages awaiting sending as the Outbox folder was emboldened). This no longer happens (i.e. such messages show as read) and so messages in the Outbox can easily be forgotten.

Is this simply a bug that has crept into V115? Or is there a setting (or something accessible via the Config Editor to revert to the previous behaviour?

Thanks

I have also notice this. Confirm with beta. I don't know if the change is intentional

Component: Untriaged → Folder and Message Lists
Flags: needinfo?(geoff)

It's not an intentional change by me. I can't think why or how that would've happened.

Status: UNCONFIRMED → NEW
Ever confirmed: true
Flags: needinfo?(geoff)

Now that Thunderbird 115 is gaining traction I have already two reports from users of my add-on Mail Merge, who would also rather have the old behavior back of (new) messages in the Outbox being shown as unread.

I ran mozregression: Daily 2022-08-28 is showing new messages in the Outbox as unread and Daily 2022-08-29 is showing them as read. Here is the pushlog:
https://hg.mozilla.org/comm-central/pushloghtml?fromchange=1fb0e33d695a0b483ce679a0ae9827ebdd50c0dc&tochange=43de3d1aa4e7e94417f03a1ebd3b22087fa7521d

ALexander, thanks for the RR.

Magnus, is there an obvious culprit?

Flags: needinfo?(mkmelin+mozilla)

I confirm this new and unwanted behaviour.
And ask if it is related to https://bugzilla.mozilla.org/show_bug.cgi?id=1798182?
Thank you for fixing this bug.

Duplicate of this bug: 1798182
Duplicate of this bug: 1859689

Oh, I will try to fix this.

Duplicate of this bug: 1860744
Assignee: nobody → john
Flags: needinfo?(john)

My changes in bug 1646473 aimed at honoring the read, new and marked flags of the newMsgFlags parameter passed into nsMsgLocalMailFolder::CopyFileMessage().

Messages copied into the outbox set the read flag here:
https://searchfox.org/comm-central/rev/b20a8a71f829d3e24257d6072129254ee6682ca3/mailnews/compose/src/nsMsgCopy.cpp#232

Before bug 1646473 landed, that read flag was ignored. So, why is that read flag set there in the first place?

Flags: needinfo?(mkmelin+mozilla)

Yes, the try build works as expected! :-)

@Alexander: If you have the time, could you check if fcc still works as expected, or if they are saved with being unread now (which I think is not desired)

I am not too familiar with "Fcc", because I don't usually use this myself.

However, these are my test results via "Options -> Send a Copy To":

  • In Thunderbird 102 both the outgoing message in the "Outbox" and the copy in the selected folder are "unread".
  • In Thunderbird 115 both the outgoing message in the "Outbox" and the copy in the selected folder are "read".
  • With the try build both the outgoing message in the "Outbox" and the copy in the selected folder are "unread".

The try build restores the behavior of Thunderbird 102. I am undecided whether the copy in the selected folder should be "read" or "unread"; I am leaning towards your opinion that this is probably not desired.

Ok, so my fix is restoring the original behavior, which is needed for the backport-patch. We can discuss a deviation of the original behavior in a different bug, which will not be backported.

It would be great, if more users following this bug could try out my try build and check for undesired consequences of my fix. It looks like it is not causing additional test fails, but it could still affect untested areas.

Thanks everybody for your help and sorry for messing this up in the first place.

Edit: If the fix passes review, it will probably reach Daily mid next week. So testing that would of course also be fine.

Status: NEW → ASSIGNED

(In reply to John Bieling (:TbSync) from comment #12)

Is this try looking good?

Yeah.

Flags: needinfo?(mkmelin+mozilla)
Target Milestone: --- → 121 Branch

Pushed by mkmelin@iki.fi:
https://hg.mozilla.org/comm-central/rev/2f18b128ada7
Do not mark messages created by nsMsgCopy::DoCopy as read. r=mkmelin

Status: ASSIGNED → RESOLVED
Closed: 2 years ago
Resolution: --- → FIXED

I'm now seeing messages in Sent also get set to unread. Should be from this.
Can you reproduce? Maybe we should back out so this doesn't go to beta later today?

Flags: needinfo?(john)

yup, back-out

Flags: needinfo?(john)
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Attachment #9363124 - Attachment is obsolete: true

Pushed by ikey@thunderbird.net:
https://hg.mozilla.org/comm-central/rev/e3f3d81287b6
Properly set MsgFlags before calling nsMsgCopy::DoCopy. r=mkmelin

Status: REOPENED → RESOLVED
Closed: 2 years ago2 years ago
Resolution: --- → FIXED
Target Milestone: 121 Branch → 122 Branch

Comment on attachment 9364541 [details]
Bug 1852428 - Properly set MsgFlags before calling nsMsgCopy::DoCopy. r=mkmelin

[Approval Request Comment]
Regression caused by (bug #): 1646473
User impact if declined: Messages in Outbox are marked as read
Testing completed (on c-c, etc.): Just landed on Daily, but should get time on Beta and get uplifted to ESR very soon
Risk to taking this patch (and alternatives if risky): I do not see a risk.

Attachment #9364541 - Flags: approval-comm-beta?

Comment on attachment 9364541 [details]
Bug 1852428 - Properly set MsgFlags before calling nsMsgCopy::DoCopy. r=mkmelin

[Triage Comment]
Approved for beta

Attachment #9364541 - Flags: approval-comm-beta? → approval-comm-beta+

Daily looks good from my POV.
v.fixed

Status: RESOLVED → VERIFIED

good for 115?

Flags: needinfo?(john)

Comment on attachment 9364541 [details]
Bug 1852428 - Properly set MsgFlags before calling nsMsgCopy::DoCopy. r=mkmelin

[Approval Request Comment]
Regression caused by (bug #): 1646473
User impact if declined: Messages in Outbox are marked as read
Testing completed (on c-c, etc.): Just landed on Daily, but should get time on Beta and get uplifted to ESR very soon
Risk to taking this patch (and alternatives if risky): I do not see a risk. (and alternatives if risky):

Flags: needinfo?(john)
Attachment #9364541 - Flags: approval-comm-esr115?

Comment on attachment 9364541 [details]
Bug 1852428 - Properly set MsgFlags before calling nsMsgCopy::DoCopy. r=mkmelin

[Triage Comment]
Approved for esr115

Attachment #9364541 - Flags: approval-comm-esr115? → approval-comm-esr115+
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: