Matt Saladna:
> For Wieste,
That is WieTSe, if you don't mind.
>
> /> The implemenation is order-dependent./
It does store the configuration in reverse order. However upon
closer reading of code that I haven't touched in 10+ years...
You are correct in that it applies all patterns that match. The
implementation simply assumes that patterns don't overlap.
If you want a working solution now, I suggest using non-overlapping
patterns:
postscreen_dnsbl_sites =
zen.spamhaus.org=127.[0..255].[0..254].[0..255]*2
zen.spamhaus.org=127.255.255.[252;254;255]*0
I think that a reasonable solution is to use only the first match
in postscreen_dnsbl_sites. That code was not designed to handle
overlapping patterns, and I see no value in trying to make it do
such things.
Then we'd end up with:
postscreen_dnsbl_sites =
# Spamhaus error responses.
zen.spamhaus.org=127.255.255.[252;254;255]*0
# All other Spamhaus responses.
zen.spamhaus.org*2
This provides simple weight-map functionality inside main.cf.
Wietse
