Bug 123768

Summary: In-Reply-To: header in archive mailto: link is empty.
Product: [Fedora] Fedora Reporter: David Woodhouse <dwmw2>
Component: mailmanAssignee: Tomas Smetana <tsmetana>
Status: CLOSED RAWHIDE QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: rawhideCC: mattdm
Target Milestone: ---Keywords: EasyFix, Patch
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2007-05-09 13:54:32 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 150226, 430469    
Attachments:
Description Flags
Fix none

Description David Woodhouse 2004-05-20 14:44:04 UTC 
Description of problem:
See http://canuck.infradead.org/pipermail/linux-mtd/2004-May/009761.html.

Click on the first link -- the mailto: link. Or allow the mouse to
hover over it in your browser or do whatever else you do to see the
link target.

It's as follows:

mailto:linux-mtd%40lists.infradead.org?Subject=Administivia%20--%20mailing%20list%20server%20changes.&In-Reply-To=

However, the In-Reply-To: header _should_ have contained the
Message-ID of the mail to which you'd be replying. If you look at the
mbox archive at
http://canuck.infradead.org/pipermail/linux-mtd/2004-May.txt it's
clear that the Message-ID is preserved by the archival process. It
seems to be the code which generates the HTML in the archive which is
at fault.

This breaks threading when using the web archive to reply to the list.

Actually, the Subject line should probably also have 'Re: ' prepended
in the mailto: link too, if the subject doesn't already start with 'Re: '.

This is mailman-2.1.4-4
Comment 1 Matthew Miller 2005-04-26 16:03:07 UTC 
Fedora Core 2 is now maintained by the Fedora Legacy project for
security updates only. If this problem is a security issue, please
reopen and reassign to the Fedora Legacy product. If it is not a
security issue and hasn't been resolved in the current FC3 updates or
in the FC4 test release, reopen and change the version to match.
Comment 2 David Woodhouse 2006-10-05 09:11:03 UTC 
I had a fix for this once; I thought I'd sent it to the mailman folks. I'll try
to dig it out.
Comment 3 David Woodhouse 2006-10-05 09:23:17 UTC 
Created attachment 137808 [details]
Fix
Comment 4 David Woodhouse 2006-10-05 10:23:58 UTC 
Patch applied to FC-[45] and devel branches.

Do we need to do anything special for RHEL5 or will it inherit from devel?
Comment 5 Tomas Smetana 2007-05-09 13:54:32 UTC 
Fix is present also in RHEL-5.