Free email system software for linux

All System Info is a system info SuperKaramba theme. Simple english version...
It shows:
- System Info
- CPU usage
- Network Usage
- Memory Load
- HDD usage

Email::Store is a framework for database-backed email storage.

SYNOPSIS

use Email::Store dbi:mysql:mailstore;
Email::Store->setup; # Do this once

Email::Store::Mail->store( $rfc822 );
Email::Store::Mail->retrieve( $msgid );

...

Email::Store is the ideal basis for any application which needs to deal with databases of email: archiving, searching, or even storing mail for implementing IMAP or POP3 servers.

Email::Store itself is a very lightweight framework, meaning it does not provide very much functionality itself; in effect, it is merely a Class::DBI interface to a database schema which is designed for storing email. Incidentally, if you dont know much about Class::DBI, youre going to need to in order to get much out of this.

Despite its minimalist nature, Email::Store is incredibly powerful. Its power comes from its extensibility, through plugin modules and hooks which allow you to add new database tables and concepts to the system, and so access the mail store from a "different direction". In a sense, Email::Store is a blank canvas, onto which you can pick and choose (or even write!) the plugins which you want for your application.

For instance, the core Email::Store::Entity plugin module addresses the idea of "people" in the email universe, allowing you to search for mails to or from particular people; (despite their changing names or email addresses) Email::Store::Thread interfaces Email::Store to Mail::Thread allowing you to navigate mails by their position in a mail thread; the planned non-core Email::Store::Plucene module plugs into the indexing process and stores information about emails in a Plucene search index for quick retrieval later, and so on.

Sendmail Confirmation System is an Sendmail milter plugin that is designed to reduce the amount of junk email received. SMC uses a dynamic local and DNS based remote "whitelists" (for known/trusted senders), DNS based "blacklists" (for undesired senders), and an original "autoauthentication" system (for unknown, but legitimate senders). In additional SMC has a set of useful features which allows to preserve mail recipients from dangerous message attachments, HTML includes. SMC is an Sendmail tm milter (plugin), which stops the junk mail messages without receiving one.
SMC uses 3 original algorithms, one of which is "Check relay by NS" simulates a dynamical whitelist and will always accept the messages from mail systems satisfying to following conditions:
1) Mail domain name (the host part of the senders e-mail address) must have an MX records;
2) Mail domain name and the connection host address must be resolved;
3) Connection host must be listed at the one of nameservers which hold the senders mail domain name.
The second from the developed algorithms is a "check delays" algorithm which is based on statistical check of delivery delays, generated by a [tempfail] return code, that allows to exclude a direct receiving of a mail, which not passed through the standard mail server.
NOTE: Using this feature the delivery of the mail from unknown, but legitimate senders will be delayed for a count of 5-minutes checks, which setted by the "maxcount" configuration parameter.
And the third of original algorithms is "autoconfirmation" algorithm: The sender of a "mail contact" (sender-recipient pair) means as authenticated (whitelisted) if the filters statistics module has registered the both of a sended forward (request) and a recieved backward (reply) messages of this contact. The messages from the such authenticated senders will never be delayed by the previos "check delay" algorithm.
Enhancements:
- Add checks to prevent overwrite all configuration data during install.
- Minor bug fix in ns-relay code.

Email sends email to remote SMTP servers via the command line, which makes it useful in cron jobs. It will send to any RFC standard remote ESMTP server, and will allow you to encrypt, sign, and design your message on the fly.
It has the capability to use signature files with dynamic options, address book functionality, and users can also attach pictures, binary files, documents, or whatever they want. It is completely compatible with GNUPG for encryption and signing, and is easy to configure and use.
Enhancements:
- A bug where an assert caused an abort when encrypting any message with GnuPG under Cygwin has been fixed.
- Compile time problems where the compiler would complain about SIG* being undeclared have been fixed.
- There is some minor source code cleanup.

The Email Server is designed to provide services offered by its commercial email products, such as IMAP/POP services, Web-Based Email Interface and Administration, Mail Filtering, Spam Blocking and Directory-Based Authentication and Addressbooks.
RH Email Server is fine for businesses and organizations of all sizes. Multiple commercial and educational installations are already using this project. The largest current user load that has been reported is 7,000 + users.
Interoperability between RHSD projects such as the RHSD Email Server and the RHSD Domain Controller will allow for use of Single-Sign On. RHSD also utilizes IETF Standardized projects and therefore will be compatible with any Directory system compatible with LDAP v.3.
Main features:
- Web-Based Email Client for Users
- LDAP Directory / Authentication
- Mail Filtering
- Addressbooks
- Web-Based Administration Tools
- Role-Based Tool Delegation
- Spam Blocking

