Joseph Burford <joseph@...> wrote: > I currently maintain a whitelist for my own use, a couple of other > people use it and provide info for it. > > http://www.ntjl.net/whitelist/ Centralized whitelist would be a nice feature. I see two ways of implementing that in milte-rgreylist: 1) URL inclusion: you'd say in greylist.conf that you want to include config from an URL, with a refresh time: include http://www.example.net/whitelist.txt refresh 1d 2) DNS based: you'd tell in greylist.conf that hosts in a given DNS revserse list should be whitelisted. acl whitelist dnsrbl whitelist.example.com 3) Don't add any code to milter-greylist, and have a cron launched shell-script that fetches Joseph's file and rebuild a config file from it. Solution 1 would require linking with libcurl. It would have other advantages than centralized whitelisting: centralized configuration for MX pools. But that can also be done externally by a cron task that just load the file with wget or ftp and overwrite the config file. I'm not sure it's worth implenting it. OTOH inclusion of local files is usefull too. Solution 2 is nice because it can also be used for greylisting hosts that appear in various DNSRBL (dial-up DNSRBL for instance). Of course both can be done. As usual, IMO that's good features, but that's not features I need, so if someone wants to work on it, contributions are welcome. -- Emmanuel Dreyfus http://hcpnet.free.fr/pubz manu@...
Message
Re: [milter-greylist] re: Delay calculation
2005-03-15 by manu@netbsd.org
Attachments
- No local attachments were found for this message.