Changed subject is not visible any where

Bug Reports
, ,
#1

Description

Consider that in my Mailspring, I am logged in with abc@mailspring.com. There is another email id, gmail@gmail.com. I do not use mailspring for gmail@gmail.com.

  1. Now gmail@gmail.com sent an email to abc@mailspring.com.
  2. abc@mailspring.com replied back.
  3. gmail@gmail.com replied back on the same thread but changed the subject
  4. abc@mailspring.com replied back on the last email and again changed the subject.

In the above case mentioned, even if gmail@gmail.com changed the subject, Mailspring is showing the email in the same thread. There is no place where i can see the changed subject of the email. On the top, you only show the subject of the first email.

Lot of time, certain information is only mentioned within the subject

Screenshots

2880×1800 259 KB

Setup

  • OS and Version: MacOS v10.13.4
  • Mailspring Version: 1.2.1

Additional Context

If you solve this issue, #894, you will eventually solve this issue.

Gmail has thread level subject, but subject of each email is also accessible. In Mailspring, we there is no way to see email level subject line.

screen shot 2018-06-28 at 2 53 31 pm

(Originally posted by patelom on GitHub.)

#2

There is some application state inconsistency here also. If mailspring is running as the emails arrive, the subject will match first email. If mailspring wasn’t running, then syncs a new thread, mailspring will use the subject of the last email in the thread. The subject chosen persists between app restarts, but can differ between clients on different machines based on if the client was running when the emails arrived.

Side note: I missed an important email yesterday related to this behavior. The thread title of the original email was a generic error email sent to several people automatically (which we get a fair amount of). When my boss replied to me on that email thread telling me to look into it, the title never changed to RE: ... and the sender just changed from errorbot@domain.com to errorbot@mydomain.com, Chri....

(Originally posted by deckar01 on GitHub.)

#3

I started working on the issue here: