The HLA Standard Library was developed to support the High Level Assembler (HLA), but could be used with other assemblers or higher-level languages if the necessary headers were developed. It supports 32-bit versions of Windows, Linux, Mac OS X, and FreeBSD, and is written entirely in HLA. It includes the following modules: args, arrays, bits, chars, console, conversions, cset, date, environment, exceptions, file class, file I/O, filesys, lists, math, memory-mapped files, patterns, RNG, stderr, stdin, stdout, strings, tables, time, timer, zstrings, sockets, threads, and blob. An automated test suite is included.
SYINF shows in brief a system's CPU brand and model, RAM size, disk space, operating system, regional parameters, and current date and time. It can run in interactive (menu) or batch mode. There are two versions, in the C and C++ languages. They have been tested on 20 (15) compilers, 26 (25) operating systems, and 18 architectures. (Figures in parentheses are for the C++ version.) Both versions are conveyed in source code form only, each as a single ~35 KB source text file.
Secure GnuPG Form is a Web form that sends encrypted email and attachments using GnuPG, without the sender needing to have GnuPG installed. Versions are available with Recaptcha.net support and two-factor authentication using a username and password and the free PhoneFactor.com service.
Steel Bank Common Lisp is a development environment for Common Lisp, with excellent support for the ANSI standard: garbage collection, lexical closures, powerful macros, strong dynamic typing, incremental compilation, and the famous Common Lisp Object System (multimethods and all). It also includes many extensions, such as native threads, socket support, a statistical profiler, programmable streams, and more. These are all available through an integrated, interactive native compiler which feels like an interpreter. SBCL is unique in being a multiplatform native compiler which bootstraps itself completely from source, using a C compiler and any other ANSI Common Lisp implementation.
Why a milter archiver? If you are required to also log source and destination IPs and BCCs (additional rcpt to's not in a CC field communicated at the SMTP protocol level), then the only option is do this in the MTA, or in a milter application that has hooks in the MTA process (which is exactly why milter was invented). It uses a simple regex file that can be used with several *source target-mailbox rules to define what gets mirrored where. The archiver tries to be as quiet as possible. The possible methods to archive are SMTP, sendmail inject / Postfix inject, IMAP delivery, and milter-add recipient. It was build as a replacement for a Postfix BCC setup: (sender_bcc_maps = regexp:/etc/postfix/archive; recipient_bcc_maps = regexp:/etc/postfix/archive).