Re: sbl-xbl going away; zen replacing it

["Japheth J.C. Cleaver" <cleaver@redwire.net>]

Russ Nelson wrote:
> Spamhaus's sbl-xbl is going away.   Zen replacing it:
> 
> http://www.spamhaus.org/zen/
> 


Here's my problem:
-----------------
Per the site:

Caution: zen.spamhaus.org replaces sbl-xbl.spamhaus.org.
If you are currently using sbl-xbl.spamhaus.org you can now replace
'sbl-xbl.spamhaus.org' with 'zen.spamhaus.org' (the sbl-xbl.spamhaus.org
zone will eventually become obsolete and may in the future be withdrawn
from service).

Caution: Because ZEN includes the XBL and PBL lists, do not use ZEN on
smarthosts or SMTP AUTH outbound servers for your own customers (or you
risk blocking your own customers). Do not use ZEN in filters that do any
‘deep parsing’ of Received headers, or for other than checking IP
addresses that hand off to your mailservers.

------------------

So... what about those of us that *are* using sbl-xbl in either
SpamAssassin-type rulesets (aka 'deep parsing'), or who do want top have
SBL/XBL protection on our smarthosts and outbound smtp-auth'd customer
servers (to prevent IPs infected with Outlook-setting-hijacking viruses
from doing too much damage)?

I don't see the need for removing the sbl-xbl zone in and of itself.
Those of us in similar situations will have to resort back to... adding
sbl. and xbl. individually? This would obviously lead to _more_ queries,
not less.


-jc