From nobody Thu Jun 23 03:01:18 2022 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 C3D9787C4E4; Thu, 23 Jun 2022 03:02:00 +0000 (UTC) (envelope-from grog@lemis.com) Received: from smtp03.aussiebb.com.au (smtp03.aussiebb.com.au [121.200.0.94]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4LT4m83Nzjz3NrG; Thu, 23 Jun 2022 03:02:00 +0000 (UTC) (envelope-from grog@lemis.com) Received: from localhost (localhost [127.0.0.1]) by smtp03.aussiebb.com.au (Postfix) with ESMTP id 7667B1A004D; Thu, 23 Jun 2022 13:01:23 +1000 (AEST) X-Virus-Scanned: Debian amavisd-new at smtp03.aussiebb.com.au Received: from smtp03.aussiebb.com.au ([127.0.0.1]) by localhost (smtp03.aussiebb.com.au [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NDW_Ur8mcglH; Thu, 23 Jun 2022 13:01:23 +1000 (AEST) Received: by smtp03.aussiebb.com.au (Postfix, from userid 119) id 6660A1A002B; Thu, 23 Jun 2022 13:01:23 +1000 (AEST) X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on smtp03.aussiebb.com.au X-Spam-Level: * X-Spam-Status: No, score=1.4 required=10.0 tests=KHOP_HELO_FCRDNS,RDNS_DYNAMIC, SPF_HELO_NONE autolearn=disabled version=3.4.4 Received: from eureka.lemis.com (121-200-11-253.79c80b.mel.nbn.aussiebb.net [121.200.11.253]) by smtp03.aussiebb.com.au (Postfix) with ESMTP id 1ACEB1A003E; Thu, 23 Jun 2022 13:01:19 +1000 (AEST) Received: by eureka.lemis.com (Postfix, from userid 1004) id B4C452635BD; Thu, 23 Jun 2022 13:01:18 +1000 (AEST) Date: Thu, 23 Jun 2022 13:01:18 +1000 From: Greg 'groggy' Lehey To: grarpamp Cc: freebsd-doc@freebsd.org, postmaster@freebsd.org, freebsd-current@freebsd.org, freebsd-questions@freebsd.org Subject: Re: Posting Netiquette [ref: Threads "look definitely like" unreadable mess. Handbook project.] Message-ID: <20220623030118.GA59423@eureka.lemis.com> References: 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: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="17pEHd4RhPHOinZp" Content-Disposition: inline In-Reply-To: Organization: The FreeBSD Project Phone: +61-3-5309-0418 Mobile: +61-490-494-038. Use only as instructed. WWW-Home-Page: https://www.FreeBSD X-PGP-Fingerprint: 9A1B 8202 BCCE B846 F92F 09AC 22E6 F290 507A 4223 User-Agent: Mutt/1.6.1 (2016-04-27) X-Rspamd-Queue-Id: 4LT4m83Nzjz3NrG X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; none X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[] X-ThisMailContainsUnwantedMimeParts: N --17pEHd4RhPHOinZp Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wednesday, 22 June 2022 at 15:41:39 -0400, grarpamp wrote: > Around 6/2x/22, Many rammed their horribly formed > msgs upon others to parse: > ... > FreeBSD needs to add an entire section on the > email post formatting netiquette to the Handbook, > and link it on the List Subscription pages, and in the List Welcome > emails, and even in quarterly automated administrivia post to all lists. In fact we have guidelines, just not exactly where you might expect. "How to get Best Results from the FreeBSD-questions Mailing List" (https://docs.freebsd.org/en/articles/freebsd-questions/) contains: Unless there is a good reason to do otherwise, reply to the sender and to FreeBSD-questions. Include relevant text from the original message. Trim it to the minimum, but do not overdo it. It should still be possible for somebody who did not read the original message to understand what you are talking about. Use some technique to identify which text came from the original message, and which text you add. I personally find that prepending =E2=80=9C>=E2=80=9D to the original message works best. Leaving white spa= ce after the =E2=80=9C> ;=E2=80=9D and leave empty lines between your text and the= original text both make the result more readable. Put your response in the correct place (after the text to which it replies). It is very difficult to read a thread of responses where each reply comes before the text to which it replies. Most mailers change the subject line on a reply by prepending a text such as "Re: ". If your mailer does not do it automatically, you should do it manually. If the submitter did not abide by format conventions (lines too long, inappropriate subject line) please fix it. In the case of an incorrect subject line (such as "HELP!!??"), change the subject line to (say) "Re: Difficulties with sync PPP (was: HELP!!??)". That way other people trying to follow the thread will have less difficulty following it. In such cases, it is appropriate to say what you did and why you did it, but try not to be rude. If you find you can not answer without being rude, do not answer. Arguably these recommendations should be separated out into their own page. Re-reading them, I see that there is no explicit line length recommendation. That should be included. And yes, I agree entirely with your concerns, though without my core hat. Greg -- Sent from my desktop computer. See complete headers for address and phone numbers. This message is digitally signed. If your Microsoft mail program reports problems, please read http://lemis.com/broken-MUA.php --17pEHd4RhPHOinZp Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iEYEARECAAYFAmKz134ACgkQIubykFB6QiOK1gCghWwLqEXUMbKR8WI5abC7wR0Q NdYAn2+u90RsgdBRD4ukeQsyiI+qNKWo =i2Fs -----END PGP SIGNATURE----- --17pEHd4RhPHOinZp--