George Elgin <gelgin@...> wrote: > 51: acl whitelist list "my network" > 86: acl greylist dnsrbl "SCORE" delay 2h > 87: acl greylist dnsrbl "MCFADDEN" delay 2h > 91: acl greylist dnsrbl "DYNABLOCK" delay 4h > 93: acl greylist dnsrbl "DNSBLNJABL" delay 4h > 123: acl greylist dnsrbl "SORBS-SPAM" delay 1h > 126: acl greylist dnsrbl "SORBS-WEB" delay 1h > 178: acl greylist dnsrbl "NOMOREFUN" delay 2h > 181: acl greylist dnsrbl "unconfirmed" delay 2h > 184: acl greylist sm_macro "maybe_forged" delay 8h I'm interested by the dnsrbl definitions. It seems there is a missing data in order to discover what rule is efficient. For instance, acl 184 gets 53/325 accept/tempfail, which suggests a high rate of spam. But it could be a few legitimate messages that are often retried. Do you think it would buy us something to keep record the the number of delivery attempts before a message gets accepted? -- Emmanuel Dreyfus http://hcpnet.free.fr/pubz manu@...
Message
Re: [milter-greylist] Re: Greylist timing %A
2007-02-25 by manu@netbsd.org
Attachments
- No local attachments were found for this message.