On Sat, 01 Aug 2009 17:24:30 +0200, Alessandro Vesely <ves...@tana.it> wrote: > Robert Penz wrote: >> A switch (to a minimal blocker process) before forking the smtpconnection >> and submit process would be even better but thats would also take longer. >> Sure the long time solution should be something like this, best together >> with iptables. > > The examples I've seen, e.g. SpamCannibal, work by parsing log lines > and taking specific actions based on that. The action is specific to > the system/network configuration: what ports to block, how long for, > and even whether to use iptables are system specific issues that > cannot be hardcoded. > > Parsing log files is obviously CPU intensive. There ought to be a > standard API to pass a reason code and an IP address to the correct > function, but I wouldn't know whether to look in SNMP, GSS, STREAMS, > or whatelse. > > I don't think coding that would take much longer than writing a log > line. What would take longer is determining which standard applies.
just call a program or send something via a socket like with the courierfilters, the external program can pass it than on in the wished standard. -- Regards, Robert ----- Robert Penz ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ courier-users mailing list courier-users@lists.sourceforge.net Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
