Welcome to Linux Knowledge Base and Tutorial
"The place where you learn linux"
Linux Magazine - Missing Anything?

 Create an AccountHome | Submit News | Your Account  

Tutorial Menu
Linux Tutorial Home
Table of Contents

· Introduction to Operating Systems
· Linux Basics
· Working with the System
· Shells and Utilities
· Editing Files
· Basic Administration
· The Operating System
· The X Windowing System
· The Computer Itself
· Networking
· System Monitoring
· Solving Problems
· Security
· Installing and Upgrading
· Linux and Windows

Man Pages
Linux Topics
Test Your Knowledge

Site Menu
Site Map
Copyright Info
Terms of Use
Privacy Info
Masthead / Impressum
Your Account

Private Messages

News Archive
Submit News
User Articles
Web Links


The Web

Who's Online
There are currently, 64 guest(s) and 0 member(s) that are online.

You are an Anonymous user. You can register for free by clicking here




       bounce [generic Postfix daemon options]


       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:

             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 them
       selves,  and  that  depend  on  retry  logic  in their own


       RFC 822 (ARPA Internet Text Messages)
       RFC 1894 (Delivery Status Notifications)
       RFC 2045 (Format of Internet Message Bodies)


       Problems and transactions are logged to syslogd(8).


       The log files use an  ad-hoc,  unstructured  format.  This
       will  have  to  change in order to easily support standard
       delivery status notifications.


       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.

              The  recipient of single bounce postmaster notices.

              Notify the postmaster of  bounced  mail  when  this
              parameter  includes  the  bounce class. For privacy
              reasons, the message body is not included.


       master(8) process manager
       qmgr(8) queue manager
       syslogd(8) system logging


       The Secure Mailer license must be  distributed  with  this


       Wietse Venema
       IBM T.J. Watson Research
       P.O. Box 704
       Yorktown Heights, NY 10598, USA

Show your Support for the Linux Tutorial

Purchase one of the products from our new online shop. For each product you purchase, the Linux Tutorial gets a portion of the proceeds to help keep us going.



Security Code
Security Code
Type Security Code

Don't have an account yet? You can create one. As a registered user you have some advantages like theme manager, comments configuration and post comments with your name.

Help if you can!

Amazon Wish List

Did You Know?
You can get all the latest Site and Linux news by checking out our news page.


Tell a Friend About Us

Bookmark and Share

Web site powered by PHP-Nuke

Is this information useful? At the very least you can help by spreading the word to your favorite newsgroups, mailing lists and forums.
All logos and trademarks in this site are property of their respective owner. The comments are property of their posters. Articles are the property of their respective owners. Unless otherwise stated in the body of the article, article content (C) 1994-2013 by James Mohr. All rights reserved. The stylized page/paper, as well as the terms "The Linux Tutorial", "The Linux Server Tutorial", "The Linux Knowledge Base and Tutorial" and "The place where you learn Linux" are service marks of James Mohr. All rights reserved.
The Linux Knowledge Base and Tutorial may contain links to sites on the Internet, which are owned and operated by third parties. The Linux Tutorial is not responsible for the content of any such third-party site. By viewing/utilizing this web site, you have agreed to our disclaimer, terms of use and privacy policy. Use of automated download software ("harvesters") such as wget, httrack, etc. causes the site to quickly exceed its bandwidth limitation and are therefore expressly prohibited. For more details on this, take a look here

PHP-Nuke Copyright © 2004 by Francisco Burzi. This is free software, and you may redistribute it under the GPL. PHP-Nuke comes with absolutely no warranty, for details, see the license.
Page Generation: 0.09 Seconds