From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from outgoing.selfhost.de ([82.98.87.70]) by ewsd; Thu Sep 10 15:58:44 EDT 2020 Received: (qmail 3926 invoked from network); 10 Sep 2020 19:58:23 -0000 Received: from unknown (HELO mx03.bss-wf.de) (postmaster@emdtgvmf.mail.selfhost.de@84.150.42.130) by mailout.selfhost.de with ESMTPA; 10 Sep 2020 19:58:23 -0000 Received: by mx03.bss-wf.de (Postfix, from userid 1000) id 8856C3DD7C; Thu, 10 Sep 2020 21:58:23 +0200 (CEST) X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on mx03 X-Spam-Level: X-Spam-Status: No, score=-1.0 required=5.0 tests=ALL_TRUSTED autolearn=ham autolearn_force=no version=3.4.2 Received: from 9pi.pala (p5b3bc91e.dip0.t-ipconnect.de [91.59.201.30]) by mx03.bss-wf.de (Postfix) with ESMTPSA id E8C1B3DD7A for <9front@9front.org>; Thu, 10 Sep 2020 21:58:22 +0200 (CEST) Message-ID: <1E9189D603E4A86EC6969A0C7524340A@bss-wf.de> To: 9front@9front.org Subject: Re: [9front] [Bug] [PATCH] Mail cannot cope with multi-line header fields Date: Thu, 10 Sep 2020 21:58:21 +0200 From: theinicke@bss-wf.de In-Reply-To: <85974F541E859AF65CD882E57D735703@bss-wf.de> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit List-ID: <9front.9front.org> List-Help: X-Glyph: ➈ X-Bullshit: private reduce/map control Maybe we should just get rid of the line breaks altogether (either at info file generation or possibly even before), because this would probably honor the following part of rfc2822 (this is identical in the newest rfc5322): > Each header field should be treated in its unfolded form for further syntactic and semantic evaluation. -- Tobias Heinicke