PUBLIC MARKS from camel with tags server & control

2008

SugarCRM is a complete CRM system for businesses of all sizes. Core CRM functionality includes sales force automation, marketing campaigns, support cases, project management, calendaring, and more. It supports MySQL and MS SQL Server.
Sugar consists of modules, each of which represents a specific functional aspect of CRM such as Accounts,Activities, Leads, and Opportunities. For example, the Accounts module enables you to create and manage customer accounts, and the Activities module enables you to create and manage activities related to accounts, opportunities, etc. These modules are designed to help you manage customer accounts through each step of their lifecycle, starting with generating and qualifying leads to customer support and resolving reported bugs.
Because many of these steps are interrelated, each module displays related information. For example, when you view the details of a particular account, the system also displays the related contacts, activities,opportunities, and bugs. You can not only view and edit this information but also create new information.
As an administrator, you have the power to implement access control for these modules. You can customize the look and feel of Sugar across your organization. You can even create new modules if needed. You can also create multiple forums as platforms of discussion on various topics amongst your users and customers.

Mail Avenger is a highly-configurable, MTA-independent SMTP server daemon. It lets users run messages through filters like ClamAV and SpamAssassin during SMTP transactions, so the server can reject mail before assuming responsibility for its delivery. Other unique features include TCP SYN fingerprint and network route recording, verification of sender addresses through SMTP callbacks, SPF (sender policy framework) as a general policy language, qmail-style control over both SMTP-level behavior and local delivery of extension addresses, mail-bomb protection, integration with kernel firewalls, and more.

Caching is the temporary storage of frequently accessed data in higher speed media (typically SRAM or RAM) for more efficient retrieval. Web caching stores frequently used objects closer to the client through browser, proxy, or server caches. By storing "fresh" objects closer to your users, you avoid round trips to the origin server, reducing bandwidth consumption, server load, and most importantly, latency. This article shows how to configure your Apache server for more efficient caching to save bandwidth and improve performance.
Caching is not just for static sites, even dynamic sites can benefit from caching. Graphics and multimedia typically don't change as frequently as (X)HTML files. Graphics that seldom change like logos, headers, and navigation can be given longer expiration times while resources that change more frequently like XHTML and XML files can be given shorter expiration times. By designing your site with caching in mind, you can target different classes of resources to give them different expiration times with only a few lines of code.

Lighttpd web server will generate a directory listing if a directory is requested and no index-file was found in that directory. mod_dirlisting is one of the modules that is loaded by default and doesn’t have to be specified on server.modules to work.

2007

Applications using the LAMP (Linux®, Apache, MySQL, PHP/Perl) architecture are constantly being developed and deployed. But often the server administrator has little control over the application itself because it's written by someone else. This series of three articles discusses many of the server configuration items that can make or break an application's performance. This second article focuses on steps you can take to optimize Apache and PHP.
Linux, Apache, MySQL, and PHP (or Perl) form the basis of the LAMP architecture for Web applications. Many open source packages based on LAMP components are available to solve a variety of problems. As the load on an application increases, the bottlenecks in the underlying infrastructure become more apparent in the form of slow response to user requests. The previous article showed you how to tune the Linux system and covered the basics of LAMP and performance measurement. This article focuses on the Web server components, Apache and PHP.