From nobody Sun Jun 26 18:59:04 2022 X-Original-To: freebsd-doc@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 9BBF9862240; Sun, 26 Jun 2022 18:59:06 +0000 (UTC) (envelope-from bapt@FreeBSD.org) Received: from smtp.freebsd.org (smtp.freebsd.org [96.47.72.83]) (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-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "smtp.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4LWKs63snXz4jB0; Sun, 26 Jun 2022 18:59:06 +0000 (UTC) (envelope-from bapt@FreeBSD.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1656269946; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=nZ2+yj7amM6DHnr48U2h+Y0OGyg+fP1P9Jq4odkty+Q=; b=AtkquNXoImPoiBRyj3NU6RhRZYoaWn0yMDkTrhOHiKIRS6zxJohHsLqOE6WWRs99qFzCiu jJuQaFLwVZnN6S+tb0msw1po+H5qNVhpQ76OCUUjBAawNTajx/P6nosAsQNLQR+4GFnKBb GX3+0R19E1BqvXBEoe6Ra4FwUJQP697FotaZxGd0InC8YPp2eUatlZ8ylxu4AbmSUSlnEF 8DAxrsgMLeddFOefsfEMiCE3kUWq/ZfdHq7WPYva1VXtHDkLdiNDKHx85PCTYv5qKApPU9 GGhHUh6/sUbJjPOhaKk3zLHVyhivmFwBrmspqFmyo1OHTREoPHXk5Sy9nP0Lag== Received: from aniel.nours.eu (nours.eu [IPv6:2001:41d0:8:3a4d::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) (Authenticated sender: bapt) by smtp.freebsd.org (Postfix) with ESMTPSA id 4EB3485C9; Sun, 26 Jun 2022 18:59:06 +0000 (UTC) (envelope-from bapt@FreeBSD.org) Received: by aniel.nours.eu (Postfix, from userid 1001) id B0ED41605A9; Sun, 26 Jun 2022 20:59:04 +0200 (CEST) Date: Sun, 26 Jun 2022 20:59:04 +0200 From: Baptiste Daroussin To: Warner Losh Cc: Walter Parker , Michael Gmelin , freebsd-doc@freebsd.org, FreeBSD questions , FreeBSD Current Subject: Re: Posting netiquette: HTML, attachments etc. Message-ID: <20220626185904.mqetrczfcubslxzp@aniel.nours.eu> References: <753A27F9-9CEA-4592-A44F-91164917358B@freebsd.org> List-Id: Documentation project List-Archive: https://lists.freebsd.org/archives/freebsd-doc List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-doc@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1656269946; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=nZ2+yj7amM6DHnr48U2h+Y0OGyg+fP1P9Jq4odkty+Q=; b=MN/DXONP6r2BMVEx0nQCWY7wxb98zV/GVHU7NfeGU/Dgvm8nZRZwCU/aZ8a/28sY2vYnOa QRfbu82ofJPTS1l2HT2IuNXeo9oda1eGPVxU1jS7kNAyFTWIddorPW8BQ9L/zA9iNkhXs1 +yn+u4/zV3pkidaUn2htTBzHnRBppv95mIWAswaa/UNdLynIjlsQbKqnmsdjBExKSOdndn TF31JMjM8OsTrsmpLQItQ7cofojOlpDXiUaSv/EOKBgSnrOG8lbNodWXsb90irfIx1kSMq 9LsELEn+zbul9QNc/C43eMxKtlqTvEfZ3MZwfS0QZYpMJVKt3gu/svuqkqM+JQ== ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1656269946; a=rsa-sha256; cv=none; b=qyEWHi8+ccgzdDuG7GD/2yb8/i6MgMH2DIuGcvn5h7CYaJnguHH1dkcidx//XCIyWEMzFa 9Ajrv/AWxBtUpB9YS9GzmdrwRTVRd1DElDnDlAwn2FPmwYFMmOIRwTKzKSjDIHMgUn3227 VAGYGdTvUcJ98aW18nXCU0mZmPjS65r1yPaa4YVJNQiG01/Uh/XiRyv2nZZxlZABY+1ugZ l09XvOXWEsRmAYpe53GBoZE1ZwC0H5KgdS1jMXGiZ477LMbe4h7rMQvsYIgjjqTODDwhtV pTDgiDRa5bIuuO45yBJlVW+zLtBL+e94zEd79sXu5ISjwzsGWSeI0oFnUQksHg== ARC-Authentication-Results: i=1; mx1.freebsd.org; none X-ThisMailContainsUnwantedMimeParts: N On Sun, Jun 26, 2022 at 12:32:41PM -0600, Warner Losh wrote: > On Sun, Jun 26, 2022, 12:20 PM Walter Parker wrote: > > > So, utf-8 is good, posting to multiple lists is bad (but ok when you do > > it), what about the original post? He was asking about HTML. UTF-8 != HTML. > > UTF is a character encoding format. It is supported by most email clients > > and does not require HTML for support. > > > > Html is fine as well. Most modern mail platforms generate it for you, > whether you want them too or not. Most of the advice in appendix c is dated > and doesn't really match what people do on the lists. Phones and web based > Gmail are to large a presence to ignore or have policies against. I stopped > listening to complaints about how Gmail or my phone formatted posts 5 years > ago... and I'm definitely an old school straggler... > > Warner > Note that the mailing list engine will reject html only email, html is fine as long at it is created with text/plain alternative. Note that only the text/plain alternative will be used to construct the archive, and I will not ever work on trying to render properly an html only formatted thing via the archiver, it will require too many escaping and madness to be done safely, I will simply drop the ball to someone else here ;) bapt