Christian Ro??ner:
> Is there some chance that postscreen could be extended to also have "defer"?
That is a good question, but you might want to ask that in a thread
that isn't about socketmaps.
Wietse
On Tue, Sep 13, 2016 at 05:40:09PM +0200, Christian Rößner wrote:
> > 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 va
> Am 13.09.2016 um 17:11 schrieb Viktor Dukhovni :
>
> 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 permit (or dunno)
NOTFOUND
TEMP
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 permit (or dunno)
> >> NOTFOUND
> >> TEMP What is done with this reason?
> >
> > It is up to the
> Am 13.09.2016 um 16:51 schrieb Wietse Venema :
>
> Christian Ro??ner:
>> Hi,
>>
>> I just looked into the socketmap_table man page. I try to understand several
>> things:
>>
>> First: Is it correct that request and response are not terminated by newline?
>
> I think that is the least of your
Christian Ro??ner:
> Hi,
>
> I just looked into the socketmap_table man page. I try to understand several
> things:
>
> First: Is it correct that request and response are not terminated by newline?
I think that is the least of your problems.
This is not a text-based protocol where messages are
Hi,
I just looked into the socketmap_table man page. I try to understand several
things:
First: Is it correct that request and response are not terminated by newline?
Second the respone:
OK data
The requested data was found.
NOTFOUND
The requested d
