Home  |  Products  |  Purchase  |  Download  |  Support  |  Tech News  |  Contact

Server Downloads

7.0 Production (March 14, 2007)

The 7.0 Production release is now available for Windows and Linux. The upgrade can be retrieved by Pro licensees from the System Administration pages.

6.4.7 Production Patch (October 10, 2006)

Several bugs have been fixed since 6.4 has gone production, specifically in the User and Administrator consoles (GUI fixes) as well as problems with the mail server (STARTTLS advertising and spool file removal). The README.TXT outlines the changes. It is highly recommended you upgrade to this latest patch if you have downloaded the 6.4 production release.

Amazon S3 Downloads (July 27, 2006)

In an effort to improve download performance of both incremental and full Sambar Server distributions we are now using Amazon S3.

6.4 Production (June 27, 2006)

The 6.4 production release is now available. The major features of this release include dynamic start and stop of most services. Enhancements to virtually all areas of the server and the addition of a "Site Manager" facility for delegating management over specific areas of the server. All 6.X licensees will receive the 6.4 upgrade at no charge.

Note: The Home Page configuration parameter has caused some problems for vhost management for users with this property set. A 6.4.1 patch is forthcoming which allows this parameter to be cleared via the Administration pages. As well, the full distribution does not update the config/globals.c file when "upgrade" is selected. This too will be fixed in the 6.4.1 incremental update.

6.3 Production (January 18, 2006)

The major features of this release include document manager enhancements, system administration improvements (reporting, dynamic configuration, enable and disable of servers and services, RSS feeds), blog, photo gallery and address book enhancements. In addition, a new "Friends" feature can be enabled that allows users to associate friend accounts with their login.

Note: With the 6.3 beta 2 release, the passwd file format has been changed to include an access mask in the second to last column. The server is backward compatible with older passwd files, but when modifying an account password or privileges, the format is modified. This format change will result in incorrect display of the "Symbolic Name" field if the server is reverted to 6.2 but should otherwise function correctly.

6.2.6 DBMS and FTP Patch (August 18, 2005)

The DBMS connection pool can be exhausted resulting in a crash and the FTP RWD (delete directory) will cause a crash if versioning is not enabled. These fixes as well as a patch for the zlib buffer overflow announced July 10, 2005 have been fixed in the 6.2.6 patch available from the administration console.

6.2.2 Security Patch (June 1, 2005)

Several cross-site scripting security holes were identified by Jamie Fisher. Windows and Linux patches are available. The 6.2.2 patch fixes an SSL issue introduced in the 6.2.1 patch.

6.2 Production (May 2, 2005)

The 6.2 production release is now quite stable. Thanks to all who exercised the beta releases. The 6.2 release builds on 6.1 with numerous bug fixes and enhancements to existing functionality (especially throttling, spamassasin support, mail mime parsing, and address book enhancements). In June, we will rollout some significant enhancements in the area of clustering (6.3 release).

6.1 Production (September 21, 2004)

The 6.1 production release is now available. This release includes many server enhancements, including:

The only difference between the Linux version and the Windows version is in the executables found in the 'bin' directory. Everything else, including configuration files is 100% compatible between the two (unless you have DOS pathing, i.e. d:/docs, in any config.ini or mapping.ini settings). The only other differences are that unixODBC is used for the DBMS layer and the LD_LIBRARY_PATH is used for locating the Java shared libraries if that functionality is enabled.

If you have problems viewing the ASP pages in the System Administration section it's likely because your mime.ini configuration file lacks an entry for asp extensions or contains an out of date entry. If you remove any existing entries and entry asp = text/html in this file you will be able to view ASP pages correctly.

© 1997-2007 Sambar Technologies, Inc. All rights reserved.