[rbldnsd] $TIMESTAMP - is per dataset expiry possible?

[Steven F Siirila]

On Wed, Apr 26, 2006 at 10:51:45PM -0500, Steven F Siirila wrote:
> On Wed, Apr 26, 2006 at 11:44:33PM -0400, Jon Lewis wrote:
> > On Wed, 26 Apr 2006, Paul McClure wrote:
> > 
> > >local-whitelist. Then, I was going to have the -g option tag the TXT 
> > >record on each list with an expiry time (5 minutes for BL, 24 hours for 
> > >WL). I could write this code relatively easily. However, there needs to 
> > >be some method to clear out the expired records from the local-blacklist 
> > >and local-whitelist. Perhaps, a cron job that ran some script. Or, I 
> > >could modify the -r and -a options to ignore expired records. That would 
> > >work too, but the lists would grow and grow and probably still require 
> > >some system to clear them regularly (cron job?). These solutions are not 
> > >very elegant.
> > 
> > I think your best bet is to make your lists SQL based.  i.e. When you add 
> > an IP to your local black or white list, you add an IP and a timestamp 
> > saying when it was added.  Every N minutes, you run a script that expires 
> > entries older than $threshold from the db and then builds the rbldnsd data 
> > from whats left in the db.  i.e. "delete from table where NOW() - add_time 
> > >300" if you want to expire after 5 minutes.
> 
> Or simply use a simple NDBM/GDBM database, which is what we do.
> Using a general-purpose database will no doubt be easier to implement,
> but will generally also be less efficient and use more system resources.

We use a simple ndbm database for greylisting and keeping track of other
interesting MTA characteristics and have found it to be highly efficient.
We chose it for its simplicity as well.

-- 

Steven F. Siirila			Office: Lind Hall, Room 130B
Internet Services			E-mail: sfs at umn.edu
Office of Information Technology	Voice: (612) 626-0244
University of Minnesota			Fax: (612) 626-7593