| What we are doing is to track the 2000 (user configurable)
| most recent spammer
| IP addresses. The list is maintained as an MRU style list
| (sorted with the
| most recent at the top). If incoming messages reach a user
| defined score, the
| IP address of the spammer is added to the list.
Hi Scott and all,
We added a test to SpamManager that has produced some really interesting
results.
What we are doing is to track the 2000 (user configurable) most recent spammer
IP addresses. The list is maintained as an MRU style list (sorted with the
most recent at the top). If incoming
Here is what we found. After about 3 weeks of data collection, only about 1 in
400 incoming spams is identified by a DNS lookup, and NOT on the list of the
2000 most recent spammers.
That is quite impressive.
I was thinking that it would probably be a relatively simple matter to add
such a test
I was thinking that it would probably be a relatively simple matter to add
such a test in a future version of declude. If an incoming message reached
a
certain weight, it could be added to a recent spammer list. This list
could be
checked along with other internal tests _before_ DNS tests are
SPThat sounds like an excellent idea -- I'm going to investigate to see
SPwhether this may be possible or not. Circumventing the DNS lookups would
SPbe very useful.
Mr. Obvious here... the same technique could be used in the negative to pass
through frequent mail from *low* scoring servers.
That
