9front - general discussion about 9front
 help / color / mirror / Atom feed
From: theinicke@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 08:27:27 +0200	[thread overview]
Message-ID: <85974F541E859AF65CD882E57D735703@bss-wf.de> (raw)
In-Reply-To: <94E808D19B9A5E6B039FDEF2737B325A@eigenstate.org>

Hi,

thanks for your reply. Concerning your question: This should not be a problem, at least if I have read the rfc correctly. We are getting white space in front of split lines for free, because in rfc2822 it says that the line breaks may only be inserted in front of white space. The relevant part is in section 2.2.3.

--
Tobias Heinicke



  reply	other threads:[~2020-09-10  6:27 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-09 19:33 theinicke
2020-09-09 19:50 ` [9front] " ori
2020-09-10  6:27   ` theinicke [this message]
2020-09-10 19:58     ` theinicke
2020-09-10 21:12       ` ori
2020-09-11 21:08         ` theinicke
2020-09-12 21:19           ` theinicke
2020-09-12 22:58           ` ori
2020-09-14 21:49             ` theinicke
2020-09-17 23:01               ` ori

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=85974F541E859AF65CD882E57D735703@bss-wf.de \
    --to=theinicke@bss-wf.de \
    --cc=9front@9front.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).