From nobody Sun Jan 4 15:02:09 2026 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4dkh1w6pkkz6MQdM for ; Sun, 04 Jan 2026 15:20:04 +0000 (UTC) (envelope-from freebsd-current@m.gmane-mx.org) Received: from ciao.gmane.io (ciao.gmane.io [116.202.254.214]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (prime256v1) server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4dkh1w3P5Xz3dS2 for ; Sun, 04 Jan 2026 15:20:04 +0000 (UTC) (envelope-from freebsd-current@m.gmane-mx.org) Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=fail reason="SPF not aligned (relaxed), No valid DKIM" header.from=gmail.com (policy=none); spf=pass (mx1.freebsd.org: domain of freebsd-current@m.gmane-mx.org designates 116.202.254.214 as permitted sender) smtp.mailfrom=freebsd-current@m.gmane-mx.org Received: from list by ciao.gmane.io with local (Exim 4.92) (envelope-from ) id 1vcPth-0000Ca-U6 for freebsd-current@freebsd.org; Sun, 04 Jan 2026 16:20:01 +0100 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-current@freebsd.org From: Anton Shepelev Subject: Re: A question on how much of my list messaging is considered inappropriate content for the lists I post to? Date: Sun, 4 Jan 2026 18:02:09 +0300 Message-ID: <20260104180209.585347eb16ad8caf84c43e44@gmail.com> References: <7d2a8e91-c78b-4207-a4ab-41056333bdd5@gmail.com> <20260101182647.83e09e83e81605690b1ff0fc@dec.sakura.ne.jp> List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@FreeBSD.org Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Newsreader: Sylpheed 3.7.0 (GTK+ 2.24.30; i686-pc-mingw32) X-Spamd-Bar: + X-Spamd-Result: default: False [1.90 / 15.00]; SUBJECT_ENDS_QUESTION(1.00)[]; NEURAL_SPAM_MEDIUM(0.97)[0.972]; NEURAL_HAM_LONG(-0.77)[-0.767]; MV_CASE(0.50)[]; FORGED_SENDER(0.30)[antontxt@gmail.com,freebsd-current@m.gmane-mx.org]; R_SPF_ALLOW(-0.20)[+mx:c]; ONCE_RECEIVED(0.20)[]; NEURAL_HAM_SHORT(-0.10)[-0.104]; MIME_GOOD(-0.10)[text/plain]; DMARC_POLICY_SOFTFAIL(0.10)[gmail.com : SPF not aligned (relaxed), No valid DKIM,none]; RCVD_TLS_LAST(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; FREEMAIL_FROM(0.00)[gmail.com]; ARC_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; TAGGED_FROM(0.00)[]; ASN(0.00)[asn:24940, ipnet:116.202.0.0/16, country:DE]; RCVD_COUNT_ONE(0.00)[1]; TO_DN_NONE(0.00)[]; FROM_NEQ_ENVFROM(0.00)[antontxt@gmail.com,freebsd-current@m.gmane-mx.org]; MISSING_XM_UA(0.00)[]; MLMMJ_DEST(0.00)[freebsd-current@freebsd.org]; MID_RHS_MATCH_FROM(0.00)[]; R_DKIM_NA(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; FROM_HAS_DN(0.00)[] X-Rspamd-Queue-Id: 4dkh1w3P5Xz3dS2 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).