|
Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com |
From: brian moore (bem
rom.org)Date: Wed Sep 05 2001 - 01:36:25 CDT
On Tue, Sep 04, 2001 at 06:25:34PM -0700, Chip Paswater wrote:
> > a) Put all restrictions into smtpd_recipient_restrictions:
> >
> > smtpd_recipient_restrictions =
> > check_sender_access hash:/etc/postfix/relay_domains.map,
> > reject_unknown_sender_domain,
> > permit_mynetworks,
> > check_relay_domains
> >
> > and relay_domains.map would return not OK or REJECT, but the name of a
> > restriction class, e.g. foobar:
>
> How do the ordering of these options work? Maybee I'm dumb, but I've read
> the documentation over and over again, I can't seem to figure it out.
>
> At first I thought it was an ALLOW ALL/DENY FEW operation, like it would go
> down the list looking for a rule to REJECT against, otherwise defaulting to
> OK. Then I saw the option for putting a PERMIT at the bottom of the
> ruleset, which implies a DENY ALL/ALLOW FEW order. So now, I just play
> musical rulesets with the options and telnet to the mail port until I get
> the desired result. Can someone shed some light on this for me?
Well, it's not a binary operation, it's trinary. ( OK, REJECT and
DUNNO).
The order is the order things are checked. It will stop checking when
it gets an OK or REJECT. It will keep checking for a DUNNO (or 'not
found' in the case of things like db lookups).
The order of the checks is the order that postfix will check them.
-
To unsubscribe, send mail to majordomo
postfix.org with content
(not subject): unsubscribe postfix-users
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]