well `tombo` asked for histograms ?
[gelgin@mail5 ~]$ ./hist.pl
0:accept ( 2) *
123:accept ( 15) **
123:tempfail ( 27) ***
126:tempfail ( 3) *
178:tempfail ( 19) **
181:tempfail ( 1)
184:accept ( 53) *****
184:tempfail (325) ******************************
51:accept ( 92) *********
86:accept ( 1)
87:accept ( 10) *
87:tempfail ( 23) **
91:accept ( 1)
91:tempfail (662)
*************************************************************
93:tempfail ( 23) **
<zero> -10 /
these are my `hits` on ACL lineno (courtesy Text::BarGraph)
here are the ACLs it corresponds to ...
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
51 is actually decieving. as i discussed (outside group) i use
spamassassin as the backend to greylist. that milter forwards spam
(i use 4.2 cutoff VERY agressive) to a local /dev/null mail drop
which show up as most 51's (a good thing actually)
you say "timeout 23h" too tight ? i agree, but note that even
Yahoo!Mail doesn't honor the traditional 5 dys of retries anymore (
i think 24 hrs and `thats all folks` ) ReturnToSender full stop.
if they get a bounce and are too lazy to resend probably not
something worth reading anyway -;
i would encourage folks to continue along the original thread and
`discover` in an analytic way to the magic autowhite time.
____________________________________________________________________________________
8:00? 8:25? 8:40? Find a flick in no time
with the Yahoo! Search movie showtime shortcut.
http://tools.search.yahoo.com/shortcuts/#newsMessage
Re: Greylist timing %A
2007-02-25 by George Elgin
Attachments
- No local attachments were found for this message.