On Tue, Sep 13, 2016 at 05:00:01PM +0200, Christian Rößner wrote:
> > They are. You just need to combine the postcreen_access_list
> > documentation with the socketmap encapsulation.
> >
> >> OK <space> permit (or dunno)
> >> NOTFOUND <space>
> >> TEMP <space> What is done with this reason?
> >
> > It is up to the table-driven mechanism to report it as a warning
> > or to report it as a fatal error.
>
> The background to my question is that I already implemented a fully working
> tcp-map-driven service for postscreen and I just thought about switching
> it to socketmap, if socketmap would give me more choices for replying.
> But as I guess that "reject", "permit" and "dunno" are the only possible
> results, this switch seems useless.
>
> What I miss is something like "defer"
>
> Thanks anyways for helping me to understand this map.
Don't confuse the socketmap layer protocol which can find, not find or
tempfail a lookup, with the Postfix syntax for the lookup result, which,
depending on context access(5), header_checks(5), ...
may begin with various keywords such as:
OK
DUNNO
REJECT
DEFER
WARN
or just some address or transport spec as with virtual(5) or transport(5).
--
Viktor.
