On Jul 21, 2010, at 13:55 , Paul Cockings wrote: > I'd love to hear comments from anyone still running 3.6.8 and 3.8.0 I > want to understand why you didn't upgrade yet. What can we do to help you?
A bit late to the party here, but I might as well chime in: Still running 3.6.8 on an appliance built by someone else quite a few years back. The impetus for using the appliance was multiple failed attempts to directly integrate with CommuniGate Pro due to its broken LDAP alias handling which prevents most individual training implementations. The system was built with a custom phpmysql frontend to handle account creation/deletion/etc and we simply have not had the time to re-work it. We saw similarly impressive improvements with policyd-weight (90% reduction using DSPAM's own stats, at a cost of <1% CPU.) It is now time to move everything to a new platform and (based in large part on my experiences with the postfix-based appliance) I want to use postfix and DSPAM for the new build. It appears that groups may be able to help with our ongoing issue of users who refuse to train, then complain that DSPAM does not work. I need to read up on this as I plan the new system. What would help (aside from just plain time to implement) is a better understanding the various architectural options and interaction with RBLs and whitelists and tools like policyd-weight. Is there some way to tie local blacklisting or greylisting to DSPAM data so we can dynamically reject inbound connections even if the global lists have not yet found a source? thanks, looking forward to 3.9.1 soon! ------------------------------------------------------------------------------ This SF.net email is sponsored by Make an app they can't live without Enter the BlackBerry Developer Challenge http://p.sf.net/sfu/RIM-dev2dev _______________________________________________ Dspam-user mailing list Dspam-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspam-user
