Message-Id from the page source
Besides downloading the month archives as mentioned at https://webapps.stackexchange.com/a/23198/51862 you can also find the
Message-Id by inspecting the page source.
At the top of every message page, e.g. http://lists.busybox.net/pipermail/buildroot/2018-March/214868.html there is a
mailto: link that shows as:
Ciro Santilli ciro.santilli at gmail.com
If you just click on it on Chromium 64, Ubuntu 17.10, it does not work: Thunderbird opens up, without the
In-Reply-To. Same behaviour for all combinations of Firefox 58 and setting gmail as my email handler that I've tried.
However, if you open the page source, or use the Inspect browser feature (Ctrl + Shift + I), we can see that the full link is actually:
and so the
In-Reply-To is actually there but URL encoded! We can then use a decoder such as: https://urldecode.org or CLI tools which gives us the correct
Manually set the
In-Reply-To header to the
Message-Id we found
Once we have the message ID, we now need to find a client that allows us to set it.
Methods that I've tested on my gmail account:
I could not find a good method for the following clients:
The RFC itself mentions that
mailto links https://www.rfc-editor.org/rfc/rfc1738 :
An interesting use of your mailto URL is when browsing archives of messages. Each browsed message might contain a mailto URL like:
and it is great that GNU Mailman devs took advantage of it,
but I wonder which component is not working properly to make this just work.
Confusingly, the same RFC also says:
4. Unsafe headers
The user agent interpreting a mailto URL SHOULD choose not to create
a message if any of the headers are considered dangerous; it may also
choose to create a message with only a subset of the headers given in
the URL. Only the Subject, Keywords, and Body headers are believed
to be both safe and useful.
The creator of a mailto URL cannot expect the resolver of a URL to
understand more than the "subject" and "body" headers. Clients that
resolve mailto URLs into mail messages should be able to correctly
create RFC 822-compliant mail messages using the "subject" and "body"
so maybe that's why many clients don't support it?
See also: https://stackoverflow.com/questions/4782068/can-i-set-subject-content-of-email-using-mailto/41365892#41365892
The next thing you will want to know is how to apply patch sets other people have sent to test them locally: https://stackoverflow.com/questions/5062389/getting-started-with-git-am Spoiler: it is a pain / undoable as well.