The DNS Configuration class is used for maintaining BIND 8 zone files and named.conf files. It is useful for adding and removing zones to your name server as well as the manipulation of resource records within your zones. It is extremely fast and is capable of handling thousands of zones.
The LDAP class for PHP is an easy way to interface your PHP program with an LDAP directory server. The interface is similar to what you would find in a filesystem. You can easily navigate through your directory server similar to the way you would navigate a filesystem with commands such as cd(), mkdir(), etc. A Web-based LDAP browser/modifier is supplied with the class library.
> I understand the need for scalability
> and faster code would be great. I would
> however challange the notition that you
> can't afford 10 more MX servers. I
> think that it's more like "management
> does not want to pay for 10 more MX
I suppose we're getting off topic, but here goes anyway.
Yes it's management, but even I agree with them (for a change). We're talking about serving 50k customers, not 50k employees. The cost of providing the service outweighs the benefits gained from the cost. As we've all seen in the telecom bust, providing services at a lower cost than what you pay is a bad idea :). funny that the engineers realized it and marketing didn't... oh well. Anyway, it's basically an ROI decision.
> I'd be interested in a more extensive
> overview of antispam tools in a
> category review of Topic ::
> Communications :: Email :: Filters, if
> anyone feels up to it.
I would like to see this as well. Most people are concerned about things such as false positives and accuracy. Personally, my biggest concern is per-user configurability. I think that these tools can provide me with the level of flexibility that I need to help users fight spam. My problem then becomes scalability. In a large production environment, say upwards of 50k users, i can't afford for a spam filter solution to drop my CPU resources to zero. I can't (literally) afford to add 10 more MX servers because my spam solution hogs all of the resources.
PERL is nice. It has great flexibility and amazing text processing power. Unfortunately, it is slow. I would really love to see an open source spam fighting solution written in a compiled language to help improve scalability. Perhaps spastic can provide that to me.
The nicest feature that I can see about SpamAssassin is that I can provide a web interface to my users to let them choose how aggresive they want their spam to be filtered. Then if they complain about a false positive, i'll can just tell them to decrease the aggressiveness of the filter.
I liked the article quite a bit. I would really have liked to see information about MANY spam solutions rather than just these two. Brightmail is a decent commercial offering. Fortinet makes anti-spam hardware based firewalls, and there are tons of others.