Release Notes: This is a production release. It has better handling when a contact with an internal forwarder is not successfully completed (i.e.: connection established, but no signon). It fixes the case where the internal forwarder did not respond to a double check about an email alias found previously (Clement was doing a core dump in this unexpected configuration). It uses 'postmaster' instead of 'Mailer_daemon' for email bounces.
Release Notes: This release fixes a MySQL language syntax error, ROOLBACK instead of ROLLBACK. This error triggers an alarm in /var/log/messages and makes the database inconsistent sometimes. Updating is necessary if you are running clement with a MySQL database. This release also fixes a comstat message about unexpected statuses to be less prone to report an error.
Release Notes: This release include one bugfix at the first install procedure. The install procedure now detects the server as improperly configured if the server name can't be resolved to (at least) one IPV4 IP number.
Release Notes: This release adds several fixes and performance enhancements. It adds a spare IPC channel, improved transit email handling, and a better transit trouble report (the full exchange with the remote server is displayed with a simple click on the Web interface). Overrides are now properly working when the remote server is IPV6. Now clement displays its release status (old or beta) by checking its own version number against the release version as published via DNS. Graph statistics of some Clement production servers show 4.000 accepted email/hour sustained traffic with a peak of 30.000 rejected email messages per hour.
Release Notes: Various bugs were fixed. A sending trace is now available for each email to help the system administrator diagnose problems with delayed transmissions.
Release Notes: This release makes many improvements regarding posting email. Mail logs now include exchange traces with remote systems for every email set with trouble status (remote recipient unknown, mail rejected under various conditions). It now possible to access those logs from the Web interface.