----- "Sven Holz" <sven.holz@...> wrote: > > > > > > > > > > How scalability would be improved? Accessing a mysqldb or any db > > stored on Hard Disk is slower than accesing memory directly (only > > mysql memory tables (HEAP) are fast enough. > > > > > > Eduardo is right at this point I also do not believe in performance > impacts but for data manipulation and processing a db would be nice. > In our case we are using the data generated by milter-greylist for > building white and blacklists and detecting other possible spam > sources so a native db backend would be much more comfortable. > How do you user milter-greylist data to generate white/blacklist? If a server doesn't retry you blacklist it? Please it would be kind if you can give me an example of how you re-use the data :D thanks! > > > > > > > > In the only case i think it might help is in configuration data, but > > the text file is not so complicated, and adding layers might add > > problems. > > > > > > It´s much easier to handle the config in a single db or directory. > Normally we generate the configs out of db/directory data but in some > cases just in time changes are usefull and so a single db/directory > would be nice to have. > > Mit freundlichen Gruessen || with kind regards > > Sven Holz > > -- ----- Eduardo Casarero Informatica Avanzada SRL Email: eduardo.casarero@... Tel: (054) 011-52353939 int 115
Message
Re: [~Disarmed~] Re: [~Disarmed~] Re: [milter-greylist] Implement MySQL backend in Milter-greylist
2009-01-19 by Eduardo Casarero
Attachments
- No local attachments were found for this message.