On 30/05/16 03:29, Michael Fox wrote:
> Ah. O.K. My original post said that I'm trying to configure
> postscreen_access.cidr,
This is the name of a table, which has absolutely no bearing on what
setting it is used for. You could point alias_maps to
postscreen_access.cidr and then the expected re
> The access(5) manpage is for the Postfix SMTP DAEMON. It says so
> on the first line of the manpage, and it says so again in the first
> paragraph.
>
> The postscreen_access_list parameter, as the name suggests, is for
> the POSTSCREEN DAEMON. This name is as explicit as it can be, without
> chan
Michael Fox:
>
> > What is a valid result depends on what the result is used for: an
> > access table expects results as described in the access(5) manpage,
> > a virtual aliases table expects the results as described in the
> > virtual(5) manpage, a transport table expects results as described
On 2016-05-29 06:34, Michael Fox wrote:
What is a valid result depends on what the result is used for: an
access table expects results as described in the access(5) manpage,
a virtual aliases table expects the results as described in the
virtual(5) manpage, a transport table expects results as d
> What is a valid result depends on what the result is used for: an
> access table expects results as described in the access(5) manpage,
> a virtual aliases table expects the results as described in the
> virtual(5) manpage, a transport table expects results as described
> in the transport(5) m
Michael Fox:
> 1) How can I tell which result values can be used in any given lookup
> table?
What is a valid result depends on what the result is used for: an
access table expects results as described in the access(5) manpage,
a virtual aliases table expects the results as described in the