Mail::Toaster is an installer for a collection of software which provides a full-featured mail server. The system is built around the qmail mail transport agent, with many additions and modifications
Main features:
- SMTP Mail Server (SMTP-AUTH, chk-user, SPF, TLS, tarpitting, RBL)
- Virtual Domain Hosting w/delegated administration
- Virtual Domain Users
- Mailing List (Ezmlm)
- AutoResponder
- Web Based E-Mail (Sqwebmail, Squirrelmail, V-Webmail)
- Web Based Domain Administration
- Mail Filtering (rbls, SpamAssassin, simscan, Qmail-Scanner)
- Virus Scanning (ClamAV, F-Prot, Uvscan)
- SMTP roaming via SMTP-AUTH, POP-AUTH, & IMAP-AUTH
- SMTP roaming via SMTP-submission (port 587)
- POP3, POP3-SSL
- IMAP, IMAP-SSL (Courier IMAP)
- CGI frontend to mail features
- Log processing and pretty graphs (via RRDutil)
- Auto-Installs of MySQL, Apache, phpMyAdmin, and more
- Centralized configuration files
- Support for clusters of qmail servers
- Builds SSL certs for Apache, Qmail, & Courier
Security - Mail::Toaster supports secure connections from the email client (via POP3, IMAP, SMTP, and webmail) to the server. If the remote (destination) email server supports it, we also encrypt the email as it travels across the public Intenet from server to server. Thus, if you happen to be using two Mail::Toasters and your email clients are configured to use SSL, you have a fully encrypted path from the email sender to the final recipient.
State of the Art Filtering - Mail::Toaster has sophisticated filtering capabilities built right in. A default installation blocks all viruses and will detect 85% of the spam. With a little bit of training, its reasonable to expect and achieve 99% spam filtering accuracy.
Flexibility - Mail::Toaster provides an extremely flexible framework to allow you to build your email system your way. This flexibility makes it easy to migrate existing systems to Mail::Toaster and also allows Mail::Toaster to work in diverse environments and OS platforms.
Support - There is a thriving and active support community available on the mailing list. The web forums are also frequented by quite a few helpful folks. If you need more support than folks are willing to provide, commercial support is available.
Enhancements:
- Primarily code quality improvements.
- Rewrites of major portions of the code using techniques described in Perl Best Practices.
- Many more tests, much better tests, and more error testing within the functions.
- A new Webmail interface.
- Its not terribly "pretty" yet, but is much more user friendly and functional.

SurgeMail is the fastest, most robust and secure, full-featured email server on the market today supporting all the protocols and standards. Surgewall works with every mail server and can be installed in minutes, instantly gives you the uniquely advanced, Spam Blocking, Virus Scanning and even user configurable filtering and friends modes normally only found in our SurgeMail product.
Main features:
- User existence is checked at rcpt stage to prevent major spam problems
- Spam and virus free email
- Friends mail screening system.
- Integrated mail server and web based email
- Web based administration (user, domain and server)
- Full SSL secure support for all protocols
- Runs on platform of choice (Windows, most Unix versions)
- Installs in minutes and unparalleled after sales service

Email::Store::DBI is a Perl module for database backend to Email::Store.

SYNOPSIS

use Email::Store dbi:...;

This class is a subclass of Class::DBI and contains means for Email::Store-based programs to register what DSN they wish to use. It also provides for building database tables from schemas embedded in the DATA section of plug-in modules, using Class::DBI::DATA::Schema.

"Email::Store" is the ideal basis for any application which needs to deal with databases of email: archiving, searching, or even storing mail for implementing IMAP or POP3 servers.

"Email::Store" itself is a very lightweight framework, meaning it does not provide very much functionality itself; in effect, it is merely a Class::DBI interface to a database schema which is designed for storing email. Incidentally, if you dont know much about "Class::DBI", youre going to need to in order to get much out of this.

Despite its minimalist nature, "Email::Store" is incredibly powerful. Its power comes from its extensibility, through plugin modules and hooks which allow you to add new database tables and concepts to the system, and so access the mail store from a "different direction". In a sense, "Email::Store" is a blank canvas, onto which you can pick and choose (or even write!) the plugins which you want for your application.

For instance, the core "Email::Store::Entity" plugin module addresses the idea of "people" in the email universe, allowing you to search for mails to or from particular people; (despite their changing names or email addresses) "Email::Store::Thread" interfaces "Email::Store" to "Mail::Thread" allowing you to navigate mails by their position in a mail thread; the planned non-core "Email::Store::Plucene" module plugs into the indexing process and stores information about emails in a Plucene search index for quick retrieval later, and so on.