Free emails software for linux

StrongBad Emails is an extension which adds the words "Previous" and "Next" to the StrongBad Emails.

Tired of having to go back to the main email page to view the next Strong Bad email cartoon? Well wake up and smell the coffee with this extension.

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.

KmailSpy is a small KDE docking mail preview program (POP3) that can be used to get a list of the current emails on your server complete with size, subject, date-time, and "from" information for each entry.

Individual messages can be read (in ASCII text only), saved (in ASCII text only), or deleted.

KMailSpy is intended to be a convenient and quick way to keep an eye on your email server, preview your email, and delete spam to keep your system free of clutter and potential viruses.

Developed with KDevelop 3.33 in C++ on Mepis 6.x

EMailRobot is a simple object-oriented framework for developing email auto-responders.
It performs actions based on parameters extracted from received email bodies and generates answer emails.
Enhancements:
- Minor fixes were made and documentation and installation notes were added.

MailStore is a tool that is built in python and provides a mail proxy for POP3,IMAP4 and SMTP protocols. However, beyond usual proxies, it makes a backup of all incoming and outgoing email and stores them in a Maildir format.

Emails then can be accessed through an IMAP server run on the same machine using the backup Maildirs as mailboxes.

The idea is to provide a realtime , centralized backup of all incoming and outgoing of an organization without the need of user intervention, especially for organizations that use shared email hosting. Many of this hosting providers allow for only POP3 based access of the email.

Secondly, due to its shared hosting environment , there is limited space hence all email ends up being downloaded directly to the client. Any backup effort has to be taken up by the user on a periodical basis. This is prone to problems due to the fact that users might either forget or a data disaster might happen in between a backup cycle.

With a backup proxy like this all email is always available at the backup proxy. Any backup need be done by the administrator only at the proxy server itself. This we believe to be a much more convenient task then backing up user systems individually.

Secondly the MailStore server will always have all the emails the user has sent or received at any point ,hence the backup will always be current. To access the email, a local IMAP server can be run that will provide the user with access to the email that has been backed up. The user may then add this account to their email client and backup all the email out of it locally. (E.g. In Outlook you would probably export all the email in the account). Following that the user will import back the mail back into its original account.

Thirdly , the system requires minimal administrator involvement. It handles the creation of new maildirs for new domain/user combinations. Hence administrators dont have extra config files to play with whenevr new users are added to the system. Whether a user exists or not is left up to the mailserver that mailStore is proxying.

The mailStore system is built in Python. It has been tested with Python 2.3 and 2.4. Any system which support Python 2.3/ Python 2.4 should be able to run it.

Email::Find allows you to find RFC 822 email addresses in plain text.

Email::Find is a module for finding a subset of RFC 822 email addresses in arbitrary text (see "CAVEATS"). The addresses it finds are not guaranteed to exist or even actually be email addresses at all (see "CAVEATS"), but they will be valid RFC 822 syntax.

Email::Find will perform some heuristics to avoid some of the more obvious red herrings and false addresses, but theres only so much which can be done without a human.

Finds email addresses in the text and executes callback registered.

The callback is given two arguments. The first is a Mail::Address object representing the address found. The second is the actual original email as found in the text. Whatever the callback returns will replace the original text.

PerlSendmail is a small script to imitate having sendmail installed.
If you have scripts that require SendMail for sending emails, but do not want to install sendmail on your server then you can use this wrapper instead.
This simple Perl script will send email by connecting to a user specified SMTP server directly. This means that no queue daemons or directories are needed.
If the SMTP server can not be reached then the email will be discarded.
Main features:
- Suitable for use in a chroot environment
- Supports the following sendmail command line options:
-f
-F
-t
- Simple installation
- Simple configuration

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.