{ "mode": "man", "parameter": "RELOCATED", "section": "5", "url": "https://www.chedong.com/phpMan.php/man/RELOCATED/5/json", "generated": "2026-08-06T11:12:26Z", "synopsis": "", "sections": { "NAME": { "content": "relocated - Postfix relocated table format\n", "subsections": [] }, "SYNOPSIS": { "content": "", "subsections": [ { "name": "postmap /etc/postfix/relocated", "content": "" } ] }, "DESCRIPTION": { "content": "The 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 a 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", "subsections": [] }, "CASE FOLDING": { "content": "The 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", "subsections": [] }, "TABLE FORMAT": { "content": "The 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", "subsections": [] }, "TABLE SEARCH ORDER": { "content": "With 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", "subsections": [] }, "ADDRESS EXTENSION": { "content": "When 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", "subsections": [] }, "REGULAR EXPRESSION TABLES": { "content": "This 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\navailable in Postfix 2.5 and later.\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", "subsections": [] }, "TCP-BASED TABLES": { "content": "This 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 available in Postfix 2.5 and later.\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", "subsections": [] }, "BUGS": { "content": "The table format does not understand quoting conventions.\n", "subsections": [] }, "CONFIGURATION PARAMETERS": { "content": "The 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", "subsections": [ { "name": "relocated_maps (empty)", "content": "Optional lookup tables with new contact information for users or domains that no\nlonger exist.\n\nOther parameters of interest:\n" }, { "name": "inet_interfaces (all)", "content": "The network interface addresses that this mail system receives mail on.\n" }, { "name": "mydestination ($myhostname, localhost.$mydomain, localhost)", "content": "The list of domains that are delivered via the $localtransport mail delivery trans‐\nport.\n" }, { "name": "myorigin ($myhostname)", "content": "The domain name that locally-posted mail appears to come from, and that locally posted\nmail is delivered to.\n" }, { "name": "proxy_interfaces (empty)", "content": "The network interface addresses that this mail system receives mail on by way of a\nproxy or network address translation unit.\n" } ] }, "SEE ALSO": { "content": "trivial-rewrite(8), address resolver\npostmap(1), Postfix lookup table manager\npostconf(5), configuration parameters\n", "subsections": [] }, "README FILES": { "content": "Use \"postconf readmedirectory\" or \"postconf htmldirectory\" to locate this information.\nDATABASEREADME, Postfix lookup table overview\nADDRESSREWRITINGREADME, address rewriting guide\n", "subsections": [] }, "LICENSE": { "content": "The 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\nRELOCATED(5)", "subsections": [] } }, "summary": "relocated - Postfix relocated table format", "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" } ] }