Free ldap sync replication software for linux

LDAP Mailing Lists Access Policy Daemon (MLAPD) is a mailing list manager that uses LDAP (instead of BDB or GDBM) to control list access. Its designed to work in conjunction with Postfix as an access policy delegation daemon. It manages electronic mail discussion and e-newsletter lists. Its goal is to store/read list data on/from LDAP.
It works as a Postfix access policy delegation agent, so it can be installed one time and used by multiple Postfix instances, or installed multiple times and not suffer database access concurrency issues (because it uses LDAP).
Enhancements:
- This can be considered the first stable and usable release.

LDAP Shell is an interactive LDAP shell written in Perl and allowing basic administrative functionality, such as crawling the directory tree and modifying entries.
It is composed of two parts: Net::LDAP::Config, and ldapsh.
Net::LDAP::Config is a library for simplifying and centralizing access to your LDAP repositories. Instead of having every single script ask for your ldap server and search base, or have it hard coded, you can simply use this library:
my $config = Net::LDAP::Config->new("default");
Its got a couple other nice features, like the fact that it caches your LDAP UID (per host), so you should only ever have to type it in once. Its pretty well documented, so perldoc Net::LDAP::config should get you the rest of the way.
ldapsh, and its corresponding library Net::LDAP::Shell, provide (shockingly) the shell behaviour. When run, ldapsh drops you into a (very simple) interpreter.
Even given its simplicity, though, ldapsh is still very useful: You can use it to walk your LDAP tree, you can clone existing objects (using the clone command), remove objects (can you guess the command?), and create new objects using new.
The new command, when provided one or more objectclasses, will automatically retrieve the required and optional attributes for those objectclasses, which can be a great time-saver.
Enhancements:
- A lot of cleanup, some new commands, and Term::ReadKey support.

Apache Directory Server is an embeddable LDAP server implemented in pure Java.
Our primary vision (others also outlined below) is to build an enterprise directory server platform (and its components) where other Internet services snap in to store their data within the directory so they may be managed using LDAP.
From the image above youll see the architecture is designed so services besides LDAP like DNS, DHCP, SLP and Kerberos will snap in. Other services like UDDI can also be implemented and snapped in. These services will use a common networking layer and each can be toggled on and off according to the needs of the environment.
apseda, mina, or sedang are various frameworks used for the common network layer. These services share the common network layer and back their data within the Apache Directory Servers backing stores without any network latency or going through the LDAP line protocol. NTP btw is the only exception and its there to remedy the need for time sync for replication and other time sensitive protocols like kerberos. Its implementation here is intended to prevent any dependency on external infrastructure.
Main features:
- Designed as an LDAP and X.500 experimentation platform. Plugable components and subsystems make ApacheDS extremely modular and ideal for experiments with various aspects of the LDAP protocol.
- The servers frontend is completely separable from its backend and vice-versa making it very flexible for implementing virtual directories, proxy servers and gateways to X.500.
- Several backends can be implemented and plugged into the servers partition nexus. The server supports a BTree based partition out of the box but any backing store can be used to implement a partition so long as it conforms to interfaces.
- The server exposes aspects of administration via a special system backend. LDAP can be used to manage these concerns through the system naming context at ou=system.
- Java based triggers and stored procedures are being implemented.
- Both the backend subsystem and the frontend are separable and independently embeddable.
- The server contains a server side JNDI LDAP provider as the facade for the entire backend subsystem. JNDI operations are directly translated by this provider into operations against the nexus and the target partitions storing server entries.
- The server will use JNDI as the data access API for stored procedures. This will make stored procedures functional within and outside of the server without requiring recompilation.
- The servers networking code, MINA, Multipurpose Infrastructure for Network Applications was designed for pluggable protocol providers, of all sorts and not just LDAP. MINA gives ApacheDS the ability to handle large amounts of concurrency.
- The server uses the Snickers tools and APIs for ASN.1 BER encoding and decoding. These tools are designed for a very small encoding and decoding footprint as well as for use in non-blocking servers. The chunking nature of the BER codec makes the server very efficient while handling encoding and decoding making it more resistant to DoS attacks. This layer is also pluggable with a new experimental Twix provider which is much more efficient. Of course there is the unsupported Snacc4J provider which is no longer maintained.

Warsync is the program that initiates replication between the Warsync server and its clients. Warsync is designed to be called from the command line of the Warsync server to initiate replication on demand. It can also be called from cron on the server to automate replication.
Warsync not only replicates files from the server to the client, but can also synchronize what software packages are installed on a Debian GNU/Linux system.
Warsync determines what files to replicate by processing the /etc/warsync/filepacks.d directory on the sever. This directory contains filepacks which are simple text files that contain lists of the files and directories that should be replicated.
Installation
On a Debian GNU/Linux system, the best way to install Warsync is to download the Debian package. Once downloaded it can be installed easily with dpkg.
dpkg -i warsync_0.9.8_all.deb
If you receive an error about missing dependencies, a quick call to apt-get will fix that up.
apt-get -f install
Warsync can also be installed manual from the source tarball, although this method has not been tested. A from source installation would go something like this:
tar zxvf warsync_0.9.8.tar.gz
cd warsync-0.9.8
perl Makefile.PL
make
make install
Enhancements:
- Filepack replication introduced.
- Debian package snapshot improvements.
- Output improvments. -q and -v actually mean something along with special handling when run from non-tty (such as cron).
- Real documentation! See warsync-howto manpage.

QmailLdapAdmin is a tool designed to handle qmail-schema of LDAP.
QmailLdapAdmin project provides basic LDAP operations, and it also has a lot of built-in intelligence to support rules to setup email accounts stored in LDAP.
Mailing lists also can be maintained.
Enhancements:
- Setup scritp has been added for automated installation.
- Minor bug fixes.

Single Source information Server provides a set of applets for sharing information from a single source.
The Single Source Infomation Server is a suite of applets designed to share information from a single source, a set of MySQL tables, with as many other systems as possible, starting with PHP, Palm OS PDAs, LDAP, and WAP.
The first part of this project will create a set of PHP pages to edit the information inside a simple set of tables.
This will be the first bi-directional applet (DONE). Following on from there will the ability to export some of this data into a format that can be used by the file link feature in HotSync (DONE), a bi-directional PDA sync (DONE) and by an LDAP server applet, the ability to print single address labels onto a Dymo / CoStar label printer, print envelopes and create a mail-merge export for letters.
If we can work out or get the spec, we will write a QuickBooks timer export for the datebook, and allow import/export of vCal, iCal and vCards.
Enhancements:
- This release fixes a number of bugs and adds some new functionality, includine LDAP.
- After this release we will be making a major re-write to the coldsync conduits, so the next release will be an alpha release of Version 0.2