Free email functionality software for linux

Email Administration Utility provides an IMAP-based email account management utility.
The Email Administration Utilities package can be used to manage email accounts with a series of PHP-based scripts through a browser.
Addition, Removal, and modification of accounts is possible as long as an IMAP port is available on the mail server.
The Mailadmin project was originally designed to help owners of domains that were hosted by Hub.Org Networking Services. The company wanted users to be able to create, remove or modify email accounts when ever they wanted, giving them a quicker turnaround for Mail Administration Purposes.
As the utility was developed, tested and matured into what it is today, many users requested more features or contributed reports of issues to help improve the utilities stability. Hub.Org has given me permission to release the utility as an Open Source package so that others may also benifit from the simplicity that the Mailadmin utility offers to those who need complete control over email accounts.
With this in mind, I intend to continue development by adding new features as they are requested and fix any issues that may pop up. The more users who use and test the features that the Mailadmin utility offers will help to improve the functionality offered by Mailadmin. I have opened a Sourceforge account to help manage the development and releases of the utility as it matures into what users and developers see the Mailadmin to be.
Main features:
- Administrator:
- Adding/Deleting Email accounts.
- Setting Account Quotas.
- Obtaining Administrative Access Over Older Accounts.
- Changing An Accounts Password.
- Interfaces with the Cyrus IMAP/POP3 server.
- Transaction Log system, allowing you to track changes or to help debug issues.
- Standard User:
- Changing The Accounts Password.
- In Development:
- Transaction Log system, allowing you to track changes or to help debug issues.

MailRecon is Unix email content control application. It does listen network traffic, capture SMTP messages, analyse it (checks against very flexible and extendable checklist), discards usual private/business messages and save suspicious messages for detailed inspection by security staff.
Main features:
- Capturing email messages from the wire. So its compatible will all mailing software, do not require any reconfiguration and captures messages even if its sent directly to recipient bypassing your mailserver.
- Support for SMTP and POP3 protocols.
- Very flexible mailing filter which goes with MailRecon allows to record only suspicious messages which worth to be examined, and skip usual private and business messages.
- Open Architecture. MailRecon supports plugins for analysis and save of messages. Its very easy to extend its functionality with new plugins - every programmer and system administrator can write it.
- Thanks to Open Architecture, you can use your favorite mail reader or browser to manage archive of captured suspicious messages.
- For limited time, WWW-Security offers free installation and support of evaluation versions on your servers.
- FREE evaluation version which is never expires!
Installation:
- Create user mailrecon and groups mailrecon and mail
- From installation directory run "make install" (as root)
- Copy init.d/mailrecon to your init.d directory and optionally create symlinks from rcN directories if you want to automatially start mailrecon on boot.

Email Files Thunderbird is a very simple service menu script, to email one or more files with Thunderbird to any address or to a given address, which i assume is used as a "backup" space.

The subject is automatically updated according to the attached files and, in case you choose to send to your specific email address, details about sending date, user and host are automatically added in the body.

There are other similar service menus around, but i wanted a script that allows to attach more than one file at one time and that automatically updates the subject line.

USAGE: pretty straightforward.. Just make the two .sh files executable (if necessary) and place them in a directory of your path, for example /home/YOUR_USERNAME/bin. Place the service menu file EmailWithThunderbird.desktop in /home/YOUR_USERNAME/.kde/share/apps/konqueror/servicemenus

IMPORTANT: In file EmailWithThunderbirdToMyAddress.sh, you need to specify your email address in to=.... (that is, where i wrote: YOUR_EMAIL_ADDRESS@DOMAIN.NAME)

This project was tested on OpenSuSE 10.2, KDE 3.5.6

Evolution provides integrated mail, addressbook and calendaring functionality to users of the GNOME desktop.
Main features:
- No viruses or worms
- Junk filtering
- Desktop integration
- Developer Platform (EDS)
- Evolution#
- EPlugin
- Advanced email searching
- Web calendars
- vFolders
- User-defined filters
- Multiple accounts
- Palm device support
- Customized reminders
- Multiple calendar views
- iCalendar support
- To-Do list
- LDAP compatible
- Share vCards
- Security and encryption
- Open Source

Email::AutoReply is a Perl extension for writing email autoresponders.

SYNOPSIS

use Email::AutoReply;
my $auto = Email::AutoReply->new;
$auto->reply;

This module may be useful in writing autoresponders. The example code above will try to respond (using Sendmail) to an email message given as standard input.

The module will reply once to each email address it sees, storing sent-to addresses in a database. This database class is Email::AutoReply::DB::BerkeleyDB by default, but any class that implements Email::AutoReply::DB may be used.

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.

morigin email classifier is a filter that classifies and tags email messages based on the DNS information of the system submitting the mail to your organization.

morigin email classifier can then be used to improve upon existing spam filters such as SpamAssassin.