user/dev discussion of public-inbox itself
 help / color / mirror / code / Atom feed
From: Eric Wong <>
Subject: [PATCH 0/2] header limit and consistency
Date: Sun, 10 May 2020 06:21:03 +0000	[thread overview]
Message-ID: <> (raw)

We take most of these limits from postfix, so be consistent with
the corresponding option names used by postfix in our internal

Limiting header scanning serves the same purpose as the new
`--max-size' option for -index (and the default matches

Eric Wong (2):
  eml: enforce a maximum header length
  eml: rename limits to match postfix names

 lib/PublicInbox/ | 41 +++++++++++++++++++++++++++++++++--------
 t/eml.t                | 29 +++++++++++++++++++++++++++--
 2 files changed, 60 insertions(+), 10 deletions(-)

             reply	other threads:[~2020-05-10  6:21 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-10  6:21 Eric Wong [this message]
2020-05-10  6:21 ` [PATCH 1/2] eml: enforce a maximum header length Eric Wong
2020-05-10  6:21 ` [PATCH 2/2] eml: rename limits to match postfix names Eric Wong

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:

  List information:

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

  git send-email \ \ \ \

* 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.
Code repositories for project(s) associated with this public inbox

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 read-only IMAP folder(s) and NNTP newsgroup(s).