# man > RELOCATED(5)

[_RELOCATED_(5)](https://www.chedong.com/phpMan.php/man/RELOCATED/5/markdown)                             File Formats Manual                            [_RELOCATED_(5)](https://www.chedong.com/phpMan.php/man/RELOCATED/5/markdown)

## NAME
       relocated - Postfix relocated table format

## SYNOPSIS
### postmap /etc/postfix/relocated

## DESCRIPTION
       The  optional  [**relocated**(5)](https://www.chedong.com/phpMan.php/man/relocated/5/markdown) table provides the information that is used in "user has moved to
       _new_location_" bounce messages.

       Normally, the [**relocated**(5)](https://www.chedong.com/phpMan.php/man/relocated/5/markdown) table is specified as a text file that  serves  as  input  to  the
       [**postmap**(1)](https://www.chedong.com/phpMan.php/man/postmap/1/markdown)  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 regular-expression map where patterns are given
       as  regular expressions, or lookups can be directed to a TCP-based server. In those case, the
       lookups are done in a slightly different way as described below under "REGULAR EXPRESSION TA‐
       BLES" 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)](https://www.chedong.com/phpMan.php/man/postmap/1/markdown) command is as follows:

       •      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.

       •      Empty lines and whitespace-only lines are ignored, as are lines whose first non-white‐
              space character is a `#'.

       •      A  logical  line  starts  with non-whitespace text. A line that starts with whitespace
              continues a logical 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 recipient delimiter (e.g., _user+foo_@_do‐_
       _main_), 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)](https://www.chedong.com/phpMan.php/man/regexptable/5/markdown) or [**pcre_table**(5)](https://www.chedong.com/phpMan.php/man/pcretable/5/markdown). For a  descrip‐
       tion  of  the  TCP  client/server  table  lookup protocol, see [**tcp_table**(5)](https://www.chedong.com/phpMan.php/man/tcptable/5/markdown).  This feature is
       available in Postfix 2.5 and later.

       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 table, until a pattern  is  found  that
       matches the search string.

       Results are the same as with indexed file lookups, with the additional feature that parenthe‐
       sized 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 description of the TCP client/server lookup protocol, see  [**tcp_table**(5)](https://www.chedong.com/phpMan.php/man/tcptable/5/markdown).   This
       feature is available in Postfix 2.5 and later.

       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 pa‐
       rameter summary. See [**postconf**(5)](https://www.chedong.com/phpMan.php/man/postconf/5/markdown) for more details including examples.

### relocated_maps (empty)
              Optional lookup tables with new contact information  for  users  or  domains  that  no
              longer exist.

       Other parameters of interest:

### inet_interfaces (all)
              The network interface addresses that this mail system receives mail on.

### mydestination ($myhostname, localhost.$mydomain, localhost)
              The  list  of domains that are delivered via the $local_transport mail delivery trans‐
              port.

### myorigin ($myhostname)
              The domain name that locally-posted mail appears to come from, and that locally posted
              mail is delivered to.

### proxy_interfaces (empty)
              The network interface addresses that this mail system receives mail on  by  way  of  a
              proxy or network address translation unit.

## SEE ALSO
       [trivial-rewrite(8)](https://www.chedong.com/phpMan.php/man/trivial-rewrite/8/markdown), address resolver
       [postmap(1)](https://www.chedong.com/phpMan.php/man/postmap/1/markdown), Postfix lookup table manager
       [postconf(5)](https://www.chedong.com/phpMan.php/man/postconf/5/markdown), configuration parameters

## README FILES
       Use "**postconf readme_directory**" or "**postconf html_directory**" 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)](https://www.chedong.com/phpMan.php/man/RELOCATED/5/markdown)
