jibie wrote: >> If one really wanted to do this in Policyd, you will need to run 2 >> instances of Policyd. (one doing sender throttling by SASL/from >> addresses and another instance throttling by HOST addresses). > > Haha =) This is exactly what I thought of initially, but I dismissed it > as a bad hack. Does this issue only exist, because policyd currently > only uses a single table for sender throttle info and I guess the code > expects the data to be one or the other but not both? > > I haven't had a chance to look at the code yet, but how amenable do you > think it would be to using an extra table and allowing both types of > checks? > > I don't want to muck with everything if there's deep magic here that I > don't really understand yet. But if this only requires a little bit of > coding to get working, I can try working on it this weekend.
The code is fairly simple to follow and making those changes shouldn't be that difficult. Such functionality will not be natively supported inside of Policyd itself and any patches you make/create will 1) need to be applied to future revisions and 2) will stop all support when/if things break. Cami ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ policyd-users mailing list policyd-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/policyd-users
