>Given this CONFIG File: > >BADHEADERS badheaders x x 5 0 >SPAMHEADERS spamheaders x x 3 0 >SPAMROUTING spamrouting x x 4 0 >REVDNS revdnsexists x x 5 0 >HEUR10 heuristics 10 x 4 0 >HEUR9 heuristics 9 x 4 0 >HEUR8 heuristics 8 x 3 0 >HEUR heuristics > >WEIGHT10 weight x x 10 0 >WEIGHT8 weight x x 8 0 > >why doesn't the second log entry report that weight8 and/or weight10 has >been exceeded? > >11/04/2001 03:39:42 Qfec315c Msg failed SPAMHEADERS (This E-mail has headers >consistent with spam [60000303].). >11/04/2001 03:39:42 Qfec315c Msg failed SPAMROUTING (This E-mail was routed >in a poor manner consistent with spam [60000303].). >11/04/2001 03:39:42 Qfec315c Msg failed REVDNS (This E-mail was sent from a >mail server with no reverse DNS entry.).
It should. It's possible that there is a per-user or per-domain configuration that doesn't include the WEIGHT8 or WEIGHT10 test, which would account for this. Note that the WEIGHT8/WEIGHT10 tests will only get displayed in the log if they are being used for that E-mail. > Here's the opposite problem - when *I* add up the weight, only get 14 - but > the log claims a value of 18. How does this compute? > ORDB ip4r relays.ordb.org * > SPAMCOP ip4r bl.spamcop.net 127.0.0.2 7 0 > ... > BADHEADERS badheaders x x 5 0 > SPAMHEADERS spamheaders x x 3 0 > SPAMROUTING spamrouting x x 4 0 > ... > WEIGHT10 weight x x 10 0 > WEIGHT8 weight x x 8 0 > 11/04/2001 03:57:02 Q02d5274 Msg failed ORDB (Blackholed by ORDB -- see > http://ordb.org/lookup/?host=200.190.82.26). > 11/04/2001 03:57:02 Q02d5274 Msg failed SPAMCOP (Blocked - see > http://spamcop.net/bl.shtml?200.190.82.26). > 11/04/2001 03:57:02 Q02d5274 Msg failed SPAMHEADERS (This E-mail has headers > consistent with spam [60000303].). > 11/04/2001 03:57:02 Q02d5274 Msg failed SPAMROUTING (This E-mail was routed > in a poor manner consistent with spam [60000303].). I also count 14 for this one. The next release will include a line that shows exactly how the value is calculated. Every one I've checked here has added up correctly, but the new log file entry will show what Declude is thinking. -Scott --- 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 .
