Free email and data extractor pro 3.2.13 software for linux

Flat File Extractor can be used for reading different flat file structures and printing them in different formats. ffe is a command line tool developed in GNU/Linux environment and it is distributed under GNU General Public License 2 or later.
Main areas of use are:
- Extracting particular fields or records from a flat file
- Converting data from one format to an other, e.g. from CSV to fixed length
- Verifying a flat file structure
- Testing tool for flat file development
- Displaying flat file content in human readable form
Main features:
- Command-line tool
- Reads standard input and writes to standard output as default
- One input file can contain several types of records (lines)
- Fields in a flat file can be fixed length or separated
- Input file structure and output definitions are independent, meaning one output format can be used with several input files
- Input file structure and output format are freely configurable, they are not predefined
- Output can be formatted e.g. as: fixed length, separated, tokenized, XML, SQL,...
- ffe tries to guess the input format, user needs not to give it as a parameter
Enhancements:
- Configuration keyword const has been added

Evolution Data Server provides a single database for common, desktop-wide information, such as a users address book or calendar events.

Evolution Data Server is also a dependency of the clock applet from the gnome-applets package, 2.10 release.

Evolution provides integrated mail, addressbook and calendaring functionality to users of the GNOME desktop.

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

Local Data Manager (LDM) is a collection of cooperating programs that select, capture, manage, and distribute arbitrary data products.
The system is designed for event-driven data distribution, and is currently used in the Unidata Internet Data Distribution (IDD) project. The LDM system includes network client and server programs and their shared protocols.
An important characteristic of the LDM is its support for flexible, site-specific configuration.
Enhancements:
- Fixes for timestamp bugs.

Obscure-Extractor-GTK can extract data from simple and unusual archives as used by games, e.g. Neverwinter Nights, Homeworld 2, BloodRayne.

Mostly a framework where I can easily add new modules when I want to have a look at the inner workings of games, though the Delphi version has some more advanced stuff like support for old InstallShield archives that would need to be ported.

Email This! Bookmarklet Extension is formerly known as GMail This!

Email This! (formerly known as GMail This!) will send your recipient the link, title, & highlighted text of the page you are viewing using GMail, Yahoo, and Stand-Alone Mail Clients like Outlook Express, Thunderbird, & More!

After downloading (and restarting Firefox), right click anywhere on the toolbar, push customize, and drag the emailthis icon/button to the toolbar (if you want to use the buttons that is - more options in v1.4).
Youre now ready to use EmailThis!

Red = GMail
Green = Yahoo
Blue = Stand-Alone Client

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.

Yukatan data model project is the schema definition of the Yukatan webmail database.
The PostgreSQL database structures defined in this file can be used as a backend store of an email message handling application. The database should be created with the "UNICODE" encoding to properly support messages in different languages.
New data types
The special data types commonly used in the Yukatan data model have been made explicit by the introduction of seven new domains. The domains and the related COMMENT statements make field semantics more clear than before.
See the SQL schema file for more detailed documentation on these domains.
Explicitly named constraints
All the table constraints in the database are now explicitly named and documented. This change makes the database implementation more orthogonal and cleans up the documentation.
Renamed fields and tables
All the *address field names have been truncated to *addr, to make it visually clearer that they are always paired with the corresponding *name fields. The change also makes parts of the documentation less repetitive.
The referencesfield table has been renamed to referencefield to avoid the plural form in the table name. Also all the contained references* field names have been renamed to reference*.
Semantic changes
Quite a few changes have been made to the semantics of various fields. The unnecessarily tight constraints on sequence numbers have been replaced with clearer documentation, the format and encoding of most fields has been explicitly documented, and the previously allowed dual use of the enttext and enddata fields has been prohibited.
Dropped envelope data
The envelope data added in version 0.5 of the data model has for now been removed. The reason for the removal is that the envelope data is not an integral part of an email message, and I wanted to make the version 1.0 as clear as possible. The database now stores "email messages" - nothing less, nothing more. Envelope data can and probably will be reintroduced in an incremental version 1.x along with other extensions.
Enhancements:
- cleans up and documents the data model that has developed since version 0.1
- removal of the envelope data added in version 0.5
- enaming and redefinition of some of the fields and tables
- database structure has also been extensively documented