> > 91: acl greylist dnsrbl "DYNABLOCK" delay 4h
> > 184: acl greylist sm_macro "maybe_forged" delay 8h
funny how these are some 90% of MY acl hits :|
i forget why i use 184 i think it came from your man page ?
i am guessing it comes via this
[gelgin@mail5 mail]$ grep -i forge sendmail.cf
R<FORGED> $#error $@ 5.7.1 $: "550 Relaying denied. IP
name possibly forged " $&{client_name}
oops do i have a config bug ::|
>
> I'm interested by the dnsrbl definitions.
i could send you the list i am sure mine is the BIGGEST.
>
> 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.
i shouldn't say this publicly but i set my grey time REALLY small
if someone is trying more than 1/15m they are 91% (ah... j'aim those
spam assassin heuristics) probably spammer.
>
> Do you think it would buy us something to keep record the the number of
> delivery attempts before a message gets accepted?
>
not really since a key composed of %f%i%S already has this info
besides it might NEVER get accepted (which is why false +s are
such a problem with SORBS).Message
Re: Greylist timing %A
2007-02-25 by george
Attachments
- No local attachments were found for this message.