Free email address search software for linux

Mail::RFC822::Address is a Perl extension for validating email addresses according to RFC822.

SYNOPSIS

use Mail::RFC822::Address qw(valid validlist);

if (valid("pdw@ex-parrot.com")) {
print "Thats a valid addressn";
}

if (validlist("pdw@ex-parrot.com, other@elsewhere.com")) {
print "Thats a valid list of addressesn";
}

Mail::RFC822::Address validates email addresses against the grammar described in RFC 822 using regular expressions. How to validate a user supplied email address is a FAQ (see perlfaq9): the only sure way to see if a supplied email address is genuine is to send an email to it and see if the user recieves it. The one useful check that can be performed on an address is to check that the email address is syntactically valid. That is what this module does.

This module is functionally equivalent to RFC::RFC822::Address, but uses regular expressions rather than the Parse::RecDescent parser. This means that startup time is greatly reduced making it suitable for use in transient scripts such as CGI scripts.

valid ( address )

Returns true or false to indicate if address is an RFC822 valid address.

validlist ( addresslist )

In scalar context, returns true if the parameter is an RFC822 valid list of addresses.

In list context, returns an empty list on failure (an invalid address was found); otherwise a list whose first element is the number of addresses found and whose remaining elements are the addresses. This is needed to disambiguate failure (invalid) from success with no addresses found, because an empty string is a valid list

AddressTangler is a PHP function that helps you protect email addresses that you need to add to a web page from spam bots.
The project uses a simple HTML/CSS trick: The email address is divided into groups of letters, then each group is placed on a table cell, but not sequentially. If a bot browses the HTML code or strips out all the tags from it, it wont find the email address (which is shown correctly when the browser displays the page) but instead a mixed set of groups of letters.
The address, even if correctly displayed, cannot be selected nor copied/pasted. It must be manually typed.
How to use it
It is quite easy to use this function. You only need to give it the email address as a parameter, and it will return the HTML TABLE code.
Remember to copy the at.php file to your webpage folder and add a line like this to the beginning of your PHP code:
require "at.php";
Also remember to add the CSS definition for the table cells to the page with class "at_r1" as follows:
TD.at_r1 {vertical-align:bottom;}
(Note: since the result is a simple HTML table, you dont need to use this function if your page is made with just HTML. You can simply copy the HTML code written on this page and correct it according to the email address that you need to display.)
Version restrictions:
- Keep in mind that not only spam bots will have trouble detecting the email address: the text-to-speech software used by blind users will likely also be affected.
- So, if you plan to make your email address accessible to them, you must provide a second way to publish it. At the present time, this is out of the scope of this project. (perhaps in the future...)
- A possible solution could be to try to describe the address. But even if this results in a high security level, it would be hard to implement it into an automatic function. Also, it could be annoying to hear and complex to understand when used with addresses that make use of many random numbers and letters.

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.

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 2, or simply E2, refers to a new email technology designed from the bottom-up to meet the needs of our modern society.
In contrast with present-day email systems, the E2 infrastructure finds its strength in having a direct connection between E2 clients and servers, instead of relying on a delivery chain of message transfer agents.
Main features:
- The secure transfer of email messages through SSL/TLS is always guaranteed.
- The sender of an email message knows immediately whether a recipient address is valid, and whether the email message was delivered or not.
- A receiver can check instantly whether the return address indicated in an email message is valid.
- A receiver can check instantly whether the sender of an email message owns the return address indicated in the message.
These powerful features are transparent to the end user, and self-contained in the E2 solution. Most importantly, features (3) and (4) can help significantly improve spam detection. How can these features be possible? Simply because E2 servers function as key distribution centers on behalf of their account holders.
Therefore, recipients of an email message can freely download the senders public key from the mail server indicated by the return address, then use the key for authentication. Both the upload and download of keys can be done automatically by E2 clients, making the entire authentication process completely transparent to the end user!
E2 is a standalone solution that does not require additional packages (e.g. IMAP, POP3, etc). It defines a single network protocol capable of, among other things, delivering email messages, retrieving them, uploading and downloading public keys.

RFC822 Address Parser Library provides application developers with a complete parser for RFC822 addresses. Not only can you use the library to verify that RFC822 addresses are syntactically correct, you can also have an address split up into its semantic parts, what is needed when deciding where to route an address to, etc.
What is quite unique is that librfc822 does indeed parse all address types allowed by the standard. That includes such weird things as "address groups" or addresses with whitespace and comments throw in. Take a look at this beast to get an idea:
testing my parser : peter.simons@gmd.de,
(peter.)simons@rhein.de ,,,,,
testing my parser ,
it rules < @peti.gmd.de,@listserv.gmd.de:simons @ cys .de >
;
,
peter.simons@acm.org
That is indeed a legal e-mail address in RFC822 messages. It contains five separate addresses, which are grouped together. Heres the parsed result:
peter.simons@gmd.de
simons@rhein.de
simons@ieee.org
< @peti.gmd.de,@listserv.gmd.de:simons@cys.de >
peter.simons@acm.org
simons@rhein.de
simons@rhein.de
simons@rhein.de
In case you wonder: The strange looking address thats listed fourth is a so called "routing address" -- and yes, thats a legal e-mail address, too. These were popular in the early days of the Internet. Back then, every mail server that relayed an e-mail put its own address into this construct so that bounces could be routed the same way back that they originally went.
The address says that the mail should be send to the host peti.gmd.de, then to listserv.gmd.de, and from there it should be delivered (using any route) to the address simons@cys.de. These days, such addresses can hardly be used, because nobody relays for other recipients anymore. Still, these are legal.
librfc822 provides you with several routines that parse the different flavours of e-mail addresses as defined in the standard. The results will be placed in a rfc822address structure and returned. If constructs are parsed that may contain multiple addresses, you can pass a "committer" class to the function, which is called every time a correct address is found and may append it to a container of your choice.
Enhancements:
- The library has been re-released under an all-permissive license.

pro-search is a crawler for FTP servers, SMB shares, HTTP servers, and DC++ networks.