alx/mu4e
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

mu: Change default max msg size to 500 Mb

Browse Source 
Seems people are getting really big mails these days, so let's up the
default (which is also what mu4e uses) to 500 Mb (which should be enough
for everyone, always)
This commit is contained in:
djcb
2016-03-13 16:41:09 +02:00
parent 1505da640d
commit 68f5dc3973
2 changed files with 10 additions and 7 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
lib/mu-index.c
View File

@ -37,7 +37,9 @@
#include "mu-util.h"
#define MU_LAST_USED_MAILDIR_KEY "last_used_maildir"
#define MU_INDEX_MAX_FILE_SIZE (50*1000*1000) /* 50 Mb */
#define MU_INDEX_MAX_FILE_SIZE (500*1000*1000) /* 500 Mb */
/* apparently, people are getting really big mails, so let us index those (by
* default)*/
struct _MuIndex {
MuStore *_store;

13
man/mu-index.1
View File

@ -105,12 +105,13 @@ size to (for example) 1000, which will reduce memory consumption, but also
substantially reduce the indexing performance.
.TP
\fB\-\-max-msg-size\fR=\fI<max msg size>\fR
set the maximum size (in bytes) for messages. The default maximum (currently
at 50Mb) 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.
\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