diff options
| author | Dirk-Jan C. Binnema <djcb@djcbsoftware.nl> | 2020-02-26 19:31:24 +0200 |
|---|---|---|
| committer | Dirk-Jan C. Binnema <djcb@djcbsoftware.nl> | 2020-02-26 19:31:24 +0200 |
| commit | 07e4a28deb1ebdc2c8629a786099bbe1466dabfb (patch) | |
| tree | 08f922f54fe5202e7f41ccc3ec187267dfb4ac81 /man | |
| parent | 3fe437985f679c8c5bc5cb72836d1e3c014b6162 (diff) | |
man: remove max-msg-size from index man-page
We still keep in the code, as there are some future plans to handle it
there in a different way.
Fixes #1591.
Diffstat (limited to 'man')
| -rw-r--r-- | man/mu-index.1 | 9 |
1 files changed, 0 insertions, 9 deletions
diff --git a/man/mu-index.1 b/man/mu-index.1 index a8a7a80..5760edc 100644 --- a/man/mu-index.1 +++ b/man/mu-index.1 @@ -87,15 +87,6 @@ indexing only a part of messages (using \fB\-\-maildir\fR). For this reason, it is necessary to run \fBmu index \-\-rebuild\fR when there is an upgrade in the database format. \fBmu index\fR will issue a warning about this. -.TP -\fB\-\-max-msg-size\fR=\fI<max msg size>\fR -set the maximum size (in bytes) for messages. The default maximum -(currently at 500Mb) should be enough in most cases, but if you -encounter warnings from \fBmu\fR about ignoring messsage because they -are too big, you may want to increase this. Note that the reason for -having a maximum size is that big messages require big memory -allocations, which may lead to problems. - .B NOTE: It is not recommended to mix maildirs and sub-maildirs within the hierarchy in the same database; for example, it's better not to index both with |