All releases of Greylite
Release Notes: greylite now supports load balancing on upstream SMTP servers, such that one single greylite instance can be used to filter junk mail for many MDAs. New man pages for modules were written.
Release Notes: Plug-ins are supported for databases. Support for SQLite (default) and PostgreSQL are included. Insertion of a newline character to end the recipient information in the database was fixed.
Release Notes: Control on compliance of commands from the clients is now stricter. This release raises the SQLite tryout, and lowers the log priority for useless DB lock messages.
Release Notes: The "354 go ahead (in reply to RCPT TO command)" bug was fixed when responding to non-suspicious clients at the second delivery attempt.
Release Notes: The STARTTLS SMTP command is now handled explicitly. Logging has been made atomic, fixing possible log mixes in case of high concurrencies. An example file for a tolerant suspicion ruleset has been included in the distribution.
Release Notes: This release can work as a generic SMTP proxy with any server. The command session control is completely new, and is able to extract envelope information out of any SMTP command session even with unrecognized/custom commands. SMTP AUTH still passes transparently automatically. The client behaviour analysis can now react sensibly to command errors.
Release Notes: Greetdelay and client behavior analysis were added. The dnsblenv module was added for combining greylite's suspicion with DNS/RBL blacklists. Verified servers are now pruned automatically after 25 days of inactivity.
Release Notes: Suspicion now supports a manifold of rule types: regex, envvar, geoip. Policies can be defined with respect to external modules and with respect to the origin of the client.
Release Notes: This release adds a fix for a possible buffer overflow, a fix for collision handling in SQLite, suspicion (see documentation), earlier detection of "dead clients" (shorter hangs), a new man page, and refined logging.
Release Notes: Stale pending requests in the database are automatically pruned. "Dead" clients are correctly handled, instead of waiting indefinitely. Database locking is insisted up to five times, with exponential delays.
