> From: "Jason R. Mastaler" <[EMAIL PROTECTED]> > Date: Wed, 23 Oct 2002 11:31:00 -0600 > > Gre7g Luterman <[EMAIL PROTECTED]> writes: > > > Yes, yes, automating such changes would be easy to do, but that > > doesn't get at the roots of the problem: > > > > [1] The chances that I'll forget to run this shell script after > > editing rcpthosts is just as high as me forgetting to modify the > > filter file in the first place. > > Can't you just run a script from cron (once per minute if need be) > that translates rcpthosts into a format TMDA understands, and then > point all your TMDA filters at that instead? e.g, > > from-file /var/qmail/control/rcpthosts.tmda ok > > What we want to avoid is adding code to support every format of domain > or wildcard out there. It's much more sensical to support one format, > and then have files in other formats translated before TMDA sees them.
Here's a harebrained idea: from-pipe "/usr/local/sbin/hosts2tmda < /var/qmail/control/rcpthosts" which would, of course, have quite a bit of a performance hit, but this would obviously imply from-pipe -autodbm "/usr/local/sbin/hosts2tmda < /var/qmail/control/rcpthosts" if we could figure out how to determine when to create the new dbm file and when not to. However, now that I write that, it sounds fairly impractical...but how about this scheme: from-file -autodbm -filter=/usr/local/sbin/hosts2tmda /var/qmail/control/rcpthosts where filter is a script that reads from STDIN and writes to STDOUT and STDOUT is in a format that tmda can understand. Would that be unworkable? Chris P.S. I like sending ideas to you guys (Jason and Tim) because they've all been taken seriously and several have even been implemented. By the time you get to version 1.0, TMDA is going to be awesome! -- Chris Garrigues http://www.DeepEddy.Com/~cwg/ virCIO http://www.virCIO.Com 716 Congress, Suite 200 Austin, TX 78701 +1 512 374 0500 World War III: The Wrong-Doers Vs. the Evil-Doers.
msg00442/pgp00000.pgp
Description: PGP signature
