Postfix Overview - Introduction - SCN Research

BOUNCE(8)
BOUNCE(8)
Page 1 of 2
NAME
bounce - Postfix message bounce or defer daemon
SYNOPSIS
bounce
[generic Postfix daemon options]
DESCRIPTION
The bounce daemon maintains per-message log files with
non-delivery status information. Each log file is named
after the queue file that it corresponds to, and is kept
in a queue subdirectory named after the service name in
the master.cf file (either bounce or defer). This program
expects to be run from the master(8) process manager.
The bounce
daemon processes two types of service requests:
o
o
Append a recipient status record to a per-message
log file.
Post a bounce message, with a copy of a log file
and of the corresponding message. When the bounce
is posted successfully, the log file is deleted.
The software does a best effort to notify the sender that
there was a problem. A notification is sent even when the
log file or original message cannot be read.
Optionally, a client can request that the per-message log
file be deleted when the requested operation fails. This
is used by clients that cannot retry transactions by themselves,
and that depend on retry logic in their own
client.
STANDARDS
RFC 822 (ARPA Internet Text Messages)
RFC 1894 (Delivery Status Notifications)
DIAGNOSTICS
Problems and transactions are logged to syslogd(8).
BUGS
The log files use an ad-hoc, unstructured format. This
will have to change in order to easily support standard
delivery status notifications.
CONFIGURATION PARAMETERS
The following main.cf parameters are especially relevant
to this program. See the Postfix main.cf file for syntax
details and for default values. Use the postfix reload
command after a configuration change.
bounce_notice_recipient
The recipient of single bounce postmaster notices.
2bounce_notice_recipient
The recipient of double bounce postmaster notices.
delay_notice_recipient
The recipient of "delayed mail" postmaster notices.
bounce_size_limit
http://www.porcupine.org/postfix-mirror/defer.8.html
6/26/01