CDAC notification email threading is broken

General
1

Starting last week around 2021-12-07T18:00Z, threading of CDAC notification emails is broken, at least in Thunderbird.

Looking for possible changes that could have caused this regression suggests a switch in the notification email Message-ID header composition (and following from that, In-Reply-To and References headers as well).

Example from before (i.e. threading works):

Message-ID: <topic/54055/106474@community.developer.atlassian.com>
In-Reply-To: <topic/54055/106469@community.developer.atlassian.com>
References: <topic/54055@community.developer.atlassian.com>
 <topic/54055/106469@community.developer.atlassian.com>

Example from after (threading broken):

Message-ID: <topic/54055/106605.ec39849322579f08d1fc6a96@community.developer.atlassian.com>
In-Reply-To: <topic/54055/106599.f4569a2f0fb9fdaf66df8949@community.developer.atlassian.com>
References: <topic/54055.98ceb74a213579d18bcaf610@community.developer.atlassian.com>
 <topic/54055/106599.f4569a2f0fb9fdaf66df8949@community.developer.atlassian.com>

Note the hash/uuid like ‘.ec39849322579f08d1fc6a96’ suffixes in the id part before the @ - these suffixes change between different replies to the same message, thus breaking the thread detection.

I have confirmed this to be the case for colleagues as well.

Tracking a lot of CDAC category subscriptions without proper threading in the email client is bordering on unusable - can we get back to consistent, non changing Message-ID headers?

2 Likes
2

Let me raise this with Discourse and see if something shipped recently.

2 Likes
3

The fix was deployed at 21:58:34 UTC, Monday, December 13, 2021.

It will only be applied to posts created after the deployment date.

2 Likes
4

Thanks for the quick action! Sounds promising - not seeing the full effect yet, but this reply might serve as a test case …
(Edited to add: D’oh, insufficient test case for myself, as I do not get notifications for my own posts, but will check with colleague starting next workday in a couple of hours)

1 Like
5

Ok, I can confirm the ‘fix’ having a positive effect in that notification mails do get sorted under their starting topic again. Unfortunately, sub threading within a topic is still broken, as the ‘fix’ only ensures a single, stable References entry for the starting topic, but still uses the weirdly randomized and thus never matching IDs for additional References and In-Reply-To to entries.

Not ideal, but at least halfway usable again - guess I’ll have to file a follow up bug report for this with Discourse.

Thanks again for the quick reaction, much appreciated!

3 Likes
6

Please do! I gave them a heads-up that you were likely to submit something. Let me know when you do and I can link it directly with them.

I think they’d love to hear more about sub threading. They shared the following:

If there is any more context or information they could send through that would be very helpful, I am not quite sure what they mean by “sub threading within a topic” and I will need to experiment a bit to find the issue.

1 Like