adamengst
June 19, 2019, 4:50pm
1
Some time ago there was a discussion of threading being broken in Apple Mail.
Yes, sigh, I know, again.
1.7 breaks the workaround we had for Mac Mail threading, namely always including “Re:” at the start of the subject
Setting for email subject Re: [%{site_name}] %{optional_pm}%{topic_title}
Unfortunately, Discourse 1.7 sensibly does not include an “In-Reply-To” on the first post, and this results in the first post being threaded separately from the replies in Mac Mail.
I have a hack to put the “In-Reply-To” back:
@message.header['Message-ID'] = incoming_mes…
One of my users just reported this as having changed on our site, since we switched recently from SendGrid to Amazon SES.
In both Mail.app and iOS Mail (latest versions), the first message in a topic (like a TidBITS article) and the replies to that topic are separate threads. Looking at the list messages I haven’t deleted, a topic started May 28 is a single thread...
Reading time: 1 mins 🕑
Likes: 1 ❤
A topic-starting message from 5/31, when threading still worked contains this:
Message-ID: <topic/8883@talk.tidbits.com>
While my message starting this topic has this:
Message-ID: <0100016b6b37a230-92ef9d2a-ded7-43f2-b9a8-e5b9e574cf2e-000000@email.amazonses.com>
which doesn’t match the Message-ID references found in these headers in your reply:
In-Reply-To: <topic/9031@talk.tidbits.com>
References: <topic/9031@talk.tidbits.com>
My guess this is the problem. I think all the replies remain threaded because they all contain matching References. Topic-starting messages don’t contain a References header. If Amazon SES can avoid replacing Message-IDs or if Discourse can include a self-referential References header in topic-starting messages, the problem could go away.
I think this is a problem in Mail because it tries to be an old-school (proper) mail agent, using headers like this for threading, while Gmail is “dumb” and just uses the Subject.
It would seem that the problem is related to the Message-ID header being different. It doesn’t seem that it’s possible to override Message-ID on SES:
Message-ID ( Note: Amazon SES overrides any Message-ID header you provide.)
Any other thoughts about how I might be able to get threading to work for my users relying on Apple Mail (which is most of them)?
@peternlewis . are you still having issues here? What email service are you sending through?
1 Like
I believe Amazon SES messes with mail headers as I recall, in a particularly invasive way.
Ah yes I see you found that as well.
I use my own mail server (which has its own problems, but messing with the heads is not one of them).
adamengst
June 20, 2019, 4:10pm
4
Good to know. And using your own email server is enabling the threads to be maintained in Mail?
We’ve also noticed that breaking some messages out into a new topic runs into the same problem in Mail—the new topic continues to be threaded with the old one. We’re not sure why that’s happening yet.
Yes.
Mail threading is a bizarre black box, so “works most of the time” seems to be as good as it gets.
1 Like