Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:114109 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 96319 invoked from network); 23 Apr 2021 13:45:19 -0000 Received: from unknown (HELO php-smtp4.php.net) (45.112.84.5) by pb1.pair.com with SMTP; 23 Apr 2021 13:45:19 -0000 Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id 90A961804D8 for ; Fri, 23 Apr 2021 06:48:33 -0700 (PDT) X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on php-smtp4.php.net X-Spam-Level: X-Spam-Status: No, score=-2.4 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,FREEMAIL_ENVFROM_END_DIGIT,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW, RCVD_IN_MSPIKE_H2,SPF_HELO_NONE,SPF_PASS autolearn=no autolearn_force=no version=3.4.2 X-Spam-Virus: No X-Envelope-From: Received: from mout.gmx.net (mout.gmx.net [212.227.17.21]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by php-smtp4.php.net (Postfix) with ESMTPS for ; Fri, 23 Apr 2021 06:48:32 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=gmx.net; s=badeba3b8450; t=1619185710; bh=6Xw8AMew77Lajjm7rk+j+6NtFA352+a0yDOdDJyzm/I=; h=X-UI-Sender-Class:To:From:Subject:Date; b=WHEzSnuv8eUWrbZ7df6s4Uo+4qONzNy0Gf02czi/0BXuLB3XVH5A4mvG4GWSc0LMU LRNPL1+XMFlBzECj5eagMpSNTmP3dqGsz7iJvUCVRNxeff+qWkeKQHVO2GUX4o2XMY alfRBKjnGWW+nXrjQqJljmrG5laIT50t1I7vHLNQ= X-UI-Sender-Class: 01bb95c1-4bf8-414a-932a-4f6e2808ef9c Received: from [192.168.2.130] ([84.179.250.112]) by mail.gmx.net (mrgmx104 [212.227.17.168]) with ESMTPSA (Nemesis) id 1MowGU-1lGaFE2vOQ-00qSv7 for ; Fri, 23 Apr 2021 15:48:30 +0200 To: PHP internals Message-ID: Date: Fri, 23 Apr 2021 15:48:30 +0200 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.10.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Language: de-DE Content-Transfer-Encoding: quoted-printable X-Provags-ID: V03:K1:qJ9V7J45SOj/rs+6Jc8XWe5Xp2dfXpLXi8W+ze8z2ETo6tV7ydF hgogAdDISaOA4n5eEJe9XfGOAJUvF7px8wZhZD7eGtXQJNBlDwi4G9rj9aZQiSeT9JbI1V4 Or5/rg8SJgjx2dLteHDAP8a/IY3yzgU0wW0F4+v0HhzQ96CFEU7RfiB81cb23fejfDxXUNe U2hIp3bysrrn0XSVKmAxg== X-UI-Out-Filterresults: notjunk:1;V03:K0:4l/TwpoZPWI=:4fEbaFcXSgbmOIYtFa6FOL YDqS94pU/UqXeGvZzvrcOSU6DQWvhrPUR8BXQ+5jCK2Qr031CO4D7JVn4qAIcRSAu11WMQdpa n5BOe0VXJmqTFEs0ll1pzG6vMbpdWpNMjEJaIvixGKHpjWUI2G/lQik4olt00yxAPKvUyW/st EkSEKLUyGwmrviLfk4onMju2HF7eqRXv9g9/C3j0qkY7/65V1fUboNA6uL1vjAb5Lsxxjlo0u y605T6QFiyA9QsCZXmgE9+6+dMlqmjueflO3iKXwpYrJXr4E9zOI1eVfwEi1V3V+Btu7q5NQJ /nSMLx+xBDM/io30GH1I+c42Yek6LX+gndfujro598i2yIKg8l4qxugOpdg22o3pd4xVT4kLO AiR3vT+odPTshzcBJHffxthspU1f4aB6S92DV9LPM1IoAU5THirhEn9R5oJ4HIx19/5qBpCo7 Atms1QDuhaE7qjrQDGQNfRb2t/r1QutjSa5gqgOMSpxODyzGhG7N/rVnpLQHeH2o+YzlPTAe2 OBpuWvs/jcNj0aidkJMsCg5IPhP+HTfmgbqlQchpggqnvJgMi9ESLrypvLfYUnzulyTRcTEGR TQj7H1wuSNcJm1Xfk0tdUXohQl+VDy37z43LJeJS9CODFmlNKg/PzTjX+KuxJcQz21gRfvlpu ysk5LFX7s5mLIzz2d0wzctbbGa+F6/ehQlKdcziURJsF1oErrK8klPuwu9Jjv5CU8vYDCLehh ErB/AwT5exHCLy/prmNSHMYsDkD8CRvjjlpJ5zWZeIbEyEMo5UpkV1sa9l+WyRmx+Lm8vZqFr 5O2jw4SaeIX8a1OSsdSRQNf4i76tZ3+YUgMDl7STumDxZSiRFZyaylwUoX3BA8RbB7P3D7FUz LdgdvCbHpMIm7SOlPbAi9NU2T2IRVw3ZVGPh2e3SJO5oBUexhQD2/fDpsWqhHGfPSONSCgGmZ 8X18ZmoR8U74ycbLw9cU6q6pl46YszqxHEzV1QQUeaAU91VGTErj/LxmkC7UWM4NyhcPqymGC IO2AxHTNpsI93yYbB0IXWRtD06mR8gGnMF7xMWto5sPZDOVKA/OTTeEwWoiegif8JPsKGekw7 XkS9Rultz75DxLFd5K0j+HUuDm+I6PZsQM40pMlY2EIAbNw1Xi3DQHyLQU635n4oFTz2zKGWB 9jZmFktO49DOhQfD2v/I7jIOunzekiRgnhrKq2WHaPMPEsMgQUISfAnJr3cbUBrGmEgvA= Subject: Case folding with following whitespace in MIME headers From: cmbecker69@gmx.de ("Christoph M. Becker") Hi all, while working on a fix[1] for bug #80259[2], I noticed that iconv_mime_decode() and mb_decode_mimeheader() collapse all whitespace after a case folding marker (CRLF) to a single space[3]. This appears to be in violation of RFC 5322, section 2.2.3: | Unfolding is accomplished by simply removing any CRLF | that is immediately followed by WSP. imap_utf8() properly keeps the whitespace. (ext/imap is not available on 3v4l.org) I wonder whether it's worth to fix it, due to the obvious BC break, or whether we want to treat that as a documentation issue. If we're going for a fix (what I would suggest), which version should that target? [1] [2] [3] =2D- Christoph M. Becker