Hi all, I'm moving this discussion to gossip because it is of general interest. There are about 1000 uses of The Mail Archive's reply feature every day. Based on David's request, I've put together preliminary support for In-Reply-To to help with threading. You can see it in action with curl and I'm also appending the relevant PHP fragment. I don't think I have it quite right yet, especially with respect to escaping, so suggestions are appreciated. It is a little hard for me to test because my particular email setup (Chrome/Ubuntu/GMail) does not seem to respect this feature at all.
To answer the other question, the reply feature intentionally goes to the sender instead of the list. This seems like a reasonable balance. Specifically, it avoids having messages silently dropped, which is a very common list setting for non-subscribers. Plus a number of list administrators feel more comfortable with private replies, and making the hoi polloi do a little more work in order to contact the entire list. Some admins have been very vocal about this preference. $ curl -s -D - -d 'subject=Re: "challenging" subjectline' -d 'msgid=abc...@mail.gmail.com' -e http://www.mail-archive.com/gossip@jab.org/msg01001.html http://www.mail-archive.com/mailto.php | grep Location Location: mailto:j...@jab.org?Subject=Re%3A%20%5C%22challenging%5C%22%20subjectline&In-Reply-To=%3Cabc123%40mail.gmail.com%3E $subject = $_POST['subject']; $msgid = $_POST['msgid']; $header = "Location: mailto:$name@$domain?"; . "Subject=" . rawurlencode($subject) . "&" . "In-Reply-To=%3C" . rawurlencode($msgid) . "%3E"; === From: David Woodhouse <dw...@infradead.org Date: Sat, Apr 2, 2011 at 9:00 AM To: themailarch...@gmail.com I'm having to deal with broken threading on my mailing list which I think is happening because of users using your mailto: links to reply. If you look at my own list archive at http://lists.infradead.org/pipermail/get_iplayer/2011-March/001193.html you'll see the mailto: link at the top includes '&In-Reply-To=...' so that threading information is correctly preserved. The link is: mailto:get_iplayer%40lists.infradead.org?Subject=Re:%20Re%3A%20Broken%20list%20threads&In-Reply-To=%3CAANLkTi%3DdDPQ3LnN0_G86AXO4gFrX3%3DvqbsDK_40FocHq%40mail.gmail.com%3E"; But your copy of the same message at http://www.mail-archive.com/get_iplayer@lists.infradead.org/msg01077.html ends up with an HTTP redirect to a mailto: URL *without* the correct threading information: mailto:she...@shevek.co.uk?subject=Broken%20list%20threads Please could you fix your mailto: links to include correct threading information? Thanks. I actually have a filter on my mailing lists so that messages with 'Re:' in the subject but no In-Reply-To: or References: headers are trapped for moderation, but these replies bypass that by omitting 'Re:' from the subject line too! Also, you don't seem to give a way to reply to the *list*; only the original sender. I think users who reply using your archive are manually editing the To: header to reply back to the list instead of to the sender? Is that intentional? -- dwmw2 -- To unsubscribe, send mail to gossip-unsubscr...@jab.org.
