I think you're using too many blacklists.
reject_rbl_client relays.ordb.org, #dead, remove
reject_rbl_client dnsbl.njabl.org, #part of sbl-xbl.spamhaus.org, see below
reject_rbl_client opm.blitzed.org, #dead, remove
reject_rbl_client cbl.abuseat.org, #part of sbl-xbl.spamhaus.org, see below
reject_rbl_client bl.spamcop.net, #ok to use now
reject_rbl_client sbl.spamhaus.org, #change to sbl-xbl.spamhaus.org, see spamhaus' site for what it does
reject_rhsbl_client blackhole.securitysage.com, #haven't heard of this one; a cursory check makes it look ok
reject_rhsbl_sender blackhole.securitysage.com, #see above
reject_rbl_client blackholes.easynet.nl, # dead. remove
reject_rbl_client proxies.blackholes.wirehub.net, #see above
reject_rbl_client list.dsbl.org, #no automatic removal; many entries that are years old. would not use.
reject_rbl_client multihop.dsbl.org, #see above
In addition, I think it's smarter to only do a little DNSBL-based blocking at the STMP level, and let spam software like spamassassin do further checks and assign a spam score. I use sbl-xbl.spamhaus.org and bl.spamcop.net only, because they have very few false positives. See
http://www.dnsbl.com/ for more DNSBL information.