6.0.0-RC7
6/28/26

[#7103] Add "In-Reply-To" header
Summary Add "In-Reply-To" header
Queue Whups
Queue Version HEAD
Type Enhancement
State Resolved
Priority 1. Low
Owners jan (at) horde (dot) org
Requester selsky (at) columbia (dot) edu
Created 7/23/08 (6549 days ago)
Due
Updated 8/25/08 (6516 days ago)
Assigned
Resolved 8/25/08 (6516 days ago)
Milestone
Patch No

History
02 Jan Schneider Assigned to Jan Schneider
 
532 Jan Schneider State ⇒ Resolved
 
154 Jan Schneider Comment #7
State ⇒ Accepted
Reply to this comment
Interesting idea.
243 Matt Selsky Comment #6 Reply to this comment
Bugzilla uses:



$threadingmarker = "In-Reply-To: <bug-$id-" . $user->id . "$sitespec>"



We could the following:



"In-Reply-To: <bug-$id-" . md5($mail) . "$sitespec>"
328 Jan Schneider Comment #5
State ⇒ Rejected
Reply to this comment
Rejected, until someone comes up with a good implementation idea.
388 Jan Schneider Comment #4 Reply to this comment
Bugzilla adds these two headers:
Yes. But what should that tell us?
01 Matt Selsky Comment #3 Reply to this comment
Bugzilla adds these two headers:



In-Reply-To: <bug-3617-62@https.bugzilla.example.com/>

References: <bug-3617-62@https.bugzilla.example.com/>


189 Jan Schneider Comment #2
State ⇒ Feedback
Reply to this comment
Beside that this is really hard work, because we would have to track 
message ids from notification messages with the comments that 
triggered the notification, this might even render impossible, because 
we send individual messages now to each user, so that we don't have a 
single message id anymore.
295 Matt Selsky Comment #1
State ⇒ New
Patch ⇒ No
Milestone ⇒
Queue ⇒ Whups
Summary ⇒ Add "In-Reply-To" header
Type ⇒ Enhancement
Priority ⇒ 1. Low
Reply to this comment
This will help with threading of bug mail

Saved Queries