Fix on branch db/8132 To test, you can generate some emails via the web interface. Then use `telnet` to send an email into allura's smtp listener, see https://forge-allura.apache.org/p/allura/wiki/Notes/ for details. For the email, have a missing or bogus `In-Reply-To:` header, and include a `References:` header with valid values (taken from the `References` and `Message-ID` values in a notification email)
--- ** [tickets:#8132] Fix comment threading when email In-Reply-To header isn't useful** **Status:** in-progress **Milestone:** unreleased **Created:** Tue Oct 04, 2016 06:31 PM UTC by Dave Brondsema **Last Updated:** Tue Oct 04, 2016 06:31 PM UTC **Owner:** Dave Brondsema Normally when replying to a thread, the `In-Reply-To` header is set to something like `</p/allura/tickets/7873/6e5421b0a3201b41f8a729d67ef7b13384bf309a.tick...@allura.p.forge-allura.apache.org>` and then that is used to insert the message in the right part of the thread. However, sometimes that header has just a "regular" message id like `caftne1nm2mfg3o2wtq_bdwurjmspneicw-d_uiwbsat3aly...@mail.gmail.com` and then it creates a whole new thread. One case when this can happen is if you reply to your own message, then your mail client will use your sent mail's ID instead of the notification mail ID. We should be able to use the `References` header sitll though. E.g. `References: <553179ed6d19cd11b75b56ce.tick...@allura.p.forge-allura.apache.org> </p/allura/tickets/7873/8f4bbc80b155474daf34173d16045ec9d148877c.tick...@allura.p.forge-allura.apache.org> </p/allura/tickets/7873/6e5421b0a3201b41f8a729d67ef7b13384bf309a.tick...@allura.p.forge-allura.apache.org>` --- Sent from forge-allura.apache.org because dev@allura.apache.org is subscribed to https://forge-allura.apache.org/p/allura/tickets/ To unsubscribe from further messages, a project admin can change settings at https://forge-allura.apache.org/p/allura/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.
