From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=-2.4 required=5.0 tests=DKIMWL_WL_HIGH,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,RCVD_IN_DNSWL_MED,RCVD_IN_MSPIKE_H3, RCVD_IN_MSPIKE_WL autolearn=ham autolearn_force=no version=3.4.4 Received: (qmail 13821 invoked from network); 19 Dec 2022 17:27:34 -0000 Received: from mx1.math.uh.edu (129.7.128.32) by inbox.vuxu.org with ESMTPUTF8; 19 Dec 2022 17:27:34 -0000 Received: from lists1.math.uh.edu ([129.7.128.208]) by mx1.math.uh.edu with esmtps (TLS1.3) tls TLS_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1p7JvJ-009vIa-8o for ml@inbox.vuxu.org; Mon, 19 Dec 2022 11:27:33 -0600 Received: from lists1.math.uh.edu ([127.0.0.1] helo=lists.math.uh.edu) by lists1.math.uh.edu with smtp (Exim 4.96) (envelope-from ) id 1p7JvI-004Z8M-2q for ml@inbox.vuxu.org; Mon, 19 Dec 2022 11:27:32 -0600 Received: from mx2.math.uh.edu ([129.7.128.33]) by lists1.math.uh.edu with esmtp (Exim 4.96) (envelope-from ) id 1p7JvF-004Z8F-1J for ding@lists.math.uh.edu; Mon, 19 Dec 2022 11:27:29 -0600 Received: from quimby.gnus.org ([95.216.78.240]) by mx2.math.uh.edu with esmtps (TLS1.3) tls TLS_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1p7JvB-007daH-Hw for ding@lists.math.uh.edu; Mon, 19 Dec 2022 11:27:29 -0600 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnus.org; s=20200322; h=Content-Transfer-Encoding:Content-Type:MIME-Version:Message-ID :In-Reply-To:Date:References:Subject:Cc:To:From:Sender:Reply-To:Content-ID: Content-Description:Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc :Resent-Message-ID:List-Id:List-Help:List-Unsubscribe:List-Subscribe: List-Post:List-Owner:List-Archive; bh=KI95RB+vYr6OdQ9oeyWAbPsE6grcqsYevkiZVS2rJRc=; b=IlnkynNSt6G3tk5U78W+sdy+fn /HLkQ2TI97Y2Q9MNOKje+VF64osUvMiZhVCbZtWl/AQgspjm3HqtD68RggmnwhYcvdAYnLcEYv6gv 2hqq+qNa1awktWp5Q15CwtxtoJIMgtEXisUQDXrZHQjQ+dRMfwWab3vZwk0qShXuxJQs=; Received: from us-smtp-delivery-124.mimecast.com ([170.10.133.124]) by quimby.gnus.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1p7Jv3-0004Hp-NC for ding@gnus.org; Mon, 19 Dec 2022 18:27:20 +0100 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1671470835; 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: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=KI95RB+vYr6OdQ9oeyWAbPsE6grcqsYevkiZVS2rJRc=; b=Sh+1D5jiP8RB1WQMpy7cqKwIo6yuBcZz4+w1kTd4/lvI3xncqGsBaZz+pBNQchjdpM7Vcw HHxV8C2CGhRwqVuVLSDCte4jfCAEu7QFiJeS1XUM4yer0ZCv8c3cv16uXia4VzQSZ0znnD N2nM+RnelW1w2kKUKfwh8HWkd7QMQeo= Received: from mimecast-mx02.redhat.com (mx3-rdu2.redhat.com [66.187.233.73]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id us-mta-128-lCkMkmbNPqSqTLFwKvnAbA-1; Mon, 19 Dec 2022 12:27:13 -0500 X-MC-Unique: lCkMkmbNPqSqTLFwKvnAbA-1 Received: from smtp.corp.redhat.com (int-mx06.intmail.prod.int.rdu2.redhat.com [10.11.54.6]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx02.redhat.com (Postfix) with ESMTPS id EFDA21C02D3C; Mon, 19 Dec 2022 17:27:12 +0000 (UTC) Received: from oldenburg.str.redhat.com (unknown [10.2.16.17]) by smtp.corp.redhat.com (Postfix) with ESMTPS id B97EB2166B26; Mon, 19 Dec 2022 17:27:11 +0000 (UTC) From: Florian Weimer To: Eli Zaretskii Cc: larsi@gnus.org, eric@ericabrahamsen.net, emacs-devel@gnu.org, ding@gnus.org Subject: Re: master ef14acf: Make nnml handle invalid non-ASCII headers more consistently References: <20210122180801.14756.84264@vcs0.savannah.gnu.org> <20210122180802.F0A1E20A10@vcs0.savannah.gnu.org> <874jtvq8c2.fsf@oldenburg.str.redhat.com> <83k02qiicb.fsf@gnu.org> <87bko26ptd.fsf@oldenburg.str.redhat.com> <83r0wygh9b.fsf@gnu.org> <87k02nze8a.fsf@oldenburg.str.redhat.com> <83zgbjcoeq.fsf@gnu.org> Date: Mon, 19 Dec 2022 18:27:09 +0100 In-Reply-To: <83zgbjcoeq.fsf@gnu.org> (Eli Zaretskii's message of "Mon, 19 Dec 2022 19:07:57 +0200") Message-ID: <87k02nxq1e.fsf@oldenburg.str.redhat.com> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/28.1 (gnu/linux) MIME-Version: 1.0 X-Scanned-By: MIMEDefang 3.1 on 10.11.54.6 X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable List-ID: Precedence: bulk * Eli Zaretskii: >> As I expected, I could reproduce the issue with new mail. I'm happy to >> report that replacing nnml--encode-headers with your new version fixes >> the issue. > > Thanks, so I've now installed this on the emacs-29 branch, for the > upcoming Emacs 29.1. It's a denial-of-service issue, so it should be backported to 28 if possible, too. >> Going back to older mail, I see that previously the From: header was >> written in encoded form to .overview (slightly wrapped to avoid SMTP >> issues): >>=20 >> 8523 Re: [PATCH 1/7] Rename 'hello2.spec.' -> 'hello2.spec' 'hello3.spec= .' -> 'hello3.spec' =3D?utf-8?b?572X5YuH5YiaKFlvbmdnYW5nIEx1bykgdmlhIEVsZnV= 0aWxzLWRldmVs?=3D Thu, 24 Nov 2022 16:27:56= +0800 >> <20220920084307.1696-1-luoyonggang@gmail.com> <20220920084307.1696-2-l= uoyonggang@gmail.com> <20221019194930.GC24703@r= edhat.com> <3bf19d05c8976411432709fae1cc2bcc2d21d700.camel@klomp.org> >> <586fbfd512763e539f0d06e8ffa308da34be5368.camel@wildebeest.org> 705 32= Xref: oldenburg.str.redhat.com lists.sourceware.elfutils-devel:8523 Cc: "F= rank Ch. Eigler" , elfutils-devel@sourceware.org To: Mark = Wielaard >>=20 >> Now it uses unencoded form: >>=20 >> 8762 Re: [PATCH v2 13/16] lib: isatty is not available on windows =E7=BD= =97=E5=8B=87=E5=88=9A(Yonggang Luo) via Elfutils-devel Mon, 19 Dec 2022 20:32:48 +0800 <20221217165213.152-1-luoyonggang@gma= il.com> >> <20221217165213.152-14-luoyonggang@gmail.com> 1074 43 Xref: oldenburg.= str.redhat.com lists.sourceware.elfutils-devel:8762 To: elfutils-devel@sour= ceware.org > > Is that a problem? I think this was part of the reason for that > change in nnml.el. I don't know. >> I assume that there is some protection in place that tabs are not >> possible here? > > Tabs where, and what kind of protection are we talking about? The .overview file is in tab-separated-values format, and I think the code is supposed to replace tabs with spaces before the lines are written. But mail-encode-encoded-word-string/rfc2047-encode-string generally does not replace tabs, so your change shouldn't make things worse at least. Thanks, Florian