>Scott, my understanding is that SpamCop is updated
>automatically real-time by users.... that spam reports
>expire automatically after one week? Is this correct?
That is correct. It will automatically expire one week after the last spam
report is received.
>This means it doesn't expire if it keeps getting
>reported?
That's correct. It will stay in there forever, if there's at least one
spam complaint per week (and it isn't delisted for other reasons; for
example, if there are 100 legitimate mails sent for every 1 spam, I believe
it would get delisted).
>Also, weighted emails. We have not seen documentation
>that clearly outlines how to use this. Is there an
>optimum setting '15' or the like?
We don't have any official documentation on it yet. The optimum setting
would partly depend on what weights you give to the various tests (each
test can have a weight that will be used if E-mail fails the test, and
another that could be used if the E-mail doesn't fail the test).
Below is a copy of the E-mail that was posted here when v1.28 was released,
which added the weighting system, which has more details.
-Scott
---
We have just released Declude JunkMail v1.28 (beta). There are two
important new features. The first is Declude Queue (which is now part of
all the Declude programs; details are at http://www.declude.com/dq.htm ),
which will help stabilize IMail servers, by helping them not run out of a
mysterious undocumented "heap" that can cause mysterious crashes (".DLL
initialization failure" or "0xC0000142").
The second is a weighting system (that was discussed here recently). With
it, you can assign each test a "weight", and you can have a new test that
will only fail if a total weight value is reached. For example, you could
have ORDB assigned a weight of 5, SPAMCOP a weight of 8, and SPAMHEADERS a
weight of 3, along with a "WEIGHT10" test that would get triggered if a
weight of 10 was reached. If just ORDB and SPAMHEADERS failed (a total of
8), the WEIGHT10 test would not be triggered. If the SPAMCOP test failed,
it would not trigger the WEIGHT10 test. But, if the SPAMCOP test and
either the ORDB or SPAMHEADERS tests failed, the WEIGHT10 test would be
triggered.
Without much experimentation, we were able to set it up so that the
weighting system catches about 95% of the spam at our spamtrap. The only
false positive we are aware of was a canned response that we got from
Network Solutions (to an E-mail that they claimed would receive a
personalized reposonse), because they fail the NOPOSTMASTER test, NOWHOIS
test, and REVDNS tests (which had a total weight of 13 the way we set it
up, and a limit of 10). Given that Network Solutions wants us to pay
$10,000 to let people do Whois lookups on our web site, it didn't really
bother me at all that it was caught.
To use the new weighting system, you should look at the new global.cfg
file, which shows how the entries should look. The definition for each
test now has 2 extra numbers added to the end (tests that did not already
have 4 pieces of information associated with them, such as "REVDNS revdns",
need to have a placeholder, so they will now look like "REVDNS revdns x x
10 0"). The first of the two new numbers indicates the weight if a test
fails, while the other number indicates the weight if a test does not fail
(which is normally 0).
You can then add a test using the type "weight", such as "WEIGHT10 weight x
x 20 0", which would get triggered if the total weight was 20 or higher.
It's may seem confusing, so feel free to ask questions about it.
-Scott
---
[This E-mail was scanned for viruses by Declude Virus (http://www.declude.com)]
---
This E-mail came from the Declude.JunkMail mailing list. To
unsubscribe, just send an E-mail to [EMAIL PROTECTED], and
type "unsubscribe Declude.JunkMail". You can E-mail
[EMAIL PROTECTED] for assistance. You can visit our web
site at http://www.declude.com .
