From: ori@eigenstate.org
To: theinicke@bss-wf.de, 9front@9front.org
Subject: Re: [9front] [Bug] [PATCH] Mail cannot cope with multi-line header fields
Date: Thu, 17 Sep 2020 16:01:20 -0700 [thread overview]
Message-ID: <4E408C698AD9B024668C36E92F594FBC@eigenstate.org> (raw)
In-Reply-To: <FEB70CF14BD53F79E2C893F3AE4542D0@bss-wf.de>
>> I think I like your idea of doing it in copy822. How's this?
>
> This is fine except for the potential corner case of having CRLF inside a quoted string in one of the header fields treated by addr822.
>
> That is in rfc2855 it says in section 3.2.5 "Since a quoted-string is allowed to contain FWS, folding is permitted.". If we want to follow this path of fixing it here, then I think we also would have to at least amend the condition in /sys/src/cmd/upas/fs/mbox.c:763 (776 after applying your patch).
Looks good -- committing.
Thanks!
prev parent reply other threads:[~2020-09-17 23:01 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
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 [this message]
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=4E408C698AD9B024668C36E92F594FBC@eigenstate.org \
--to=ori@eigenstate.org \
--cc=9front@9front.org \
--cc=theinicke@bss-wf.de \
/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).