Postfix /etc/postfix/relocated

Authentic ๐Ÿ“‹ Red Hat Enterprise Linux 9 (Plow) 177 lines

Compatibility

Currently viewing:
Red Hat Enterprise Linux 9 (Plow)
Also compatible:
CentOS Stream 9 Red Hat Enterprise Linux 8 (Ootpa)
Different versions:

File Info

Size
177 lines
MD5
416be021c040fd2f9aefc3801e8b5284
SHA256
7ac5924452faaf32bbfbd41f816947fccc3ff2fc17554be7bc5fff99d71ebe2e

Quick Commands

curl:
curl https://exampleconfig.com/api/v1/config/original/416be021c040fd2f9aefc3801e8b5284?hint=relocated
wget:
wget -O relocated https://exampleconfig.com/api/v1/config/original/416be021c040fd2f9aefc3801e8b5284?hint=relocated
/etc/postfix/relocated
# RELOCATED(5)                                                      RELOCATED(5)
# 
# NAME
#        relocated - Postfix relocated table format
# 
# SYNOPSIS
#        postmap /etc/postfix/relocated
# 
# DESCRIPTION
#        The  optional  relocated(5) table provides the information
#        that is used in "user has moved  to  new_location"  bounce
#        messages.
# 
#        Normally,  the  relocated(5)  table is specified as a text
#        file that serves as input to the postmap(1) command.   The
#        result,  an  indexed file in dbm or db format, is used for
#        fast searching by the mail  system.  Execute  the  command
#        "postmap  /etc/postfix/relocated"  to  rebuild  an indexed
#        file after changing the corresponding relocated table.
# 
#        When the table is provided via other means  such  as  NIS,
#        LDAP  or  SQL,  the  same lookups are done as for ordinary
#        indexed files.
# 
#        Alternatively, the  table  can  be  provided  as  a  regu-
#        lar-expression  map  where  patterns  are given as regular
#        expressions, or  lookups  can  be  directed  to  TCP-based
#        server.  In those case, the lookups are done in a slightly
#        different way as described below under "REGULAR EXPRESSION
#        TABLES" or "TCP-BASED TABLES".
# 
#        Table lookups are case insensitive.
# 
# CASE FOLDING
#        The  search  string is folded to lowercase before database
#        lookup. As of Postfix 2.3, the search string is  not  case
#        folded  with database types such as regexp: or pcre: whose
#        lookup fields can match both upper and lower case.
# 
# TABLE FORMAT
#        The input format for the postmap(1) command is as follows:
# 
#        o      An entry has one of the following form:
# 
#                    pattern      new_location
# 
#               Where  new_location  specifies  contact information
#               such as an  email  address,  or  perhaps  a  street
#               address or telephone number.
# 
#        o      Empty  lines and whitespace-only lines are ignored,
#               as are lines whose first  non-whitespace  character
#               is a `#'.
# 
#        o      A  logical  line starts with non-whitespace text. A
#               line that starts with whitespace continues a  logi-
#               cal line.
# 
# TABLE SEARCH ORDER
#        With lookups from indexed files such as DB or DBM, or from
#        networked tables such as NIS, LDAP or  SQL,  patterns  are
#        tried in the order as listed below:
# 
#        user@domain
#               Matches  user@domain. This form has precedence over
#               all other forms.
# 
#        user   Matches user@site when site is $myorigin, when site
#               is listed in $mydestination, or when site is listed
#               in $inet_interfaces or $proxy_interfaces.
# 
#        @domain
#               Matches other addresses in domain.  This  form  has
#               the lowest precedence.
# 
# ADDRESS EXTENSION
#        When a mail address localpart contains the optional recip-
#        ient delimiter (e.g., user+foo@domain), the  lookup  order
#        becomes: user+foo@domain, user@domain, user+foo, user, and
#        @domain.
# 
# REGULAR EXPRESSION TABLES
#        This section describes how the table lookups  change  when
#        the  table  is given in the form of regular expressions or
#        when lookups are directed to a  TCP-based  server.  For  a
#        description of regular expression lookup table syntax, see
#        regexp_table(5) or pcre_table(5). For a description of the
#        TCP client/server table lookup protocol, see tcp_table(5).
#        This feature is not available up to and including  Postfix
#        version 2.4.
# 
#        Each  pattern  is  a regular expression that is applied to
#        the entire address being looked up. Thus, user@domain mail
#        addresses  are  not  broken up into their user and @domain
#        constituent parts, nor is user+foo broken up into user and
#        foo.
# 
#        Patterns  are applied in the order as specified in the ta-
#        ble, until a pattern is  found  that  matches  the  search
#        string.
# 
#        Results  are  the  same as with indexed file lookups, with
#        the additional feature that parenthesized substrings  from
#        the pattern can be interpolated as $1, $2 and so on.
# 
# TCP-BASED TABLES
#        This  section  describes how the table lookups change when
#        lookups are directed to a TCP-based server. For a descrip-
#        tion of the TCP client/server lookup protocol, see tcp_ta-
#        ble(5).  This feature is not available up to and including
#        Postfix version 2.4.
# 
#        Each lookup operation uses the entire address once.  Thus,
#        user@domain mail addresses are not broken  up  into  their
#        user and @domain constituent parts, nor is user+foo broken
#        up into user and foo.
# 
#        Results are the same as with indexed file lookups.
# 
# BUGS
#        The table format does not understand quoting  conventions.
# 
# CONFIGURATION PARAMETERS
#        The  following main.cf parameters are especially relevant.
#        The text below provides  only  a  parameter  summary.  See
#        postconf(5) for more details including examples.
# 
#        relocated_maps
#               List of lookup tables for relocated users or sites.
# 
#        Other parameters of interest:
# 
#        inet_interfaces
#               The network interface addresses  that  this  system
#               receives mail on.  You need to stop and start Post-
#               fix when this parameter changes.
# 
#        mydestination
#               List of domains that  this  mail  system  considers
#               local.
# 
#        myorigin
#               The domain that is appended to locally-posted mail.
# 
#        proxy_interfaces
#               Other interfaces that this machine receives mail on
#               by way of a proxy agent or network address transla-
#               tor.
# 
# SEE ALSO
#        trivial-rewrite(8), address resolver
#        postmap(1), Postfix lookup table manager
#        postconf(5), configuration parameters
# 
# README FILES
#        Use "postconf readme_directory" or  "postconf  html_direc-
#        tory" to locate this information.
#        DATABASE_README, Postfix lookup table overview
#        ADDRESS_REWRITING_README, address rewriting guide
# 
# 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
# 
#                                                                   RELOCATED(5)

