[email protected] (Edgar Pettijohn), 2016.05.21 (Sat) 20:32 (CEST): > > > On 05/20/16 13:26, Olivier Brunel wrote: > > Hello, > > > > I'm new to OpenSMTPD and while this looks really good so far, and with a > > configuration that can be both simple yet powerful/flexible at once, > > even after reading the man pages I still find myself with a few > > questions I can't answer, so I'm hoping I can get some help. > > > > * To make sure: whenever a mapping is used (virtual domains/users, > > aliases...) it always means there *needs* to be a match, and if not > > the rule "fails" and smtpd will move on to the next rule, rejecting > > the message if no other (matching) rule is found -- correct? > > For some cases the doc clearly states so, but not for others, so I'm > > unsure if that's just implied as well, or what's the behavior then? > When a message comes in it checks each rule from top to bottom until it > finds a match. First match wins.
This of course is right regarding *access rules*. I just want to warn that "alias" and "virtual" are not part of the access rule. But "recipient" is. Examples to explain my experiences follow: An email to <[email protected]> will only be delivered if that address is in <aliases>, not if it's in <aliases2>: accept from any to "domain1.com" alias <aliases> accept from any to "domain1.com" alias <aliases2> The same applies for "virtual". On the other hand, if you use "recipient", it is part of the access rule; in the example below the email will be delivered even if <[email protected]> is only in <rcpts2>. accept from any to "domain1.com" recipient <rcpts> relay ... accept from any to "domain1.com" recipient <rcpts2> relay ... This is what my testing showed. Clue sticks appreciated! Bye, Marcus -- You received this mail because you are subscribed to [email protected] To unsubscribe, send a mail to: [email protected]
