{
    "content": [
        {
            "type": "text",
            "text": "# RELOCATED(5) (man)\n\n**Summary:** relocated - Postfix relocated table format\n\n## See Also\n\n- trivial-rewrite(8)\n- postmap(1)\n- postconf(5)\n\n## Section Outline\n\n- **NAME** (2 lines)\n- **SYNOPSIS** (1 lines) — 1 subsections\n  - postmap /etc/postfix/relocated (1 lines)\n- **DESCRIPTION** (18 lines)\n- **CASE FOLDING** (4 lines)\n- **TABLE FORMAT** (15 lines)\n- **TABLE SEARCH ORDER** (12 lines)\n- **ADDRESS EXTENSION** (3 lines)\n- **REGULAR EXPRESSION TABLES** (16 lines)\n- **TCP-BASED TABLES** (10 lines)\n- **BUGS** (2 lines)\n- **CONFIGURATION PARAMETERS** (12 lines) — 2 subsections\n  - mydestination (2 lines)\n  - myorigin (6 lines)\n- **SEE ALSO** (4 lines)\n- **README FILES** (4 lines)\n- **LICENSE** (16 lines)\n\n## Full Content\n\n### NAME\n\nrelocated - Postfix relocated table format\n\n### SYNOPSIS\n\n#### postmap /etc/postfix/relocated\n\n### DESCRIPTION\n\nThe  optional  relocated(5) table provides the information that is used in \"user has moved to\nnewlocation\" bounce messages.\n\nNormally, the relocated(5) table is specified as a text file that  serves  as  input  to  the\npostmap(1)  command.   The  result,  an  indexed  file  in dbm or db format, is used for fast\nsearching by the mail system. Execute the command \"postmap /etc/postfix/relocated\" to rebuild\nan indexed file after changing the corresponding relocated table.\n\nWhen  the  table  is  provided via other means such as NIS, LDAP or SQL, the same lookups are\ndone as for ordinary indexed files.\n\nAlternatively, the table can be provided as a regular-expression map where patterns are given\nas  regular  expressions,  or lookups can be directed to TCP-based server. In those case, the\nlookups are done in a slightly different way as described below under \"REGULAR EXPRESSION TA‐\nBLES\" or \"TCP-BASED TABLES\".\n\nTable lookups are case insensitive.\n\n### CASE FOLDING\n\nThe  search  string  is  folded  to  lowercase before database lookup. As of Postfix 2.3, the\nsearch string is not case folded with database types such as regexp: or  pcre:  whose  lookup\nfields can match both upper and lower case.\n\n### TABLE FORMAT\n\nThe input format for the postmap(1) command is as follows:\n\n•      An entry has one of the following form:\n\npattern      newlocation\n\nWhere  newlocation specifies contact information such as an email address, or perhaps\na street address or telephone number.\n\n•      Empty lines and whitespace-only lines are ignored, as are lines whose first non-white‐\nspace character is a `#'.\n\n•      A  logical  line  starts  with non-whitespace text. A line that starts with whitespace\ncontinues a logical line.\n\n### TABLE SEARCH ORDER\n\nWith lookups from indexed files such as DB or DBM, or from networked tables such as NIS, LDAP\nor SQL, patterns are tried in the order as listed below:\n\nuser@domain\nMatches user@domain. This form has precedence over all other forms.\n\nuser   Matches  user@site  when  site is $myorigin, when site is listed in $mydestination, or\nwhen site is listed in $inetinterfaces or $proxyinterfaces.\n\n@domain\nMatches other addresses in domain. This form has the lowest precedence.\n\n### ADDRESS EXTENSION\n\nWhen a mail address localpart contains the optional recipient delimiter  (e.g.,  user+foo@do‐\nmain), the lookup order becomes: user+foo@domain, user@domain, user+foo, user, and @domain.\n\n### REGULAR EXPRESSION TABLES\n\nThis  section  describes  how the table lookups change when the table is given in the form of\nregular expressions or when lookups are directed to a TCP-based server. For a description  of\nregular  expression lookup table syntax, see regexptable(5) or pcretable(5). For a descrip‐\ntion of the TCP client/server table lookup protocol, see tcptable(5).  This feature  is  not\navailable up to and including Postfix version 2.4.\n\nEach  pattern  is a regular expression that is applied to the entire address being looked up.\nThus, user@domain mail addresses are not broken up into their user  and  @domain  constituent\nparts, nor is user+foo broken up into user and foo.\n\nPatterns  are  applied  in the order as specified in the table, until a pattern is found that\nmatches the search string.\n\nResults are the same as with indexed file lookups, with the additional feature that parenthe‐\nsized substrings from the pattern can be interpolated as $1, $2 and so on.\n\n### TCP-BASED TABLES\n\nThis  section describes how the table lookups change when lookups are directed to a TCP-based\nserver. For a description of the TCP client/server lookup protocol, see  tcptable(5).   This\nfeature is not available up to and including Postfix version 2.4.\n\nEach lookup operation uses the entire address once.  Thus, user@domain mail addresses are not\nbroken up into their user and @domain constituent parts, nor is user+foo broken up into  user\nand foo.\n\nResults are the same as with indexed file lookups.\n\n### BUGS\n\nThe table format does not understand quoting conventions.\n\n### CONFIGURATION PARAMETERS\n\nThe following main.cf parameters are especially relevant.  The text below provides only a pa‐\nrameter summary. See postconf(5) for more details including examples.\n\nrelocatedmaps\nList of lookup tables for relocated users or sites.\n\nOther parameters of interest:\n\ninetinterfaces\nThe network interface addresses that this system receives mail on.  You need  to  stop\nand start Postfix when this parameter changes.\n\n#### mydestination\n\nList of domains that this mail system considers local.\n\n#### myorigin\n\nThe domain that is appended to locally-posted mail.\n\nproxyinterfaces\nOther interfaces that this machine receives mail on by way of a proxy agent or network\naddress translator.\n\n### SEE ALSO\n\ntrivial-rewrite(8), address resolver\npostmap(1), Postfix lookup table manager\npostconf(5), configuration parameters\n\n### README FILES\n\nUse \"postconf readmedirectory\" or \"postconf htmldirectory\" to locate this information.\nDATABASEREADME, Postfix lookup table overview\nADDRESSREWRITINGREADME, address rewriting guide\n\n### LICENSE\n\nThe Secure Mailer license must be distributed with this software.\n\nAUTHOR(S)\nWietse Venema\nIBM T.J. Watson Research\nP.O. Box 704\nYorktown Heights, NY 10598, USA\n\nWietse Venema\nGoogle, Inc.\n111 8th Avenue\nNew York, NY 10011, USA\n\n\n\nRELOCATED(5)\n\n"
        }
    ],
    "structuredContent": {
        "command": "RELOCATED",
        "section": "5",
        "mode": "man",
        "summary": "relocated - Postfix relocated table format",
        "synopsis": "",
        "tldr_summary": null,
        "tldr_examples": [],
        "tldr_source": null,
        "flags": [],
        "examples": [],
        "see_also": [
            {
                "name": "trivial-rewrite",
                "section": "8",
                "url": "https://www.chedong.com/phpMan.php/man/trivial-rewrite/8/json"
            },
            {
                "name": "postmap",
                "section": "1",
                "url": "https://www.chedong.com/phpMan.php/man/postmap/1/json"
            },
            {
                "name": "postconf",
                "section": "5",
                "url": "https://www.chedong.com/phpMan.php/man/postconf/5/json"
            }
        ],
        "section_outline": [
            {
                "name": "NAME",
                "lines": 2,
                "subsections": []
            },
            {
                "name": "SYNOPSIS",
                "lines": 1,
                "subsections": [
                    {
                        "name": "postmap /etc/postfix/relocated",
                        "lines": 1
                    }
                ]
            },
            {
                "name": "DESCRIPTION",
                "lines": 18,
                "subsections": []
            },
            {
                "name": "CASE FOLDING",
                "lines": 4,
                "subsections": []
            },
            {
                "name": "TABLE FORMAT",
                "lines": 15,
                "subsections": []
            },
            {
                "name": "TABLE SEARCH ORDER",
                "lines": 12,
                "subsections": []
            },
            {
                "name": "ADDRESS EXTENSION",
                "lines": 3,
                "subsections": []
            },
            {
                "name": "REGULAR EXPRESSION TABLES",
                "lines": 16,
                "subsections": []
            },
            {
                "name": "TCP-BASED TABLES",
                "lines": 10,
                "subsections": []
            },
            {
                "name": "BUGS",
                "lines": 2,
                "subsections": []
            },
            {
                "name": "CONFIGURATION PARAMETERS",
                "lines": 12,
                "subsections": [
                    {
                        "name": "mydestination",
                        "lines": 2
                    },
                    {
                        "name": "myorigin",
                        "lines": 6
                    }
                ]
            },
            {
                "name": "SEE ALSO",
                "lines": 4,
                "subsections": []
            },
            {
                "name": "README FILES",
                "lines": 4,
                "subsections": []
            },
            {
                "name": "LICENSE",
                "lines": 16,
                "subsections": []
            }
        ]
    }
}