Free email autoresponder system software for linux

Yet Another Autoresponder (yaa) is an email (vacation) autoresponder that is able to fetch autoresponse data from various sources, using separate plugins for each source type.
Yes, i wrote yet another mail autoresponder daemon. Why? Becouse i was looking for mail autoresponder daemon, which would be easily extendable and would work with Postfix virtual delivery daemon virtual(8). Unfortunatly i was not able to find something like that on the internet, thats why I wrote it in Perl.
Main features:
- Fetches autoresponder data (subject, message, etc...) using plugins
- Currently developed plugins: SQL, LDAP, DB_File, BerkeleyDB, PCRE, STATIC
- It can forward entire original message to the per-recipient custom tunable email address
- Doesnt respond to mailing list posts and posts, that could couse autoresponder deadlock.
- Autoresponse messages can be in any charset.
- Single, all-in-one configuration file
- Can act as SMTP or LMTP server in daemon mode

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::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.

Email::Handle is a Objective Email Handler.

SYNOPSIS

use Email::Handle;

my $email = Email::Handle->new(root@example.com);
print $email->is_valid ? yes : no;
print $email->obfuscate;
print $email->anonymize;
print $email;
$email->send(From => foo@example.com);
This module is also convenient for using on the DB application with Template and Class::DBI / DBIx::Class.
# setup the table that has column of email with this module
my $loader = Class::DBI::Loader->new(
...
namespace => MyApp
);
$loader->find_class(user)->has_a(email => Email::Handle);

# then output records with TT2
my $tmpl = Template->new;
$tmpl->process(
sample.tt,
{ users => $loader->find_class(user)->retrieve_all }
);

# You can write the template with some methods of this module like this
[% WHILE (user IN users) %]
[% user.email.obfuscate IF user.email.is_valid %]
[% END %]

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.

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

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