[exim-cvs] Document behaviour of message_size_limit=0 (main …

Top Page
Delete this message
Reply to this message
Author: Exim Git Commits Mailing List
Date:  
To: exim-cvs
Subject: [exim-cvs] Document behaviour of message_size_limit=0 (main config setting, not transport)
Gitweb: http://git.exim.org/exim.git/commitdiff/ac8c9fbdec78f15484599cfaae195f24a6fe4858
Commit:     ac8c9fbdec78f15484599cfaae195f24a6fe4858
Parent:     522f6933d00d2e4b22885bd11fde2b24ef6e8579
Author:     Phil Pennock <pdp@???>
AuthorDate: Sun Sep 4 00:43:15 2011 -0400
Committer:  Phil Pennock <pdp@???>
CommitDate: Sun Sep 4 00:43:15 2011 -0400


    Document behaviour of message_size_limit=0 (main config setting, not transport)
---
 doc/doc-docbook/spec.xfpt |    4 ++++
 1 files changed, 4 insertions(+), 0 deletions(-)


diff --git a/doc/doc-docbook/spec.xfpt b/doc/doc-docbook/spec.xfpt
index b7d8c46..1c3e434 100644
--- a/doc/doc-docbook/spec.xfpt
+++ b/doc/doc-docbook/spec.xfpt
@@ -14169,6 +14169,10 @@ probably safest to just set it to a little larger than this value. Eg, with a
default Exim message size of 50M and a default ClamAV StreamMaxLength of 10M,
some problems may result.

+A value of 0 will disable size limit checking; Exim will still advertise the
+SIZE extension in an EHLO response, but without a limit, so as to permit
+SMTP clients to still indicate the message size along with the MAIL verb.
+

.option move_frozen_messages main boolean false
.cindex "frozen messages" "moving"