Milter-greylist

Richard Frovarp wrote:
 > Oliver Fromme wrote:
 > > Seth Mos wrote:
 > > > If however coupled with a lifetime like the autowhitelist, which was my
 > > > original intention, that would make the best example of reducing the
 > > > impact of grey listing in the enterprise. It would still however achieve
 > > > very good results.
 > > > 
 > > > Take my exmaple, apply a 10 day auto whitelist and suddenly it covers
 > > > 95% of whitelisting all business communications. In a considerably sized
 > > > company this reduces administration a lot without reducing the grey
 > > > listing benefits.
 > > 
 > > Isn't that case pretty much covered by the "lazyaw"
 > > option in the configuration file?
 > 
 > However, if the total spam run takes longer than your greylist time, 
 > wouldn't that allow the messages through then? Or does lazyaw only trip 
 > off after a (IP, sender, receiver) tuple passes?

The latter.  lazyaw does not change the way tuples are
handled at the greylisting stage.  It only changes the
autowhitelisting so that the whole IP is whitelisted
_after_ a tuple has been accepted from that IP.

I have enabled the lazyaw option since I began to use
milter-greylist a few years ago, and it seems to work
very well.

Best regards
   Oliver

-- 
Oliver Fromme, secnetix GmbH & Co. KG, Marktplatz 29, 85567 Grafing b. M.
Handelsregister: Registergericht Muenchen, HRA 74606,  Gesch\ufffdftsfuehrung:
secnetix Verwaltungsgesellsch. mbH, Handelsregister: Registergericht M\ufffdn-
chen, HRB 125758,  Gesch\ufffdftsf\ufffdhrer: Maik Bachmann, Olaf Erb, Ralf Gebhart

FreeBSD-Dienstleistungen, -Produkte und mehr:  http://www.secnetix.de/bsd

"Python tricks" is a tough one, cuz the language is so clean. E.g.,
C makes an art of confusing pointers with arrays and strings, which
leads to lotsa neat pointer tricks; APL mistakes everything for an
array, leading to neat one-liners; and Perl confuses everything
period, making each line a joyous adventure <wink>.
        -- Tim Peters