On Tue, Aug 15, 2017 at 05:10:00PM +0200, Gilles Chehade wrote: > On Tue, Aug 15, 2017 at 01:29:16PM +0200, Walter Alejandro Iglesias wrote: > > > > > > accept from any for any virtual <valiases> [...] > > > > > > > Besides, after modifying that rule in the file I also had to change the > > order. Since rules below the "catch-all" one never get evaluated, it > > has forcibly to be the last one: > > > > [...] > > accept from local for local alias <aliases> deliver to mbox > > accept from local sender <addresses> for any relay > > accept from any for any virtual <valiases> deliver to mbox > > # End of file > > > > Not a truth written in stone but, usually, having the "from any for any" > rule in a config file is a sign that user failed to write ruleset and is > using this as a fallback.
The word "mastering" I used in the subject may lead to confusion. I should've written "starting with" instead. :-) My smtpd.conf is not a finished work. Step by step. > The earliest the rules match the envelope, the > better, as it indicates that the rule was written to match precisely. > My intention was to find the way to support the "postmaster" address, that RFC requires to be supported even *with no domain specification.* I wasn't able to figure out how to solve this while the "domain" table was included in the rule. Without that table now I can add to the "valiases" file this: postmaster myuser s...@site1.com ... s...@site2.com ... To make available any of this addresses: postmaster@[IP_ADDRESS] postmas...@site1.com postmas...@site2.com > Most rulesets should finish with a relay (via?) rule from local for any. That's the way I had it, but I couldn't send mail when preceded by "from any to any" rule. I know my current solution is sloppy, I'll try to study a bit more and improve my configuration. Thank you for your help. > > > -- > Gilles Chehade > > https://www.poolp.org @poolpOrg
