On 11/4/21 12:58 PM, Simon Coggins wrote:
Please file an issue for this at https://gitlab.com/mailman/mailman/-/issues<https://gitlab.com/mailman/mailman/-/issues> and I will try to find a better solution. Your approach of munging Message-IDs will create other issues. Consider a post to a list with direct CC to userx. userx replies-all to the message received directly. the In-Reply-To of this reply is the unmunged Message-ID which will affect threading in the archives and other recipient's MUAs. I realize this is preferable to losing the message, but I hope we can do better.
Yeah it’s not a great solution but it’s the quickest I could come up with that works “for us”. 99% of our lists are announcement lists only with minimal replies so while this will break some. I’m hoping it will give us enough time to wait out a proper fix. I’ve created a new issue #955 with as much detail as I think you’ll need. Let me know if you need any more.
Thanks for filing the issue. I'll work on a solution. My current
thinking is to add a count column to the message table, set the count
to 1 when initially adding a message-id, increment the count when adding
an existing message-id, decrement the count when deleting a message-id
and only delete the entry and message when the count reaches 0.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan