1. Manuals
  2. Tumbleweed
  3. postfix
  4. cleanup(8)

Scroll to navigation

CLEANUP(8) System Manager's Manual CLEANUP(8)

NAME

cleanup - canonicalize and enqueue Postfix message

SYNOPSIS

cleanup [generic Postfix daemon options]

DESCRIPTION


The cleanup(8) daemon processes inbound mail, inserts it into the incoming mail queue, and informs the queue manager of its arrival.

The cleanup(8) daemon performs the following transformations:

  • Insert missing message headers: (Resent-) From:, To:, Message-Id:, and Date:.
    This is enabled with the local_header_rewrite_clients and always_add_missing_headers parameter settings.
  • Transform envelope and header addresses to the standard user@fully-qualified-domain form that is expected by other Postfix programs. This task depends on the trivial-rewrite(8) daemon.
    The header transformation is enabled with the local_header_rewrite_clients parameter setting.
  • Eliminate duplicate envelope recipient addresses.
    This is enabled with the duplicate_filter_limit parameter setting.
  • Remove message headers: Bcc, Content-Length, Resent-Bcc, Return-Path.
    This is enabled with the message_drop_headers parameter setting.
  • Optionally, rewrite all envelope and header addresses according to the mappings specified in the canonical(5) lookup tables.
    The header transformation is enabled with the local_header_rewrite_clients parameter setting.
  • Optionally, masquerade envelope sender addresses and message header addresses (i.e. strip host or domain information below all domains listed in the masquerade_domains parameter, except for user names listed in masquerade_exceptions). By default, address masquerading does not affect envelope recipients.
    The header transformation is enabled with the local_header_rewrite_clients parameter setting.
  • Optionally, expand envelope recipients according to information found in the virtual_alias_maps lookup tables.

The cleanup(8) daemon performs sanity checks on the content of each message. When it finds a problem, by default it returns a diagnostic status to the cleanup service client, and leaves it up to the client to deal with the problem. Alternatively, the client can request the cleanup(8) daemon to bounce the message back to the sender in case of trouble.

STANDARDS

RFC 822 (ARPA Internet Text Messages)
RFC 2045 (MIME: Format of Internet Message Bodies)
RFC 2046 (MIME: Media Types)
RFC 2822 (Internet Message Format)
RFC 3463 (Enhanced Status Codes)
RFC 3464 (Delivery status notifications)
RFC 5322 (Internet Message Format)

DIAGNOSTICS


Problems and transactions are logged to syslogd(8) or postlogd(8).

BUGS


Table-driven rewriting rules make it hard to express if then else and other logical relationships.

CONFIGURATION PARAMETERS



Changes to main.cf are picked up automatically, as
    cleanup(8) processes run for only a limited amount of time. Use the
    command "postfix reload" to speed up a change.


The text below provides only a parameter summary. See
    postconf(5) for more details including examples.






COMPATIBILITY CONTROLS





  

  
Message header that the Postfix cleanup(8) server inserts when a
      message contains no To: or Cc: message header.




Available in Postfix version 2.1 only:



  

  
Report mail delivery errors to the address specified with the non-standard
      Errors-To: message header, instead of the envelope sender address (this
      feature is removed with Postfix version 2.2, is turned off by default with
      Postfix version 2.1, and is always turned on with older Postfix
    versions).




Available in Postfix version 2.6 and later:



  

  
Always add (Resent-) From:, To:, Date: or Message-ID: headers when not
      present.




Available in Postfix version 2.9 and later:



  

  
Enable long, non-repeating, queue IDs (queue file names).




Available in Postfix version 3.0 and later:



  

  
Names of message headers that the cleanup(8) daemon will remove
      after applying header_checks(5) and before invoking Milter
      applications.

  

  
The format of the Postfix-generated From: header.








BUILT-IN CONTENT FILTERING CONTROLS




Postfix built-in content filtering is meant to stop a flood of
    worms or viruses. It is not a general content filter.



  

  
Optional lookup tables for content inspection as specified in the
      body_checks(5) manual page.

  

  
Optional lookup tables for content inspection of primary non-MIME message
      headers, as specified in the header_checks(5) manual page.




Available in Postfix version 2.0 and later:



  

  
How much text in a message body segment (or attachment, if you prefer to
      use that term) is subjected to body_checks inspection.

  

  
Optional lookup tables for content inspection of MIME related message
      headers, as described in the header_checks(5) manual page.

  

  
Optional lookup tables for content inspection of non-MIME message headers
      in attached messages, as described in the header_checks(5) manual
      page.




Available in Postfix version 2.3 and later:



  

  
The set of characters that Postfix will reject in message content.

  

  
The set of characters that Postfix will remove from message content.




Available in Postfix version 3.9, 3.8.5, 3.7.10, 3.6.14, 3.5.24,
    and later:



  

  
Replace each stray <CR> or <LF> character in message content
      with a space character, to prevent outbound SMTP smuggling, and to make
      the evaluation of Postfix-added DKIM or other signatures independent from
      how a remote mail server handles such characters.








BEFORE QUEUE MILTER CONTROLS




As of version 2.3, Postfix supports the Sendmail version 8 Milter
    (mail filter) protocol. When mail is not received via the smtpd(8) server,
    the cleanup(8) server will simulate SMTP events to the extent that this is
    possible. For details see the MILTER_README document.



  

  
A list of Milter (mail filter) applications for new mail that does not
      arrive via the Postfix smtpd(8) server.

  

  
The mail filter protocol version and optional protocol extensions for
      communication with a Milter application; prior to Postfix 2.6 the default
      protocol is 2.

  

  
The default action when a Milter (mail filter) response is unavailable
      (for example, bad Postfix configuration or Milter failure).

  

  
The {daemon_name} macro value for Milter (mail filter) applications.

  

  
The {v} macro value for Milter (mail filter) applications.

  

  
The time limit for connecting to a Milter (mail filter) application, and
      for negotiating protocol options.

  

  
The time limit for sending an SMTP command to a Milter (mail filter)
      application, and for receiving the response.

  

  
The time limit for sending message content to a Milter (mail filter)
      application, and for receiving the response.

  

  
The macros that are sent to Milter (mail filter) applications after
      completion of an SMTP connection.

  

  
The macros that are sent to Milter (mail filter) applications after the
      SMTP HELO or EHLO command.

  

  
The macros that are sent to Milter (mail filter) applications after the
      SMTP MAIL FROM command.

  

  
The macros that are sent to Milter (mail filter) applications after the
      SMTP RCPT TO command.

  

  
The macros that are sent to version 4 or higher Milter (mail filter)
      applications after the SMTP DATA command.

  

  
The macros that are sent to version 3 or higher Milter (mail filter)
      applications after an unknown SMTP command.

  

  
The macros that are sent to Milter (mail filter) applications after the
      message end-of-data.




Available in Postfix version 2.5 and later:



  

  
The macros that are sent to Milter (mail filter) applications after the
      end of the message header.




Available in Postfix version 2.7 and later:



  

  
Optional lookup tables for content inspection of message headers that are
      produced by Milter applications.




Available in Postfix version 3.1 and later:



  

  
Optional list of name=value pairs that specify default values for
      arbitrary macros that Postfix may send to Milter applications.








MIME PROCESSING CONTROLS




Available in Postfix version 2.0 and later:



  

  
Turn off MIME processing while receiving mail.

  

  
The maximal length of MIME multipart boundary strings.

  

  
The maximal recursion level that the MIME processor will handle.

  

  
Enable both strict_7bit_headers and strict_8bitmime_body.

  

  
Reject mail with 8-bit text in message headers.

  

  
Reject 8-bit message body text without 8-bit MIME content encoding
      information.

  

  
Reject mail with invalid Content-Transfer-Encoding: information for the
      message/* or multipart/* MIME content types.




Available in Postfix version 2.5 and later:



  

  
Automatically detect 8BITMIME body content by looking at
      Content-Transfer-Encoding: message headers; historically, this behavior
      was hard-coded to be "always on".








AUTOMATIC BCC RECIPIENT CONTROLS




Postfix can automatically add BCC (blind carbon copy) when mail
    enters the mail system:



  

  
Optional address that receives a "blind carbon copy" of each
      message that is received by the Postfix mail system.




Available in Postfix version 2.1 and later:



  

  
Optional BCC (blind carbon-copy) address lookup tables, indexed by
      envelope sender address.

  

  
Optional BCC (blind carbon-copy) address lookup tables, indexed by
      envelope recipient address.








ADDRESS TRANSFORMATION CONTROLS




Address rewriting is delegated to the trivial-rewrite(8)
    daemon. The cleanup(8) server implements table driven address
    mapping.



  

  
The recipient of mail addressed to the null address.

  

  
Optional address mapping lookup tables for message headers and
    envelopes.

  

  
Optional address mapping lookup tables for envelope and header recipient
      addresses.

  

  
Optional address mapping lookup tables for envelope and header sender
      addresses.

  

  
What addresses are subject to address masquerading.

  

  
Optional list of domains whose subdomain structure will be stripped off in
      email addresses.

  

  
Optional list of user names that are not subjected to address
      masquerading, even when their addresses match $masquerade_domains.

  

  
What address lookup tables copy an address extension from the lookup key
      to the lookup result.




Available before Postfix version 2.0:



  

  
Optional lookup tables with a) names of domains for which all addresses
      are aliased to addresses in other local or remote domains, and b)
      addresses that are aliased to addresses in other local or remote
    domains.




Available in Postfix version 2.0 and later:



  

  
Optional lookup tables with aliases that apply to all recipients:
      local(8), virtual, and remote; this is unlike alias_maps that apply
      only to local(8) recipients.




Available in Postfix version 2.2 and later:



  

  
What addresses are subject to canonical_maps address mapping.

  

  
What addresses are subject to recipient_canonical_maps address
    mapping.

  

  
What addresses are subject to sender_canonical_maps address mapping.

  

  
Rewrite or add message headers in mail from remote clients if the
      remote_header_rewrite_domain parameter value is non-empty, updating
      incomplete addresses with the domain specified in the
      remote_header_rewrite_domain parameter, and adding missing headers.








RESOURCE AND RATE CONTROLS





  

  
The maximal number of addresses remembered by the address duplicate filter
      for aliases(5) or virtual(5) alias expansion, or for
      showq(8) queue displays.

  

  
The maximal amount of memory in bytes for storing a message header.

  

  
The maximal number of Received: message headers that is allowed in the
      primary message headers.

  

  
Time to pause before accepting a new message, when the message arrival
      rate exceeds the message delivery rate.

  

  
The maximal size in bytes of a message, including envelope
    information.




Available in Postfix version 2.0 and later:



  

  
The maximal number of address tokens are allowed in an address message
      header.

  

  
The maximal length of MIME multipart boundary strings.

  

  
The maximal recursion level that the MIME processor will handle.

  

  
The maximal number of (name=value) attributes that may be stored in a
      Postfix queue file.




Available in Postfix version 2.1 and later:



  

  
The maximal number of addresses that virtual alias expansion produces from
      each original recipient.

  

  
The maximal nesting depth of virtual alias expansion.




Available in Postfix version 3.0 and later:



  

  
The maximal length of an email address after virtual alias expansion.








SMTPUTF8 CONTROLS




Preliminary SMTPUTF8 support is introduced with Postfix 3.0.



  

  
Enable preliminary SMTPUTF8 support for the protocols described in RFC
      6531, RFC 6532, and RFC 6533.

  

  
Detect that a message requires SMTPUTF8 support for the specified mail
      origin classes.




Available in Postfix version 3.2 and later:



  

  
Enable 'transitional' compatibility between IDNA2003 and IDNA2008, when
      converting UTF-8 domain names to/from the ASCII form that is used for DNS
      lookups.








MISCELLANEOUS CONTROLS





  

  
The default location of the Postfix main.cf and master.cf configuration
      files.

  

  
How much time a Postfix daemon process may take to handle a request before
      it is terminated by a built-in watchdog timer.

  

  
The maximal number of digits after the decimal point when logging
      sub-second delay values.

  

  
The time after which the sender receives a copy of the message headers of
      mail that is still queued.

  

  
The time limit for sending or receiving information over an internal
      communication channel.

  

  
The maximum amount of time that an idle Postfix daemon process waits for
      an incoming connection before terminating voluntarily.

  

  
The maximal number of incoming connections that a Postfix daemon process
      will service before terminating voluntarily.

  

  
The internet hostname of this mail system.

  

  
The domain name that locally-posted mail appears to come from, and that
      locally posted mail is delivered to.

  

  
The process ID of a Postfix command or daemon process.

  

  
The process name of a Postfix command or daemon process.

  

  
The location of the Postfix top-level queue directory.

  

  
Safety net to keep mail queued that would otherwise be returned to the
      sender.

  

  
The syslog facility of Postfix logging.

  

  
A prefix that is prepended to the process name in syslog records, so that,
      for example, "smtpd" becomes "prefix/smtpd".




Available in Postfix version 2.1 and later:



  

  
Enable support for the original recipient address after an address is
      rewritten to a different address (for example with aliasing or with
      canonical mapping).




Available in Postfix 3.3 and later:



  

  
The master.cf service name of a Postfix daemon process.




Available in Postfix 3.5 and later:



  

  
The email address form that will be used in non-debug logging (info,
      warning, etc.).




Available in Postfix 3.9 and later:



  

  
Convert body content that claims to be 8-bit into quoted-printable, before
      header_checks, body_checks, Milters, and before after-queue content
      filters.








FILES


/etc/postfix/canonical*, canonical mapping table
/etc/postfix/virtual*, virtual mapping table






SEE ALSO


trivial-rewrite(8), address rewriting
qmgr(8), queue manager
header_checks(5), message header content inspection
body_checks(5), body parts content inspection
canonical(5), canonical address lookup table format
virtual(5), virtual alias lookup table format
postconf(5), configuration parameters
master(5), generic daemon options
master(8), process manager
postlogd(8), Postfix logging
syslogd(8), system logging






README FILES




Use "postconf readme_directory" or
    "postconf html_directory" to locate this information.


ADDRESS_REWRITING_README Postfix address manipulation
CONTENT_INSPECTION_README content inspection






LICENSE




The Secure Mailer license must be distributed with this
  software.






AUTHOR(S)


Wietse Venema
IBM T.J. Watson Research
P.O. Box 704
Yorktown Heights, NY 10598, USA
Wietse Venema
Google, Inc.
111 8th Avenue
New York, NY 10011, USA