> > ${config_directory}/reject1_map
> > # These hosts are whitelisted from this test only
> > 192.0.2.1 OK
> > 192.0.2.2 OK
> > # Everyone else gets this test
> > 0.0.0.0/0 reject1
>
> To make "from this test only", it would have to be "DUNNO",
> rather than
> On Dec 29, 2018, at 7:19 PM, Michael Fox wrote:
>
> ${config_directory}/reject1_map
> # These hosts are whitelisted from this test only
> 192.0.2.1 OK
> 192.0.2.2 OK
> # Everyone else gets this test
> 0.0.0.0/0 reject1
To make "from this test
> > Suppose I have the following general case:
> >
> > /etc/postfix/whitelist1:
> > OK
> > OK
> >
> > /etc/postfix/whitelist2:
> > OK
> >
> > How would I accomplish the following?
> >
> > smtpd_*_restrictions =
> > . . .
> > reject_[type1] . . . (except
> Since hostname based whitelists are fragile in the face of transient
> DNS failures, and many users struggle with regular expression correctness.
> A CIDR map is more appropriate here:
> Viktor.
Excellent. Thanks.
Michael
Michael Fox:
> > >
> > > What I'd like to do is have a whitelist apply to only a specific reject.
> >
> > You could use an access table to look up per-recipient rules.
> > See http://www.postfix.org/RESTRICTION_CLASS_README.html for an
> > example.
>
> Hmmm. I read that. I don't see how it
> On Dec 27, 2018, at 12:31 AM, Bill Cole
> wrote:
>
> main.cf:
> smtpd_restriction_classes = whitelist1, whitelist2, unwhitelisted
> whitelist1 = reject_[type2]
> whitelist2 = reject_[type1]
> unwhitelisted = reject_[type1], reject_[type2]
>
> smtpd_*_restrictions =
>
On 26 Dec 2018, at 22:35, Michael Fox wrote:
What I'd like to do is have a whitelist apply to only a specific
reject.
You could use an access table to look up per-recipient rules.
See http://www.postfix.org/RESTRICTION_CLASS_README.html for an
example.
Hmmm. I read that. I don't see how
> In addition to defining alternative restriction lists and classes as
> Wietse noted, you can keep all of your restrictions in the standard
> smtpd_*_restrictions lists if you prefer and can accept the limitation
> of having each type of whitelisting applied to a trailing sublist of
>
On 24 Dec 2018, at 12:40, Michael Fox wrote:
I'm pretty sure I've seen this documented somewhere, but I can't find
it.
In addition to defining alternative restriction lists and classes as
Wietse noted, you can keep all of your restrictions in the standard
smtpd_*_restrictions lists if you
Michael Fox:
> I'm pretty sure I've seen this documented somewhere, but I can't find it.
>
> What I'd like to do is have a whitelist apply to only a specific reject.
> For example:
>
> smtpd_*_restrictions =
> .
> check_*_access .
> reject_.
>
10 matches
Mail list logo
