Free email store dbi software for linux

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.

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.

Persistent::DBI is an Abstract Persistent Class implemented using a DBI Data Source.

SYNOPSIS

### we are a subclass of ... ###
use Persistent::DBI;
@ISA = qw(Persistent::DBI);

ABSTRACT

This is an abstract class used by the Persistent framework of classes to implement persistence using DBI data stores. This class provides the methods and interface for implementing Persistent DBI classes. Refer to the Persistent
documentation for a very thorough introduction to using the Persistent
framework of classes.

This class is part of the Persistent DBI package which is available from:

http://www.bigsnow.org/persistent
ftp://ftp.bigsnow.org/pub/persistent

Before we get started describing the methods in detail, it should be noted that all error handling in this class is done with exceptions. So you should wrap an eval block around all of your code. Please see the Persistent documentation for more information on exception handling in Perl.

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 %]

Apache::Storage is Perl module containing simple functions to store and retrieve information from within the Apache process.

MailArchiva is a powerful email archiving solution. MailArchiva project is all you need to ensure that your organizations emails are backed up permanently. It automatically retrieves emails from Microsoft Exchange and stores them on multiple hard disks.
MailArchiva stores all incoming, outgoing, and internal emails for long-term storage. In doing so, it enables your company to retain valuable knowledge and comply with US and EU legislation such as the Sarbanes Oxley Act.
MailArchiva ensures that the integrity of your information remains intact. Emails are stored directly on the filesystem, as opposed to a database. As a result, there are no hidden database maintenance costs and the integrity of archived information is not subject to database corruption.
MailArchiva is a turnkey product that is easy to install and use. A clean install usually takes approximately 30 minutes.
MailArchiva is a commercially supported open source product. You have the assurance of commercial grade support combined with open source benefits.
Enhancements:
- This release introduces several major enhancements and bugfixes.
- For instance, MailArchiva is now fully internationalized, supporting indexing, search, and retrieval of emails in multiple languages.
- The archiving server has been completely rearchitected to utilize Java 1.6 contructs.
- The Microsoft Exchange archiving agent has been redesigned from the ground up.

Dbmail is the name of a group of programs that enable the possiblilty of storing and retrieving mail messages from a database. Currently PostgreSQL and MySQL can be used as database backends.
The upcoming version 2.2 that is under development also supports SQLite, an embedded SQL database system, and ldap for storing userdata. Development and support of dbmail is done by IC&S and NFG, two Dutch companies specializing in Linux development and support.
Main features:
Scalability
- Dbmail is as scalable as the database system that is used for the mail storage. In theory millions of accounts can be managed using dbmail. One could, for example, run 4 different servers with the pop3 daemon each connecting to the same database (cluster) server.
Manageability
- Dbmail is based upon a database. Dbmail can be managed by changing settings in the database (f.e. using PHP/Perl/SQL), without needing shell access.
Speed
- Dbmail uses very efficient, database specific queries for retrieving mail information. This is much faster then parsing a filesystem.
Security
- Dbmail has got nothing to do with the filesystem or interaction with other programs in the Unix environment which need special permissions. Dbmail is as secure as the database its based upon.
Flexibility
- Changes on a Dbmail system (adding of users, changing passwords etc.) are effective immediately.
How does it work?
DBMail is made up of several components. A normal MTA (Postfix, SendMail, QMail, Exim) is used for accepting messages. The MTA hands the messages over to dbmail-smtp, using a pipe interface, or dbmail-lmtpd, using LMTP (Local Mail Transport Protocol). These programs take care of delivering the message into the database. Messages can be retreived from the database using dbmail-pop3d, using the POP3 protocol, and dbmail-imapd, using the IMAP4Rev1 protocol.
The whole email is stored in the database. That includes attachments. The DBMail programs do not have to touch the filesystem to retreive or insert emails. User information is also stored in the database, so users do not need an account on the machines DBMail is running on.
Enhancements:
- This release features greatly improved handling of UTF8 email, has many fixes for IMAP protocol errors, and resolves a number of serious memory leaks.
- A new feature was added to dbmail-export to allow fine-grained message selection and post-export deletion.

Imsptool is a command line tool to communicate with an IMSP server. It allows you to create, delete, import, and export address books.
imsptool imports and exports using the LDIF format. Netscape Messenger and LDAP directory servers such as OpenLDAP use this file format directly.
IMSP is an internet protocol designed to complement IMAP. It stores additional mail user agent configuration information, including address books. IMSP is supported by very few mailers (Simeon by Esys Corp. and Mulberry are two I know of) and is considered obsolete. The ACAP protocol was designed to replace IMSP, but caught on yet.
X.500/LDAP is becoming the standard way to store large e-mail directories.
imsptool was developed to provide an easy way to use IMSP address books in Netscape Messenger. Additionally, it can be used to migrate IMSP address books to LDAP directories.
imsptool has been compiled and tested on Linux 2.2 and Solaris 2.7. It has been tested and works with the Cyrus IMSP server version 1.5a6.
Enhancements:
- imsptool.c: fixed buggy read_literal again, implemented mailing lists on import addressbook, implemented rename command