From: David Presotto <presotto@closedmind.org>
To: 9fans@cse.psu.edu
Subject: [9fans] upas
Date: Fri, 26 Sep 2003 11:22:04 -0400 [thread overview]
Message-ID: <383c3f5c0037844b4e8ca2b48f541fcb@plan9.bell-labs.com> (raw)
I changed rfc822.y to not stop parsing when it hits a bad header line. Now it
just tags it as a BadHeader: and continues. This should solve some problems
with reading mime mail that has bad headers. It should also make life a little
easier when filtering spam.
reply other threads:[~2003-09-26 15:22 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=383c3f5c0037844b4e8ca2b48f541fcb@plan9.bell-labs.com \
--to=presotto@closedmind.org \
--cc=9fans@cse.psu.edu \
/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).