Re: A question on how much of my list messaging is considered inappropriate content for the lists I post to?

From: Mark Millard <marklmi_at_yahoo.com>
Date: Sun, 04 Jan 2026 20:14:10 UTC
On 1/4/26 11:53, Mark Millard wrote:
> On 1/4/26 07:02, Anton Shepelev wrote:
>> Tomoaki AOKI:
>>
>>> Another thing I can mention is "broken threads".  Replying as
>>> top post makes traking things harder.
>>>
>>> I assume it could be because Mark is receiving ML posts as
>>> summary.  Or copy&pasting from web ML archives like I do for
>>> dev-commits-* MLs.
>>
>> Can we ask Mark to please reconsider his posting habits and to
>> reply to the correct individual messages, offering our help with
>> configuring his software to facilitate correct threading?
>>
>> I have used three approaches:
>>
>> 1. Set up a server-side filter rule that puts all messages to
>>     and from a mailing list into a dedicated IMAP directory.
>>     That way, threading is preserved, the messages are out of the
>>     way of my main INBOX, and digest mode is not required, so
>>     that I can review individual messages and reply to them as
>>     needed.  I was using Gmail filters, but they may be set up
>>     with other e-mail providers, and even locally (procmail,
>>     Sylpheed filter rules, &c).
>>
>> 2. Locate the individual message in the archive, take the
>>     Message-ID: header form it, and append it to the References:
>>     header of my reply.  Good clients will you do that.
>>
>> 3. Use Gmane for both reading and posting (as I am doing now).
>>
>>
>>
> 
> This is a test of using gmane.os.freebsd.current from macOS
> thunderbird. Use of news.gmane.io looks to be a great
> suggestion for me.
> 
> Took me a bit to identify its use of NNTP and to track down
> getting such set up in something (thunderbird). We will see
> if this goes through when I send.
> 
> 
> I did not notice dev-commits-src-main or dev-commits-src-branches
> or dev-commits-ports-main as available. So my occasional
> replies to commit notices would not be made this way.
> 
> 
> Added later:
> 
> Hmm. 2nd try (after an adjustment to a setting).
> Hmm. 3rd try (after quitting and launching thunderbird
>                and answering the application crash dialog
>                after the launch).
> Hmm. 4th try (after an adjustment to a setting).
> 


-- 
===
Mark Millard
marklmi at yahoo.com