May 16th, 2013· This release's main improvement is the ability to define a user alias a piped process.
· This can be easily defined via the Web interface (domains manag. -> click user domain -> aliases -> New alias).
· A pipedemo.sh shell script can be used as a starting point.
May 1st, 2013· This version's main improvement is the LDAP interface.
· It can now probe an LDAP server to check if a user exists (no need to define all users within Clement if you already have an LDAP server).
· This version adds list capabilities to find out which users are sending or receiving most of the email traffic (numbers or volumes).
· The email transit interface is improved, and allows you to select one email to be re-sent within a list of delayed messages.
· Current clement users can do an 'rpm update'; previous configurations are kept.
December 10th, 2012· This production release fixes a small bug within Authentication (AUTH PLAIN) on the SMTP channel (working now with an LG smartphone type).
November 20th, 2012· The local plain alias email is set as the good originator when working in smart relaying mode.
· bl.ipv6.spameatingmonkey.net was removed from the IPv6 default SBL server list, as it is no longer responding.
November 15th, 2012· An improvement in smart relaying (taking care of re-bounced email).
· Fixes a bug within the B64 routine that could make one of the listening process crash in the SMTP authentication sequence.
October 3rd, 2012· This version adds a smart relaying improvement: when an IP is within the relayed list, "envelope from:" is checked to verify that the originator is known and still active.
· If the originator wants to use an external email reference (Hotmail, Gmail, etc.), this external email address must be found within a "multi-path" list and linked to an active known user.
· This is to avoid relay spam when the end user workstation is compromised and an unrelated "envelope from:" is used by the bots.
· Various small bugfixes and log improvements have been added.
August 31st, 2012· This version supports TLS-encrypted authentication on POP3 and IMAP channels (used to check user credentials while posting email messages), and fixes a bug within a SQL call which made all SMTP input freeze once in a while (timing-dependant). Users are strongly advised to upgrade.
July 19th, 2012· IP_banned email status can be overridden by standard users now.
· The banned list scan process was staying in zombie state, locking out the next scan; such updates were not transmitted to trusted remote (major bug).
· Group interface and cron activation days can all be unselected (if at least one day was not selected, saving this new configuration was not working).
· When a quarantined email is recalled, this release uses E-From domain instead of H-from domain.
· If both domains were not the same, the override directive was not working correctly with the next email
July 9th, 2012· This version improves trusted/banned remote SMTP site detection speed.
· The banned list is now shared among trusted SMTP servers.
June 28th, 2012· This version added support for PHP versions older than 5.2, which were missing a time zone list.
· For CentOS 5.2 to 5.8, PHP 5.3 is provided if the "extra" repository is enabled in your Clement repository.
· Upgrading is strongly recommended.
January 10th, 2012· Relayed IP/mask are now linked to a groupid.
· Bubble help to major configuration interfaces.
· An updated Clement FAQ.
· Better journalling when a remote server is sending a request with a syntax error.
· Support script bugfixes. Works with clamav 0.97-3.
· A repo is available for clement-el6.2.rpm.
November 26th, 2011· This version 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.
November 1st, 2011· Various bugs were fixed.
· A sending trace is now available for each email to help the system administrator diagnose problems with delayed transmissions.
October 18th, 2011· This version 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.