Okay so I have some information from deep-diving. This is simply a **post ID** not a thread ID.
Is there any way to have Subject based thread tagging, etc.? I ask this only because we're trying to thread items for easy ID in a system right now that does thread ID tagging in the subject line (i.e. "[Test-0000004] Something" and "Re: [Test-0000004] Something" are identified as the same thread, but a brand new message "Something" would end up as "[Test-0000005] Something" in the chain if it was a new message.)
I know this is not following RFC that a Subject field isn't a tagging, and in fact under the hood i'm fine with Hyperkitty keeping the in-reply-to handling, but I need to have the semi-custom "subject" handling.
If this isn't possible out of the box, would it be possible to code this as a custom pipeline or mail handler integration plugin? And additionally, can someone point me in that direction if I have to dive down that rabbit hole?
Thomas
On 10/18/23 17:09, Thomas Ward via Mailman-users wrote:
Trying to use the thread prefix component to *tag* thread IDs in a system, but not increment per message.
It looks like replies are being received and then thread prefixes are getting incremented. "[Test-%07d]" is the prefix I"m using on a given test list, but we want it to increment by thread ID and *not* per message. (6 messages for instance have been sent, two were replies to [Test-0000004] and though the system properly archived it in the same conversation, it still incremented the digit counter).
Is there a way to achieve this in Mailman3 without me having to write some kind of custom code for this?
Thomas
Mailman-users mailing list -- mailman-users@mailman3.org To unsubscribe send an email to mailman-users-leave@mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ Archived at: https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message/...
This message sent to teward@thomas-ward.net