Bug 259083 - Mailing lists subscribers can't reply to the list from archives nor send threading capable mails without manually editing the available links
Summary: Mailing lists subscribers can't reply to the list from archives nor send thre...
Status: New
Alias: None
Product: Services
Classification: Unclassified
Component: Mailing Lists (show other bugs)
Version: unspecified
Hardware: Any Any
: --- Affects Some People
Assignee: postmaster
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-10-11 21:52 UTC by nixdoe
Modified: 2023-07-29 06:01 UTC (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description nixdoe 2021-10-11 21:52:33 UTC
In the switch form mailman to mlmmj, users that use the archive to view the mailing lists and wish to reply to any message have lost the ability to reply to the list without manually change the mailto available links, this is the link where the mail of the poster is converted to a mailto link to join the conversation.

This is because the new mailto defaults to the sender address instead the list mail.

Also, as the mailto URI lacks the In-Reply-To parameter, the mail wouldn't thread in the mailing list, splitting the conversations. To fix that feature an user have to view the original message first, copy the Message-ID header value and then craft a mailto link with an In-Reply-To parameter to call the MUA with the correct headers for the correct functionality of the list.

This affects, specially, those that choose the digest or no-mail subscriptions that use the web to join the conversations.

Happens in all mailto links in the new mlmmj archives.
Comment 1 Philip Paeps freebsd_committer freebsd_triage 2021-10-12 03:07:53 UTC
Which archives did we have that allow you to reply to the list?  As far as I know, both the pipermail mailman archiver and the older archiver also only provide a mailto: link to the poster rather than the list.
Comment 2 nixdoe 2021-10-12 13:44:47 UTC
(In reply to Philip Paeps from comment #1)

Any in pipermail mailman archives have had the mailto for the list.

Example, go to the latest archived under pipermail:

https://lists.freebsd.org/pipermail/freebsd-questions/2021-October/

Open any message, the first one, why bother on any other one for just an example, as all are the same:

https://lists.freebsd.org/pipermail/freebsd-questions/2021-October/294845.html

The mailto:
mailto:freebsd-questions%40freebsd.org?Subject=Re%3A%20expired%20Lets%20Encrypt%20CA%20and%20fetch&In-Reply-To=%3CYVZhD3obEBAl5Gsz%40ceres.zyxst.net%3E

That would open a MUA with the To header for freebsd-questions@freebsd.org (freebsd-questions%40freebsd.org), that is the questions list address; Subject header with the thread subject (?Subject=Re%3A%20expired%20Lets%20Encrypt%20CA%20and%20fetch); In-Reply-To header to instruct the recipients that it is threaded (&In-Reply-To=%3CYVZhD3obEBAl5Gsz%40ceres.zyxst.net%3E).


Go to any pipermail archive for any list and verify it is the same.

If you do the same with the new archives, example with the questions list too...

https://lists.freebsd.org/archives/freebsd-questions/2021-October/

First mail:

https://lists.freebsd.org/archives/freebsd-questions/2021-October/000091.html

Mailto:

mailto:list-freebsd-questions_at_jyborn.se?Subject=Re%3A%20Is%20there%20a%20way%20to%20get%20direct%20execution%20of%20java%20jar%20files%20in%20FreeBSD%3F



Note that this specific user have an address similar to the mailing list but is not.

Any mail in the new archives the To header in the mailto is for the poster/sender (true that in the new list the at sign is replaced by "_at_" too); and the Subject (Subject=Re%3A%20Is%20there%20a%20way%20to%20get%20direct%20execution%20of%20java%20jar%20files%20in%20FreeBSD%3F); but it lacks the In-reply-to, even though, somehow, as it is not for the list... is "less" important, if the recipient doesn't care about threading.

Is reproducible, always.

mailman
https://lists.freebsd.org/pipermail/

mlmmj
https://lists.freebsd.org/archives/