validate email address
Sponsored Links
Sponsored Links
Secleted [ 0 ] software to compare
Results 1 - 15 of about 2788
Validate_fields Class 1.34
Validate_fields Class is an easy-to-use form field validation PHP script. more>>
Validate_fields Class is an easy-to-use form field validation PHP script. This class can be used to validate database inputs or mail forms.
It can validate simple text, numbers, dates, urls, email addresses, and the presence of HTML tags. Invalid form fields will be reported inside a detailed error message.
Enhancements:
- A small improvement in the create_msg() method makes it possible to switch between the XHTML version and the simple HTML version.
- In the fields array one key was named "name", and it has been renamed to "value" to make it more clear.
- The variable declarations at the beginning of the validation method was removed.
- Because the value of a checkbox (radio) type field is only available if the element is checked, there are new functions to validate this elements.
<<lessIt can validate simple text, numbers, dates, urls, email addresses, and the presence of HTML tags. Invalid form fields will be reported inside a detailed error message.
Enhancements:
- A small improvement in the create_msg() method makes it possible to switch between the XHTML version and the simple HTML version.
- In the fields array one key was named "name", and it has been renamed to "value" to make it more clear.
- The variable declarations at the beginning of the validation method was removed.
- Because the value of a checkbox (radio) type field is only available if the element is checked, there are new functions to validate this elements.
Download (0.008MB)
Added: 2006-02-21 License: GPL (GNU General Public License) Price:
1340 downloads
Mail::RFC822::Address 0.3
Mail::RFC822::Address is a Perl extension for validating email addresses according to RFC822. more>>
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
<<lessSYNOPSIS
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
Download (0.005MB)
Added: 2007-02-14 License: Perl Artistic License Price:
985 downloads
My Address Book 1.2
My Address Book is a Web-based contact list program. more>>
My Address Book is a Web-based contact list program. It stores information like addresses, phone numbers, email addresses, and Web sites, and has a notes section for custom information.
Add, delete, and edit functions can be password protected using htaccess. Complete style control using CSS.
Main features:
- Add an unlimited number of contacts.
- Easy to use and read.
- Specify your own colors.
- Use your own template.
<<lessAdd, delete, and edit functions can be password protected using htaccess. Complete style control using CSS.
Main features:
- Add an unlimited number of contacts.
- Easy to use and read.
- Specify your own colors.
- Use your own template.
Download (0.016MB)
Added: 2005-10-19 License: GPL (GNU General Public License) Price:
1473 downloads
PEAR Validate 0.6.4
PEAR Validate is a set of useful methods to validate various kinds of data. more>>
PEAR Validate is a set of useful methods to validate various kinds of data.
Main features:
- numbers (min/max, decimal or not)
- email (syntax, domain check, rfc822)
- string (predifined type alpha upper and/or lowercase, numeric,...)
- date (min, max)
- uri (RFC2396)
- possibility valid multiple data with a single method call (::multiple)
<<lessMain features:
- numbers (min/max, decimal or not)
- email (syntax, domain check, rfc822)
- string (predifined type alpha upper and/or lowercase, numeric,...)
- date (min, max)
- uri (RFC2396)
- possibility valid multiple data with a single method call (::multiple)
Download (0.014MB)
Added: 2006-08-02 License: The PHP License Price:
1179 downloads
CGI::Validate 2.000
CGI::Validate is an advanced CGI form parser and type validation. more>>
CGI::Validate is an advanced CGI form parser and type validation.
SYNOPSIS
use CGI::Validate; # GetFormData() only
use CGI::Validate qw(:standard); # Normal use
use CGI::Validate qw(:subs); # Just functions
use CGI::Validate qw(:vars); # Just exception vars
## If you dont want it to check that every requested
## element arrived you can use this. But I dont recommend it
## for most users.
$CGI::Validate::Complete = 0;
## If you dont care that some fields in the form dont
## actually match what you asked for. -I dont recommend
## this unless you REALLY know what youre doing because this
## normally meens youve got typos in your HTML and we cant
## catch them if you set this.
## $CGI::Validate::IgnoreNonMatchingFields = 1;
my $FieldOne = Default String;
my $FieldTwo = 8;
my $FieldThree = some default string;
my @FieldFour = (); ## For multi-select field
my @FieldFive = (); ## Ditto
my $EmailAddress= ;
## Try...
my $Query = GetFormData (
FieldOne=s => $FieldOne, ## Required string
FieldTwo=i => $FieldTwo, ## Required int
FieldThree => $FieldThree, ## Auto converted to the ":s" type
FieldFour=s => @FieldFour, ## Multi-select field of strings
FieldFive=f => @FieldFive, ## Multi-select field of floats
Email=e => $EmailAddress, ## Must look like an email address
) or do {
## Catch... (wouldnt you just love a case statement here?)
if (%Missing) {
die "Missing form elements: " . join ( , keys %Missing);
} elsif (%Invalid) {
die "Invalid form elements: " . join ( , keys %Invalid);
} elsif (%Blank) {
die "Blank form elements: " . join ( , keys %Blank);
} elsif (%InvalidType) {
die "Invalid data types for fields: " . join ( , keys %InvalidType);
} else {
die "GetFormData() exception: $CGI::Validate::Error";
}
};
## If you only want to check the form data, but dont want to
## have CGI::Validate set anything use this. -You still have full
## access to the data via the normal B object that is returned.
use CGI::Validate qw(CheckFormData); # not exported by default
my $Query = CheckFormData (
FieldOne=s, FieldTwo=i, FieldThree, FieldFour,
FieldFive, Email,
) or do {
... Same exceptions available as GetFormData above ...
};
## Need some of your own validation code to be used? Here is how you do it.
addExtensions (
myType => sub { $_[0] =~ /test/ },
fooBar => &fooBar,
i_modify_the_actual_data => sub {
if ($_[0] =~ /test/) { ## data validation
$_[0] = whatever; ## modify the data by alias
return 1;
} else {
return 0;
}
},
);
my $Query = GetFormData (
foo=xmyType => $foo,
bar=xfooBar => $bar,
cat=xi_modify_the_actual_data => $cat,
);
## Builtin data type checks available are:
s string # Any non-zero length value
w word # Must have at least one w char
i integer # Integer value
f float # Float value
e email # Must match m/^s*]+@[^@.]+(?:.[^@.]+)+>?s*$/
x extension # User extension type. See EXTENSIONS below.
Basicly a blending of the CGI and Getopt::Long modules, and requires the CGI module to function.
The basic concept of this module is to combine the best features of the CGI and Getopt::Long modules. The CGI module is great for parsing, building, and rebuilding forms, however it lacks any real error checking abilitys such as misspelled form input names, the data types received from them, missing values, etc. This however, is something that the Getopt::Long module is vary good at doing. So, basicly this module is a layer that collects the data using the CGI module and passes it to routines to do type validation and name consistency checks all in one clean try/catch style block.
The syntax of GetFormData() is mostly the same as the GetOptions() of Getopt::Long, with a few exceptions (namely, the handling of exceptions) . See the VALUE TYPES section for detail of the available types, and the EXCEPTIONS section for exception handling options. If given without a type, fields are assumed to be type ":s" (optional string), which is normally correct.
If successful, GetFormData() returns the CGI object that it used to parse the data incase you want to use it for anything else, and undef otherwise.
If you only want to do value type and name validation, use CheckFormData() instead with a field=type list. -See the SYNOPSIS for an example.
<<lessSYNOPSIS
use CGI::Validate; # GetFormData() only
use CGI::Validate qw(:standard); # Normal use
use CGI::Validate qw(:subs); # Just functions
use CGI::Validate qw(:vars); # Just exception vars
## If you dont want it to check that every requested
## element arrived you can use this. But I dont recommend it
## for most users.
$CGI::Validate::Complete = 0;
## If you dont care that some fields in the form dont
## actually match what you asked for. -I dont recommend
## this unless you REALLY know what youre doing because this
## normally meens youve got typos in your HTML and we cant
## catch them if you set this.
## $CGI::Validate::IgnoreNonMatchingFields = 1;
my $FieldOne = Default String;
my $FieldTwo = 8;
my $FieldThree = some default string;
my @FieldFour = (); ## For multi-select field
my @FieldFive = (); ## Ditto
my $EmailAddress= ;
## Try...
my $Query = GetFormData (
FieldOne=s => $FieldOne, ## Required string
FieldTwo=i => $FieldTwo, ## Required int
FieldThree => $FieldThree, ## Auto converted to the ":s" type
FieldFour=s => @FieldFour, ## Multi-select field of strings
FieldFive=f => @FieldFive, ## Multi-select field of floats
Email=e => $EmailAddress, ## Must look like an email address
) or do {
## Catch... (wouldnt you just love a case statement here?)
if (%Missing) {
die "Missing form elements: " . join ( , keys %Missing);
} elsif (%Invalid) {
die "Invalid form elements: " . join ( , keys %Invalid);
} elsif (%Blank) {
die "Blank form elements: " . join ( , keys %Blank);
} elsif (%InvalidType) {
die "Invalid data types for fields: " . join ( , keys %InvalidType);
} else {
die "GetFormData() exception: $CGI::Validate::Error";
}
};
## If you only want to check the form data, but dont want to
## have CGI::Validate set anything use this. -You still have full
## access to the data via the normal B object that is returned.
use CGI::Validate qw(CheckFormData); # not exported by default
my $Query = CheckFormData (
FieldOne=s, FieldTwo=i, FieldThree, FieldFour,
FieldFive, Email,
) or do {
... Same exceptions available as GetFormData above ...
};
## Need some of your own validation code to be used? Here is how you do it.
addExtensions (
myType => sub { $_[0] =~ /test/ },
fooBar => &fooBar,
i_modify_the_actual_data => sub {
if ($_[0] =~ /test/) { ## data validation
$_[0] = whatever; ## modify the data by alias
return 1;
} else {
return 0;
}
},
);
my $Query = GetFormData (
foo=xmyType => $foo,
bar=xfooBar => $bar,
cat=xi_modify_the_actual_data => $cat,
);
## Builtin data type checks available are:
s string # Any non-zero length value
w word # Must have at least one w char
i integer # Integer value
f float # Float value
e email # Must match m/^s*]+@[^@.]+(?:.[^@.]+)+>?s*$/
x extension # User extension type. See EXTENSIONS below.
Basicly a blending of the CGI and Getopt::Long modules, and requires the CGI module to function.
The basic concept of this module is to combine the best features of the CGI and Getopt::Long modules. The CGI module is great for parsing, building, and rebuilding forms, however it lacks any real error checking abilitys such as misspelled form input names, the data types received from them, missing values, etc. This however, is something that the Getopt::Long module is vary good at doing. So, basicly this module is a layer that collects the data using the CGI module and passes it to routines to do type validation and name consistency checks all in one clean try/catch style block.
The syntax of GetFormData() is mostly the same as the GetOptions() of Getopt::Long, with a few exceptions (namely, the handling of exceptions) . See the VALUE TYPES section for detail of the available types, and the EXCEPTIONS section for exception handling options. If given without a type, fields are assumed to be type ":s" (optional string), which is normally correct.
If successful, GetFormData() returns the CGI object that it used to parse the data incase you want to use it for anything else, and undef otherwise.
If you only want to do value type and name validation, use CheckFormData() instead with a field=type list. -See the SYNOPSIS for an example.
Download (0.010MB)
Added: 2006-10-06 License: Perl Artistic License Price:
1113 downloads
Diplomacy Automated Email Judge 1.7.6
Njudge is an automated judge for Diplomacy games, based on Ken Lowe software. more>>
Njudge is an automated judge for Diplomacy games, based on Ken Lowe software.
Installation:
1. Create a system user account (i.e. judge) and its home directory
(i.e. /home/judge) It is recommended to lock the password for this
account as you should never need to login as this user.
2. `cd to the directory containing the packages source code and type
`./configure to configure the package for your system. If youre
using `csh on an old version of System V, you might need to type
`sh ./configure instead to prevent `csh from trying to execute
`configure itself.
By default it will set up the judge in /home/judge as user judge with
an email address of judge@localhost and sendmail in /usr/sbin.
If you chose a different user and directory in step 1, or if judge
email should come from a different domain, you can give the configure
script flags to override the defaults. The flags are:
--with-dir=DIR
--with-user=NAME
--with-domain=DOMAIN
--with-sendmail=SENDMAIL
for example to set up the judge in /home/jaldhar/dip as user
jaldhar and email judge@braincells.com and sendmail in /usr/ucb, you
would do:
./configure --with-dir=/home/jaldhar/dip --with-user=jaldhar --with-domain=braincells.com --with-sendmail=/usr/ucb
There are many other flags you can give (type ./configure --help
for a full list) but these are the main ones youre likely to use.
Running `configure takes awhile. While running, it prints some
messages telling which features it is checking for.
3. Type `make to compile the package.
4. If this is a new install:
Type `make install to install the programs, any data files and
documentation. You will have to edit a few configuration files
before the judge will become operation.
If this is an upgrade from an older version;
Type make upgrade to install the new programs only.
*Note* compiled programs will not be stripped of debug and other extra
information. If you want to make compiled programs a little smaller,
you can type make install-strip or make upgrade-strip instead. This
may give a few harmless errors (when it tries to strip scripts) but you
can ignore them.
If you just want to rebuild the map files (because e.g. you added a new
variant,) type make remap.
5. You can remove the program binaries and object files from the
source code directory by typing `make clean. To also remove the
files that `configure created (so you can compile the package for
a different kind of computer), type `make distclean.
Enhancements:
- Major bugfixes
<<lessInstallation:
1. Create a system user account (i.e. judge) and its home directory
(i.e. /home/judge) It is recommended to lock the password for this
account as you should never need to login as this user.
2. `cd to the directory containing the packages source code and type
`./configure to configure the package for your system. If youre
using `csh on an old version of System V, you might need to type
`sh ./configure instead to prevent `csh from trying to execute
`configure itself.
By default it will set up the judge in /home/judge as user judge with
an email address of judge@localhost and sendmail in /usr/sbin.
If you chose a different user and directory in step 1, or if judge
email should come from a different domain, you can give the configure
script flags to override the defaults. The flags are:
--with-dir=DIR
--with-user=NAME
--with-domain=DOMAIN
--with-sendmail=SENDMAIL
for example to set up the judge in /home/jaldhar/dip as user
jaldhar and email judge@braincells.com and sendmail in /usr/ucb, you
would do:
./configure --with-dir=/home/jaldhar/dip --with-user=jaldhar --with-domain=braincells.com --with-sendmail=/usr/ucb
There are many other flags you can give (type ./configure --help
for a full list) but these are the main ones youre likely to use.
Running `configure takes awhile. While running, it prints some
messages telling which features it is checking for.
3. Type `make to compile the package.
4. If this is a new install:
Type `make install to install the programs, any data files and
documentation. You will have to edit a few configuration files
before the judge will become operation.
If this is an upgrade from an older version;
Type make upgrade to install the new programs only.
*Note* compiled programs will not be stripped of debug and other extra
information. If you want to make compiled programs a little smaller,
you can type make install-strip or make upgrade-strip instead. This
may give a few harmless errors (when it tries to strip scripts) but you
can ignore them.
If you just want to rebuild the map files (because e.g. you added a new
variant,) type make remap.
5. You can remove the program binaries and object files from the
source code directory by typing `make clean. To also remove the
files that `configure created (so you can compile the package for
a different kind of computer), type `make distclean.
Enhancements:
- Major bugfixes
Download (0.71MB)
Added: 2006-08-25 License: Other/Proprietary License Price:
1163 downloads
Sendmail Sender Address Validator 1.4.0
smf-sav is a lightweight, fast and reliable Sendmail milter that implements a real-time Sender e-Mail Address Verification. more>>
smf-sav is a lightweight, fast and reliable Sendmail milter that implements a real-time Sender e-Mail Address Verification technology. This technology can stop some kind of SPAM with a spoofed senders e-Mail address.
Also it implements a real-time Recipient e-Mail Address Verification technology. It can be useful if your machine is a backup MX for the recipients domain or if your machine forwards all e-Mail messages for your domain to another (presumably internal) e-Mail server. Sendmail Sender Address Validator is written in C.
Main features:
- friendly hosts/networks whitelist;
- SMTP AUTH support;
- strictly RFC-2821 compliant MX callback engine;
- tolerance against non RFC-2821 compliant e-Mail servers;
- blocking of e-Mail messages with a spoofed senders e-Mail address;
- recipients e-Mail address verification with an authoritative e-Mail store in gateway mode;
- slow down of recipients e-Mail address brute force attacks in gateway mode.
Enhancements:
- Whitelisting by a PTR (reverse DNS) record was implemented.
- Whitelisting by an envelope recipient email address was implemented.
- The option to ignore tempfailed results of SAV was implemented.
- The option to refuse email messages from systems that dont accept the null reverse-path was implemented.
- Tempfail and fail results TTL settings were segregated.
- Progressive slowdown of brute force attacks on a recipients email address was implemented.
<<lessAlso it implements a real-time Recipient e-Mail Address Verification technology. It can be useful if your machine is a backup MX for the recipients domain or if your machine forwards all e-Mail messages for your domain to another (presumably internal) e-Mail server. Sendmail Sender Address Validator is written in C.
Main features:
- friendly hosts/networks whitelist;
- SMTP AUTH support;
- strictly RFC-2821 compliant MX callback engine;
- tolerance against non RFC-2821 compliant e-Mail servers;
- blocking of e-Mail messages with a spoofed senders e-Mail address;
- recipients e-Mail address verification with an authoritative e-Mail store in gateway mode;
- slow down of recipients e-Mail address brute force attacks in gateway mode.
Enhancements:
- Whitelisting by a PTR (reverse DNS) record was implemented.
- Whitelisting by an envelope recipient email address was implemented.
- The option to ignore tempfailed results of SAV was implemented.
- The option to refuse email messages from systems that dont accept the null reverse-path was implemented.
- Tempfail and fail results TTL settings were segregated.
- Progressive slowdown of brute force attacks on a recipients email address was implemented.
Download (0.015MB)
Added: 2006-10-30 License: GPL (GNU General Public License) Price:
1099 downloads
Easiest Validate On Submit 1.0
Easiest Validate On Submit project enables Web developers to validate any number of form fields. more>>
Easiest Validate On Submit project enables Web developers to validate any number of form fields, client side (in Javascript), with only one line of code per HTML page.
Main features:
- It requires only 1 line of javascript per html file, to validate any number of fields in any number of forms.
- The script detects whether you have a div to display errors. If you havent, it puts messages in alert boxes.
- Evos supports styling both the input widgets and the labels upon validation errors.
- Which fields to validate, and which validation (required field, email, numeric) to use, is completely controlled through CSS classes.
- Pluggable custom validation per field, with minimal amounts of code.
- Messages are located in language files, so its easy to display messages in your native language.
- Everything can be styled using CSS.
<<lessMain features:
- It requires only 1 line of javascript per html file, to validate any number of fields in any number of forms.
- The script detects whether you have a div to display errors. If you havent, it puts messages in alert boxes.
- Evos supports styling both the input widgets and the labels upon validation errors.
- Which fields to validate, and which validation (required field, email, numeric) to use, is completely controlled through CSS classes.
- Pluggable custom validation per field, with minimal amounts of code.
- Messages are located in language files, so its easy to display messages in your native language.
- Everything can be styled using CSS.
Download (0.014MB)
Added: 2006-07-27 License: BSD License Price:
1185 downloads
Params::Validate 0.88
Params::Validate is a Perl module to validate method/function parameters. more>>
Params::Validate is a Perl module to validate method/function parameters.
SYNOPSIS
use Params::Validate qw(:all);
# takes named params (hash or hashref)
sub foo
{
validate( @_, { foo => 1, # mandatory
bar => 0, # optional
}
);
}
# takes positional params
sub bar
{
# first two are mandatory, third is optional
validate_pos( @_, 1, 1, 0 );
}
sub foo2
{
validate( @_,
{ foo =>
# specify a type
{ type => ARRAYREF },
bar =>
# specify an interface
{ can => [ print, flush, frobnicate ] },
baz =>
{ type => SCALAR, # a scalar ...
# ... that is a plain integer ...
regex => qr/^d+$/,
callbacks =>
{ # ... and smaller than 90
less than 90 => sub { shift() < 90 },
},
}
}
);
}
sub with_defaults
{
my %p = validate( @_, { foo => 1, # required
# $p{bar} will be 99 if bar is not
# given. bar is now optional.
bar => { default => 99 } } );
}
sub pos_with_defaults
{
my @p = validate_pos( @_, 1, { default => 99 } );
}
sub sets_options_on_call
{
my %p = validate_with
( params => @_,
spec => { foo => { type SCALAR, default => 2 } },
normalize_keys => sub { $_[0] =~ s/^-//; lc $_[0] },
);
}
The Params::Validate module allows you to validate method or function call parameters to an arbitrary level of specificity. At the simplest level, it is capable of validating the required parameters were given and that no unspecified additional parameters were passed in.
It is also capable of determining that a parameter is of a specific type, that it is an object of a certain class hierarchy, that it possesses certain methods, or applying validation callbacks to arguments.
<<lessSYNOPSIS
use Params::Validate qw(:all);
# takes named params (hash or hashref)
sub foo
{
validate( @_, { foo => 1, # mandatory
bar => 0, # optional
}
);
}
# takes positional params
sub bar
{
# first two are mandatory, third is optional
validate_pos( @_, 1, 1, 0 );
}
sub foo2
{
validate( @_,
{ foo =>
# specify a type
{ type => ARRAYREF },
bar =>
# specify an interface
{ can => [ print, flush, frobnicate ] },
baz =>
{ type => SCALAR, # a scalar ...
# ... that is a plain integer ...
regex => qr/^d+$/,
callbacks =>
{ # ... and smaller than 90
less than 90 => sub { shift() < 90 },
},
}
}
);
}
sub with_defaults
{
my %p = validate( @_, { foo => 1, # required
# $p{bar} will be 99 if bar is not
# given. bar is now optional.
bar => { default => 99 } } );
}
sub pos_with_defaults
{
my @p = validate_pos( @_, 1, { default => 99 } );
}
sub sets_options_on_call
{
my %p = validate_with
( params => @_,
spec => { foo => { type SCALAR, default => 2 } },
normalize_keys => sub { $_[0] =~ s/^-//; lc $_[0] },
);
}
The Params::Validate module allows you to validate method or function call parameters to an arbitrary level of specificity. At the simplest level, it is capable of validating the required parameters were given and that no unspecified additional parameters were passed in.
It is also capable of determining that a parameter is of a specific type, that it is an object of a certain class hierarchy, that it possesses certain methods, or applying validation callbacks to arguments.
Download (0.078MB)
Added: 2007-04-11 License: Perl Artistic License Price:
927 downloads
Email::AutoReply 1.02
Email::AutoReply is a Perl extension for writing email autoresponders. more>>
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.
<<lessSYNOPSIS
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.
Download (0.015MB)
Added: 2007-04-19 License: Perl Artistic License Price:
927 downloads
Postaci Webmail 2.0.1
Postaci Webmail is a multiplatform PHP webmail software. more>>
Postaci (Turkish word for Postman) is a multiplatform PHP webmail software which is database independent, IMAP/POP3, multilanguage(32 languages) and fully MIME compatible. While using POP3 mode to fetch messages it uses database fields to simulate IMAP folders, on which you can save, move, delete,read e-mail.
It is a easy to set up, really secure environment and been downloaded by more than hundred thousand users all around the world. It also is bundled with a simple adressbook, a notebook, a bookmark manager application.
Postaci includes multidomain(virtual) support. Domains are stored in a DB table and all users must be linked to a domain. It can be done at tblDomains and tblUsers tables at the database. If you have a single domain on your server you won t need to do this. There must be at least one domain at the database and its index should be 1. This is the default domain for any user. You can change your default domain at the tblDomain.sql file at the queries folder.
Enhancements:
- SMTP authentication for those who need to authenticate to send email.
- An Email Address field in Preferences allows you to manually set your From: email address.
- A problem in moving messages when using IMAP has been fixed.
<<lessIt is a easy to set up, really secure environment and been downloaded by more than hundred thousand users all around the world. It also is bundled with a simple adressbook, a notebook, a bookmark manager application.
Postaci includes multidomain(virtual) support. Domains are stored in a DB table and all users must be linked to a domain. It can be done at tblDomains and tblUsers tables at the database. If you have a single domain on your server you won t need to do this. There must be at least one domain at the database and its index should be 1. This is the default domain for any user. You can change your default domain at the tblDomain.sql file at the queries folder.
Enhancements:
- SMTP authentication for those who need to authenticate to send email.
- An Email Address field in Preferences allows you to manually set your From: email address.
- A problem in moving messages when using IMAP has been fixed.
Download (0.20MB)
Added: 2006-10-01 License: GPL (GNU General Public License) Price:
1122 downloads
Disposable Temporary E-mail 1.1.0
Disposable Temporary E-mail project provides the user with disposable e-mail addresses which expire after a certain time. more>>
Disposable Temporary E-mail project provides the user with disposable e-mail addresses which expire after a certain time. The user can read and reply to e-mails that are sent to the temporary e-mail address within the given time frame.
Main features:
- Users can generate e-mail addresses
- Users can see their incoming e-mails
- Users can reply to e-mails
- Completely template driven
- Installation routine
How the script works:
With a click on a button the user generates a new e-mail address. That address will be stored in the database along with its creation time. The e-mail address is assigned to the user by a session cookie.
The user then uses the e-mail for any purpose where an e-mail address is required. Most commonly that will be some kind of registration.
In the background the script checks continuously for arriving e-mails. Once an e-mail that has been sent to a generated e-mail address arrives, the script displays it.
<<lessMain features:
- Users can generate e-mail addresses
- Users can see their incoming e-mails
- Users can reply to e-mails
- Completely template driven
- Installation routine
How the script works:
With a click on a button the user generates a new e-mail address. That address will be stored in the database along with its creation time. The e-mail address is assigned to the user by a session cookie.
The user then uses the e-mail for any purpose where an e-mail address is required. Most commonly that will be some kind of registration.
In the background the script checks continuously for arriving e-mails. Once an e-mail that has been sent to a generated e-mail address arrives, the script displays it.
Download (MB)
Added: 2007-05-16 License: Free for non-commercial use Price:
903 downloads
Net::Amazon::Validate::ItemSearch 0.39
Net::Amazon::Validate::ItemSearch is a Perl module to validate ItemSearch requests. more>>
Net::Amazon::Validate::ItemSearch is a Perl module to validate ItemSearch requests.
SYNOPSIS
Net::Amazon::Validate::ItemSearch;
my $valid = Net::Amazon::Validate::ItemSearch::factory(search_index => Actor);
my $option = $itemsearch_valid->user_or_default($input);
my $default = $itemsearch_valid->default();
Net::Amazon::Validate::ItemSearch is a class used to verify ItemSearch operation based on the current version of the WSDL and locale. For example if an Artist search is executed the user can search against Classical, Merchants, or Music.
METHODS
factory(search_index => type)
Constructs a new Net::Amazon::Validate::ItemSearch object, used to validate user input for a SearchIndex. Valid types include Actor, Artist, AudienceRating, Author Brand, BrowseNode, City, Composer, Condition, Conductor, Count, Cuisine, DeliveryMethod, Director, ISPUPostalCode, ItemPage, Keywords, MPAARating, Manufacturer, MaximumPrice, MerchantId, MinimumPrice, MusicLabel, Neighborhood, Orchestra, Power, Publisher, Sort, TextStream and Title. Which departments these search indexes are valid for is dependent upon locale.
default()
Return the default value for a given SearchIndex. Default are determined in order of preference and existence from the following list: Books, Music, DVD, Software. If none of those items are valid for a given SearchIndex then the first valid department of said SearchIndex is used.
user_or_default( $input )
If user input is specified it validates the input, and return it, otherwise it returns the default value for the SearchIndex.
<<lessSYNOPSIS
Net::Amazon::Validate::ItemSearch;
my $valid = Net::Amazon::Validate::ItemSearch::factory(search_index => Actor);
my $option = $itemsearch_valid->user_or_default($input);
my $default = $itemsearch_valid->default();
Net::Amazon::Validate::ItemSearch is a class used to verify ItemSearch operation based on the current version of the WSDL and locale. For example if an Artist search is executed the user can search against Classical, Merchants, or Music.
METHODS
factory(search_index => type)
Constructs a new Net::Amazon::Validate::ItemSearch object, used to validate user input for a SearchIndex. Valid types include Actor, Artist, AudienceRating, Author Brand, BrowseNode, City, Composer, Condition, Conductor, Count, Cuisine, DeliveryMethod, Director, ISPUPostalCode, ItemPage, Keywords, MPAARating, Manufacturer, MaximumPrice, MerchantId, MinimumPrice, MusicLabel, Neighborhood, Orchestra, Power, Publisher, Sort, TextStream and Title. Which departments these search indexes are valid for is dependent upon locale.
default()
Return the default value for a given SearchIndex. Default are determined in order of preference and existence from the following list: Books, Music, DVD, Software. If none of those items are valid for a given SearchIndex then the first valid department of said SearchIndex is used.
user_or_default( $input )
If user input is specified it validates the input, and return it, otherwise it returns the default value for the SearchIndex.
Download (0.15MB)
Added: 2007-03-09 License: Perl Artistic License Price:
960 downloads
Email::Store 0.24
Email::Store is a framework for database-backed email storage. more>>
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.
<<lessSYNOPSIS
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.
Download (0.027MB)
Added: 2006-06-28 License: Perl Artistic License Price:
1215 downloads
Jwapmail 1.1
Jwapmail is opensource wap based email client written using PHP. more>>
Jwapmail is opensource wap based email client written using PHP. Jwapmail has been tested at SonyEriccson T28, and Siemens SL45. Any volutenter of testers are welcome.
Main features:
- 1. Email client standard functions
- Jwapmail support the email client standard functions:
- Compose, Reply, Forward, and Folder.
-
- 2. Message Filter (Not finish yet)
- Message Filter is allow user to manage messages in the folder.
-
- 3. User Profile (Not finish yet)
- Allow user to set user profiles standard such as, Name and email address.
-
- 4. Paging (to overcome content size limitaion)
- Due to the vary limitation of content size in WAP GATEWAY, Jwapmail
- deliver content with size not exceded the maximum size (kbytes) where maximum size
- is a variable set in file configuration.
- If the content of message have the size exceed the maximum bytes
- Jwapmail split into several page and deliver each page with paging navigation link
<<lessMain features:
- 1. Email client standard functions
- Jwapmail support the email client standard functions:
- Compose, Reply, Forward, and Folder.
-
- 2. Message Filter (Not finish yet)
- Message Filter is allow user to manage messages in the folder.
-
- 3. User Profile (Not finish yet)
- Allow user to set user profiles standard such as, Name and email address.
-
- 4. Paging (to overcome content size limitaion)
- Due to the vary limitation of content size in WAP GATEWAY, Jwapmail
- deliver content with size not exceded the maximum size (kbytes) where maximum size
- is a variable set in file configuration.
- If the content of message have the size exceed the maximum bytes
- Jwapmail split into several page and deliver each page with paging navigation link
Download (0.091MB)
Added: 2006-06-12 License: GPL (GNU General Public License) Price:
1231 downloads
Secleted [ 0 ] software to compare
Copyright Notice:
Software piracy is theft, Using crack, password, serial numbers, registration codes, key generators is illegal and prevent future software development. The above validate email address search only lists software in full, demo and trial versions for free download. Download links are directly from our mirror sites or publisher sites, torrent files or links from rapidshare.com, yousendit.com or megaupload.com are not allowed