Hello, my Hyperkitty is creating a new post for each reply in a thread. I would expect that new posts to a list would show up in the archive and once you click on that thread you would see all replies. However in my Hyperkitty each reply to a thread shows up as its own post usually with the subject line saying RE: Original Message. How can I set up Hyperkitty to behave more like the lists.mailman3.org archives where replies to topics are filed under their respective threads?
Thank you, Paul 'Arte Chambers' Robey 502-408-6922
Arte Chambers via Mailman-users writes:
Hello, my Hyperkitty is creating a new post for each reply in a thread. I would expect that new posts to a list would show up in the archive and once you click on that thread you would see all replies.
This is the default behavior if I understand what you are saying correctly. Here is a typical thread for this list: https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/A... Here is the list of threads: https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/ There's also a recent threads view: https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/latest
Are those different from what you expect?
However in my Hyperkitty each reply to a thread shows up as its own post usually with the subject line saying RE: Original Message. How can I set up Hyperkitty to behave more like the lists.mailman3.org archives where replies to topics are filed under their respective threads?
As far as I know, threading is not configurable in HyperKitty; to inhibit it you would have to patch the code.
The only thing I can think of that would cause the behavior you describe is if the Message=ID or In-Reply-To and References headers are corrupt or missing from the replies. If you use certain services to send mail (AWS SES for example), Message-ID corruption may be imposed on your subscribers for the convenience of the provider.
The traditional algorithm (as entertainingly described by Jamie Zawinski in https://www.jwz.org/doc/threading.html and somewhat less entertainingly in https://datatracker.ietf.org/doc/html/rfc5256 by Marc Crispin et al) does consider the Subject field and order by date within subjects in the absence of reference information as a crude approximation to true threading, but I don't know if HyperKitty uses Subject information.
Steve
I am using an SMTP relay on my server. The relay provider is Brevo formally Send In Blue. I am wondering how I can verify weather message id or in-reply-to headers are being modified.
Thank you, Paul 'Arte Chambers' Robey 502-408-6922
On Wed, Mar 5, 2025 at 12:00 PM Stephen J. Turnbull < turnbull@sk.tsukuba.ac.jp> wrote:
Arte Chambers via Mailman-users writes:
Hello, my Hyperkitty is creating a new post for each reply in a thread. I would expect that new posts to a list would show up in the archive and once you click on that thread you would see all replies.
This is the default behavior if I understand what you are saying correctly. Here is a typical thread for this list:
https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/A... Here is the list of threads: https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/ There's also a recent threads view: https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/latest
Are those different from what you expect?
However in my Hyperkitty each reply to a thread shows up as its own post usually with the subject line saying RE: Original Message. How can I set up Hyperkitty to behave more like the lists.mailman3.org archives where replies to topics are filed under their respective threads?
As far as I know, threading is not configurable in HyperKitty; to inhibit it you would have to patch the code.
The only thing I can think of that would cause the behavior you describe is if the Message=ID or In-Reply-To and References headers are corrupt or missing from the replies. If you use certain services to send mail (AWS SES for example), Message-ID corruption may be imposed on your subscribers for the convenience of the provider.
The traditional algorithm (as entertainingly described by Jamie Zawinski in https://www.jwz.org/doc/threading.html and somewhat less entertainingly in https://datatracker.ietf.org/doc/html/rfc5256 by Marc Crispin et al) does consider the Subject field and order by date within subjects in the absence of reference information as a crude approximation to true threading, but I don't know if HyperKitty uses Subject information.
Steve
Arte Chambers via Mailman-users writes:
I am using an SMTP relay on my server. The relay provider is Brevo formally Send In Blue. I am wondering how I can verify weather message id or in-reply-to headers are being modified.
Most mail clients provide a "raw" or "original" or "source" message feature, often on some combination of modifiers with the "u" key. You'll be able to see it there. Many servers add *a lot* of "stuff", use the search feature to find "In-Reply-To:" and "References:".
I don't know of a way to get that information from HyperKitty itself. I think you can download an archive of the whole archive for a list from the threads view, and then get the individual posts from that in some way.
On 3/5/25 8:55 PM, Arte Chambers via Mailman-users wrote:
Hello, my Hyperkitty is creating a new post for each reply in a thread. I would expect that new posts to a list would show up in the archive and once you click on that thread you would see all replies. However in my Hyperkitty each reply to a thread shows up as its own post usually with the subject line saying RE: Original Message. How can I set up Hyperkitty to behave more like the lists.mailman3.org archives where replies to topics are filed under their respective threads?
HyperKitty's threading is based solely on In-Reply-To: headers. It does not attempt to thread based on References: or Subject: matching.
Usually this works, but it can fail if for example A posts to a list. B replies off list to A and A replies on list to B's off list reply. In this case, the In-Reply-To: of A's reply is the Message-ID: of B's reply which isn't on the archive, so A's reply starts a new thread, but this is unusual, and HyperKitty has a "Reattach this thread" feature that a list owner or superuser can use to attach one thread to another.
However, if this non-threading occurs regularly, It may be that the replyer's MUA is not setting In-Reply-To:. I've seen some phone clients do this.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
participants (3)
-
Arte Chambers -
Mark Sapiro -
Stephen J. Turnbull