using external DNSBL's with Outlook
Seth Goodman <sethg <at> GoodmanAssociates.com>
2003-11-03 01:51:42 GMT
Even though the FAQ clearly states that *ideally*, DNSBL's are done at the
server level, many of us are stuck with ISP's who do little, if any of this.
Personally, I would prefer SMTP rejects at the server for MX's listed on
selected DNSBL's, but since I don't run my own mail server, I don't have
this option. Therefore, I have taken to using a POP3 proxy to check several
external DNSBL's and filter based on the results. When there is a hit on an
external list, the POP3 proxy adds an "X-" type header line to identify the
source of the hit. I then have an Outlook rule that filters on that header
line and moves the message to the spam folder.
I would like to figure out a way to best use this added information along
with SpamBayes. As I don't know how the SpamBayes Outlook plug-in fits into
the hierarchy of POP3 email processing, it is hard for me to figure out what
to do. Before installing SpamBayes, my POP3 email went through the
following processing hierarchy (as far as I know):
1) anti-virus filters email coming in on port 110
2) POP3 proxy checks header IP addresses against external DNSBL's
3) Outlook2000 processes message rules
The FAQ talks about a POP3 proxy component, but I don't think this applies
to the Outlook plug-in. How does the SpamBayes Outlook plug-in fit in with
the above processing hierarchy? When exactly does SpamBayes get to work on
a message? There is some mention in the FAQ about "fighting" between
SpamBayes and the Outlook rule processing, and suggests that the background
filtering option will fix this. How does the background filtering option
affect the processing order? What point in time are the processing delays
in the control panel for background processing referenced to?
There is also mention in the FAQ about an "incremental" training mode where
(Continue reading)