How to Install Postfix

Alpine Linux

sudo apk add postfix

Debian

sudo apt update && sudo apt install postfix

Red Hat Enterprise Linux

sudo yum install postfix

Ubuntu

sudo apt update && sudo apt install postfix

Configuration File Location

File Path
/etc/postfix/relocated
Directory
/etc/postfix/
Significance
System-wide configuration directory
Description
Files in /etc/ contain system-wide configuration settings that affect all users.

Complete Postfix Configuration Guide

What is relocated?
Download the original 'relocated' (main.cf) configuration file from a fresh Postfix installation on Red Hat Enterprise Linux 9 (Plow). This is the factory-default mail server configuration, essential for email system recovery, anti-spam setup, and understanding secure mail relay settings.
Technical Details
Located at '/etc/postfix/relocated', this 177-line file controls SMTP authentication, TLS encryption, spam filtering, mail routing, and delivery policies. Powers email infrastructure for millions of domains and handles everything from personal mail servers to enterprise email systems processing thousands of messages daily.
Common Configuration Question
How do you configure Postfix for secure mail delivery, spam prevention, and high availability on Red Hat Enterprise Linux 9?
Why Use This Configuration?
This default configuration includes SPF/DKIM support, TLS encryption, and anti-spam measures. Critical for email administrators, system administrators, and DevOps engineers managing production mail infrastructure.

Frequently Asked Questions

When should I use this relocated file?

Use this original configuration file when you need to restore Postfix to its default state after misconfiguration, during fresh installations, or as a baseline for customization. It's particularly useful for troubleshooting when your current config isn't working properly.

How do I restore Postfix to default settings?

Download this file and replace your current configuration at /etc/postfix/relocated. Make sure to backup your existing configuration first, then restart the Postfix service to apply the changes.

Is this relocated file secure for production use?

This is the factory-default configuration that ships with Postfix on Red Hat Enterprise Linux 9 (Plow). While it provides a secure baseline, you should review and customize security settings based on your specific production requirements and compliance needs.

What's the difference between this and other OS versions?

This configuration is specifically from Red Hat Enterprise Linux 9 (Plow). Different operating systems and versions may have slightly different default settings, security patches, or feature availability. Check the compatibility section above for other OS versions.

Can I use this configuration file for Postfix troubleshooting?

Yes, this original configuration is excellent for troubleshooting. Compare it with your current settings to identify modifications that might be causing issues, or temporarily replace your config with this one to isolate problems.