On Thu, 11 Apr 2013 17:41:25 -0400 (EDT) Wietse Venema articulated: > Mark Alan: > > On Thu, 11 Apr 2013 06:56:13 -0400 (EDT), Wietse Venema > > <wie...@porcupine.org> wrote: > > > > > That should be: > > > > > > us...@example1.com us...@example1.com us...@example2.com > > > us...@example3.com us...@example3.com us...@example4.com > > > > Makes sense and perhaps it seems obvious for the postfix > > developers, but I do not remember seeing such usage case > > (a /etc/postfix/virtual file with user1 -> user1 user2) in the > > postfix documentation, namely, neither at: > > http://www.postfix.org/ADDRESS_REWRITING_README.html > > nor at: > > http://www.postfix.org/VIRTUAL_README.html. > > This is in an unexpected place: > > 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 address, address, ... > Redirect mail for user@domain to address. This form > has the highest precedence. > > ...other examples omitted... > > The text under "TABLE FORMAT" needs some tweaking. > > pattern result > When pattern matches a mail address, replace it by > the corre- sponding result. > > Maybe: > > pattern address, address, ... > When pattern matches a mail address, replace it by > the corre- sponding address(es). > > Would do the job.
Yes, that is a much clearer description of how the option works. -- Jerry ✌ postfix-u...@seibercom.net _____________________________________________________________________ TO REPORT A PROBLEM see http://www.postfix.org/DEBUG_README.html#mail TO (UN)SUBSCRIBE see http://www.postfix.org/lists.html
