Free checking email software for linux

Check Website is a performance monitoring and uptime notification tool. Check Website will check if a Website is up, and check the response time of the site.
The administrator can then choose to receive an email notification if the site is down, or if the site response time is too slow. All results are also written to a daily log file.
Enhancements:
- This release fixes some small bugs that caused hang ups in the program when checking Web sites.

videocheck project is a simple program for checking and analyzing video AVI file structure.

The program is useful for recovering broken AVI files or finding bugs during development of software that produces AVI files.

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

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.

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.

Catalyst::Plugin::Email::Page is a Perl module to email your Catalyst page.

SYNOPSIS

use Catalyst::Plugin::Email::Page;

__PACKAGE__->config->{email_page}{
email = q{webmaster@example.com},
subject = q{User Report for},
link_text = q{Report Page},
};

# In your Template
[% c.email_page_url %]

This is a simple plugin that lets a developer set and forget e-mail links in Catalyst

INTERFACE

email_page_url

Returns a link in the form of: mailto:webmaster@example.com?subject=User Report for http://yours.com/

The mailto subject is escaped using uri_escape_utf8 from URI::Escape and http://yours.com/ is the current pages uri

email_page_body

Allows you to e-mail the whole page to someone once you have the right template. Used the same way as email_page_url

To do.

email_page_anchor

Allows you to e-mail a page anchor. Used the same way as email_page_url

To do.

_construct_url

Internal routine.

Reads in the various configuration settings and constructs the mailto link. See "CONFIGURATION AND ENVIRONMENT"

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.