From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on dcvr.yhbt.net X-Spam-Level: X-Spam-ASN: AS6830 37.24.128.0/17 X-Spam-Status: No, score=-3.5 required=3.0 tests=AWL,BAYES_00, RCVD_IN_DNSWL_MED,SPF_HELO_NONE,SPF_PASS shortcircuit=no autolearn=ham autolearn_force=no version=3.4.2 Received: from albireo.enyo.de (albireo.enyo.de [37.24.231.21]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by dcvr.yhbt.net (Postfix) with ESMTPS id 54E911F4B5 for ; Tue, 12 Nov 2019 13:37:31 +0000 (UTC) Received: from [172.17.203.2] (helo=deneb.enyo.de) by albireo.enyo.de with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) id 1iUWMM-0007Sj-09 for meta@public-inbox.org; Tue, 12 Nov 2019 13:37:29 +0000 Received: from fw by deneb.enyo.de with local (Exim 4.92) (envelope-from ) id 1iUWML-0002gw-Uc for meta@public-inbox.org; Tue, 12 Nov 2019 14:37:29 +0100 From: Florian Weimer To: meta@public-inbox.org Subject: Archiving HTML mail Date: Tue, 12 Nov 2019 14:37:29 +0100 Message-ID: <87r22ddxly.fsf@mid.deneb.enyo.de> MIME-Version: 1.0 Content-Type: text/plain List-Id: New contributors tend to send text/html. We are currently rejecting such email, which is proving more and more problematic. I think a change would be easier to justify if I can show that this will not break our mailing list archives (in the sense that they become incomplete). We currently use mhonarc, and I don't think it copes well with such mail. It certainly doesn't do the subdomain split. Is it possible to archive such mail as well, possibly under separate subdomains to avoid XSS issues?