28.06.2014 Views

Postfix Overview - Introduction - SCN Research

Postfix Overview - Introduction - SCN Research

Postfix Overview - Introduction - SCN Research

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

<strong>Postfix</strong> Configuration - Resource Controls<br />

Page 1 of 3<br />

<strong>Postfix</strong> Configuration - Resource Controls<br />

Up one level | Basic Configuration | UCE Controls | Rate Controls | Resource Controls | Address Manipulation<br />

<strong>Introduction</strong><br />

The <strong>Postfix</strong> system is designed to run within a finite memory budget. To this end, there are configurable limits<br />

on the size of in-memory objects such as text line fragments, on the number of instances of such objects, and on<br />

the time an operation may take. In addition, strategies are in place for dealing with resource exhaustion. The<br />

idea is to keep running under conditions of stress, without making the problem worse.<br />

• Object size limits<br />

• Object count limits<br />

• Time limits<br />

• Acquiring exclusive file locks<br />

• Error recovery<br />

Object size limits<br />

The first step towards a fixed memory resource budget is to limit the size of each in-memory object. Once the<br />

size of in-memory objects is limited, total memory consumption is limited by limiting the number of object<br />

instances. Simple, no?<br />

line_length_limit (default: 2048 bytes)<br />

How long a line of text can be before it is broken up into pieces. All <strong>Postfix</strong> perimeter programs (SMTP<br />

server, SMTP client, local pickup and local delivery) enforce this line length limit when reading data<br />

from an untrusted source. Long lines are reconstructed upon delivery.<br />

header_size_limit (default: 102400 bytes)<br />

How much text may be carried in a multi-line message header. Header text that does not fit in<br />

$header_size_limit bytes overflows into the message body. This limit is enforced by the cleanup header<br />

rewriting code.<br />

extract_recipient_limit (default: 10240 recipients)<br />

How many recipients <strong>Postfix</strong> will extract from message headers before it gives up. This limits the damage<br />

that a run-away program can do with "sendmail -t".<br />

The following parameters restrict the use of file system storage:<br />

message_size_limit (default: 10240000 bytes)<br />

The maximal size of a <strong>Postfix</strong> queue file, including envelope information (sender, recipient, etc.).<br />

queue_minfree (default: no restriction)<br />

How many bytes of free space are needed in the queue file system. The SMTP server declines inbound<br />

http://www.porcupine.org/postfix-mirror/resource.html<br />

6/26/01

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!