Free email servers software for linux

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

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.

Mail::SendEasy can send plain/html e-mails through SMTP servers (platform independent). Supports SMTP authentication and attachments.

This modules will send in a easy way e-mails, and doesnt have dependencies. Soo, you dont need to install libnet.
It supports SMTP authentication and attachments.

USAGE:

OO

use Mail::SendEasy ;

my $mail = new Mail::SendEasy(
smtp => localhost ,
user => foo ,
pass => 123 ,
) ;

my $status = $mail->send(
from => sender@foo.com ,
from_title => Foo Name ,
reply => re@foo.com ,
error => error@foo.com ,
to => recp@domain.foo ,
cc => recpcopy@domain.foo ,
subject => "MAIL Test" ,
msg => "The Plain Msg..." ,
html => "The HTML Msg..." ,
msgid => "0101" ,
) ;

if (!$status) { print $mail->error ;}

STRUCTURED

use Mail::SendEasy ;

my $status = Mail::SendEasy::send(
smtp => localhost ,
user => foo ,
pass => 123 ,
from => sender@foo.com ,
from_title => Foo Name ,
reply => re@foo.com ,
error => error@foo.com ,
to => recp@domain.foo ,
cc => recpcopy@domain.foo ,
subject => "MAIL Test" ,
msg => "The Plain Msg..." ,
html => "The HTML Msg..." ,
msgid => "0101" ,
) ;

if (!$status) { Mail::SendEasy::error ;}

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.

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.

The Perl script testmail checks e-mail available at the POP3 server (including SSL), filters it according to the defined rules, and depending on the selected method gets the messages to the local mailbox and/or removes it from the server.
Testmail uses Perl Mail-POP3Client, Net-Ping, and Socket modules and helps you escape from spam.
Enhancements:
- This release allows the user to use SSL and a specifically selected port (for example, for a Gmail mailbox).
- Testmail now uses Mail-POP3Client module instead of the libnet module.
- Configuration files were changed to add PORT, USESSL, AUTH_MODE, and DEBUG options.
- Some rejecting rules were improved.

Open Project Services (OPS) is a project collaboration platform, integrating server components such as e-mail, calendaring, timesheets, documents, knowledge, etc. with standards complient clients. Open Project Services consists of a project server and a set of client extensions.
We are building a project collaboration platform. It consists of a project server that integrates with services needed within a project, e.g. e-mail, calendaring, timesheets, documents, knowledge, etc.
The project server is a Webservices hub based on Java (J2EE). The persistence layer for project information is LDAP. We use OpenLDAP now, but others should also be possible. The e-mail backend makes use of a standard IMAP server. Our reference implementation uses Courier.
We are building extensions/plugins for clients, making them OPS-enabled. We support e.g. Mozilla Thunderbird (XUL) and Squirrelmail (PHP) for e-mail clients. For the calendaring and timesheet components we have a Mozilla Sunbird extension (XUL).
In short: we are building a project collaboration environment on an OSS stack, enriching services with project information, using COTS clients/servers and open standards.
Enhancements:
- This release includes some changes to the underlying LDAP schema to make it possible to disable tasks when they are completed.
- To make use of this new feature, the Web services and the sunbird timesheet client have to be updated.

Mail::Toaster::Setup is a Perl module with methods to configure and build all the components of a modern email server.

The meat and potatoes of toaster_setup.pl. This is where the majority of the work gets done. Big chunks of the code and logic for getting all the various applications and scripts installed and configured resides in here.

METHODS

All documented methods in this package (shown below) accept two optional arguments, debug and fatal. Setting debug to zero will supress nearly all informational and debugging output. If you want more output, simply pass along debug=>1 and status messages will print out. Fatal allows you to override the default behaviour of these methods, which is to die upon error. Each sub returns 0 if the action failed and 1 for success.

arguments required:
varies (most require conf)

arguments optional:
debug - print status messages
fatal - die on errors (default)

result:
0 - failure
1 - success

Examples:

1. $setup->apache( debug=>0, fatal=>0 );
Try to build apache, do not print status messages and do not die on error(s).

2. $setup->apache( debug=>1 );
Try to build apache, print status messages, die on error(s).

3. if ( $setup->apache( ) { print "yay!n" };
Test to see if apache installed correctly.