Are you referring to this block:
<handler class="org.apache.james.smtpserver.DNSRBLHandler">
<rblservers>
<whitelist> query.bondedsender.org. </whitelist>
<blacklist> sbl-xbl.spamhaus.org. </blacklist>
<blacklist> dul.dnsbl.sorbs.net. </blacklist>
<blacklist> list.dsbl.org. </blacklist>
<blacklist> relays.ordb.org. </blacklist>
</rblservers>
</handler>
that is commented out in ../conf/james-smtphandlerchain.xml? Should I
replace the various blacklist entries with zen.spamhaus.org? Any other
black/white lists I should be looking at?
If I enable this, do I need to do anything in my spool manager block?
Thanks. -- Bud
Bud Bach wrote:
Noel, I have verified that is actually is working. My spam processor
is saving the test message to the spam directory. I would guess that
with your approach, the mail is not even accepted. How do I set it up
to check in the "in-protocol" handler chain? I grep'd my james
install for "in-protocol" but didn't find anything. -- Bud
Noel J. Bergman wrote:
I use zen.spamhaus.org, but I use it in the in-protocol handler
chain, not
the mailet pipeline.
--- Noel
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
