> -----Original Message-----
> From: exim-users-admin@??? [mailto:exim-users-admin@exim.org]On
> Behalf Of Tabor J. Wells
<snip>
> You've misinterpretted the purpose of /accept. That is if you had a dnsbl
> that contained only addresses which you wished to explicitly accept mail
> from you would use whitelist.example.com/accept in your rbl_domains.
> So if a lookup for the IP 1.2.3.4 matched 4.3.2.1.whitelist.example.com
> then no further rbl_domains would be considered even if it
> matched in spews,
> etc.
Let me see if we have it clear here. Say we have:
rbl_domains = whitelist.domain.com/accept :
spews.relays.osirusoft.com/reject
Looking at the docs, this should be all right, and should work as indicated:
whitelist.domain.com should be accepted, even if whitelist.domain.com is
listed in SPEWS. Is this correct? If so, this is exactly what is not working
for us. If not, does this indicate that a /reject and /accept are not
compatible in the same statement? That seems to contradict the docs,
although the docs give no example of an /accept in any case except for the
negation entries in rbl_hosts as listed below.
>
> The option you want is rbl_hosts, in particular if you want to exclude
> hosts from dnsbl lookups, then you'd do something like:
>
> rbl_hosts = "! 1.2.3.4/32 : ! 5.6.7.0/24 : \
> ! net32-dbm;/etc/exim/db/whitelist.db : 0.0.0.0/0"
>
> Or if you wanted to actually set up your own whitelist dnsbl
> zone, you could
> use /accept
We tried this as well in rbl_hosts, to exclude (in the example above)
whitelist.domain.com as !1.2.3.4/32 from lookups, with the same lack of
results. It's a bit of a puzzlement, really. We only have half a dozen items
to exclude across dozens of servers, and the fact that we can't get it to
work properly is frustrating.
