From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 83E4F3858426; Tue, 1 Nov 2022 10:04:05 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 83E4F3858426 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1667297045; bh=t6T8T4u+Lt17BDTf2gv6RNrl2c8SRUcQ2Ql0uowGAhw=; h=From:To:Subject:Date:In-Reply-To:References:From; b=vQh2Wu1JAyEx295bI4xbeMT7eHzupc6iluwVDuUnm32PpAr2TdFtFhIf5or/9Ekez ZCjfih42Snnb3XlBBqY5ovb2LCqmvCaRv8JIZJJBQAvKxsHzv22o4VZwU8Bh8S1NE7 eVAclJyvXEhm2j0YGTPGEbmYqRp7Yg7Gno/ySWcU= From: "mark at klomp dot org" To: overseers@sourceware.org Subject: =?UTF-8?B?W0J1ZyBJbmZyYXN0cnVjdHVyZS8yOTcxM10gUGxlYXNlIG1ha2Ug?= =?UTF-8?B?bGliYy1hbHBoYSBtYWlsaW5nIGxpc3QgY29tcGF0aWJsZSB3aXRoIOKAnGdp?= =?UTF-8?B?dCBhbeKAnQ==?= Date: Tue, 01 Nov 2022 10:04:02 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: sourceware X-Bugzilla-Component: Infrastructure X-Bugzilla-Version: unspecified X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: mark at klomp dot org X-Bugzilla-Status: WAITING X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: overseers at sourceware dot org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://sourceware.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 List-Id: https://sourceware.org/bugzilla/show_bug.cgi?id=3D29713 --- Comment #20 from Mark Wielaard --- (In reply to joseph@codesourcery.com from comment #19) > On Mon, 31 Oct 2022, mark at klomp dot org via Overseers wrote: >=20 > > It would be good if there was a way to reject emails containing text/ht= ml. >=20 > At least for some lists, accepting them is deliberate, to avoid losing=20 > contributions by placing requirement on email formatting that are=20 > problematic for many users nowadays. Sad, but true. So if we want to accept them and keep DKIM signatures correct then we'll need to turn off content filtering, because stripping text/html parts or turning them into plain text will alter the message body. > > Also public-inbox won't archive them (which is already a problem,=20 > > because inbox sees the messages before the text/html part is stripped). >=20 > That's clearly a bug in our public-inbox configuration. Since we're=20 > deliberate accepting text/html we should set up our archiving to handle=20 > messages using it. Lets open a separate bug for that. This is a design choice of public-inbox: To discourage phishing, trackers, exploits and other nuisances, only plain-text emails are allowed and HTML is rejected by default. This improves accessibility, and saves bandwidth and storage as mail is archived forever. We have other archives of course, the messages are in the mailman archives,= but it would be good to see what we can do for the public-inbox archives. Will discuss with the upstream project. --=20 You are receiving this mail because: You are the assignee for the bug.=