98 lines
2.7 KiB
Groff
98 lines
2.7 KiB
Groff
.TH BOUNCE 8
|
|
.ad
|
|
.fi
|
|
.SH NAME
|
|
bounce
|
|
\-
|
|
Postfix message bounce or defer daemon
|
|
.SH SYNOPSIS
|
|
.na
|
|
.nf
|
|
\fBbounce\fR [generic Postfix daemon options]
|
|
.SH DESCRIPTION
|
|
.ad
|
|
.fi
|
|
The \fBbounce\fR 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 \fBmaster.cf\fR file (either
|
|
\fBbounce\fR or \fBdefer\fR).
|
|
This program expects to be run from the \fBmaster\fR(8) process
|
|
manager.
|
|
|
|
The \fBbounce\fR daemon processes two types of service requests:
|
|
.IP \(bu
|
|
Append a recipient status record to a per-message log file.
|
|
.IP \(bu
|
|
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.
|
|
.PP
|
|
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.
|
|
.SH STANDARDS
|
|
.na
|
|
.nf
|
|
RFC 822 (ARPA Internet Text Messages)
|
|
RFC 1894 (Delivery Status Notifications)
|
|
.SH DIAGNOSTICS
|
|
.ad
|
|
.fi
|
|
Problems and transactions are logged to \fBsyslogd\fR(8).
|
|
.SH BUGS
|
|
.ad
|
|
.fi
|
|
The log files use an ad-hoc, unstructured format. This will have
|
|
to change in order to easily support standard delivery status
|
|
notifications.
|
|
.SH CONFIGURATION PARAMETERS
|
|
.na
|
|
.nf
|
|
.ad
|
|
.fi
|
|
The following \fBmain.cf\fR parameters are especially relevant to
|
|
this program. See the Postfix \fBmain.cf\fR file for syntax details
|
|
and for default values. Use the \fBpostfix reload\fR command after
|
|
a configuration change.
|
|
.IP \fBbounce_notice_recipient\fR
|
|
The recipient of single bounce postmaster notices.
|
|
.IP \fB2bounce_notice_recipient\fR
|
|
The recipient of double bounce postmaster notices.
|
|
.IP \fBdelay_notice_recipient\fR
|
|
The recipient of "delayed mail" postmaster notices.
|
|
.IP \fBbounce_size_limit\fR
|
|
Limit the amount of original message context that is sent in
|
|
a non-delivery notification.
|
|
.IP \fBmail_name\fR
|
|
Use this mail system name in the introductory text at the
|
|
start of a bounce message.
|
|
.IP \fBnotify_classes\fR
|
|
Notify the postmaster of bounced mail when this parameter
|
|
includes the \fBbounce\fR class. For privacy reasons, the message
|
|
body is not included.
|
|
.SH SEE ALSO
|
|
.na
|
|
.nf
|
|
master(8) process manager
|
|
qmgr(8) queue manager
|
|
syslogd(8) system logging
|
|
.SH LICENSE
|
|
.na
|
|
.nf
|
|
.ad
|
|
.fi
|
|
The Secure Mailer license must be distributed with this software.
|
|
.SH AUTHOR(S)
|
|
.na
|
|
.nf
|
|
Wietse Venema
|
|
IBM T.J. Watson Research
|
|
P.O. Box 704
|
|
Yorktown Heights, NY 10598, USA
|