This is a tougher case to deal with -- you either have to know the sender is coming from a specific IP address or set of IP addresses, or you have to use a filter mechanism in postfix to decide whether or not to process the message through policyd.
We ended up with some complex rules that regulate which messages get sent to policyd and which bypass it. --Tobias John Beaver wrote: > Tobias Kreidl wrote: > >> Alejandro, >> >> The whole idea of the throttle table is to limit the amount of email of >> a sender for a certain period of time. As the time expires, so do the >> records. You need only establish limits that are applied to all users >> (thoug you can set exceptions in the whitelist), but the throttle and >> throttle_from_instance table will grow and shrik according to the time >> limits set and how often you run the cleanup process. In other words, >> this is normal behavior. >> > > In my use case, I had two specific sending users that I wanted to > throttle, everyone else (default=0) was not. In this use case, these > specific users entries would be deleted after some time and I would have > to go back and enter them. > > > ------------------------------------------------------------------------- SF.Net email is sponsored by: The Future of Linux Business White Paper from Novell. From the desktop to the data center, Linux is going mainstream. Let it simplify your IT future. http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4 _______________________________________________ policyd-users mailing list policyd-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/policyd-users
