Free mail sendeasy software for linux

Mail::SendEasy can send plain/html e-mails through SMTP servers (platform independent). Supports SMTP authentication and attachments.

This modules will send in a easy way e-mails, and doesnt have dependencies. Soo, you dont need to install libnet.
It supports SMTP authentication and attachments.

USAGE:

OO

use Mail::SendEasy ;

my $mail = new Mail::SendEasy(
smtp => localhost ,
user => foo ,
pass => 123 ,
) ;

my $status = $mail->send(
from => sender@foo.com ,
from_title => Foo Name ,
reply => re@foo.com ,
error => error@foo.com ,
to => recp@domain.foo ,
cc => recpcopy@domain.foo ,
subject => "MAIL Test" ,
msg => "The Plain Msg..." ,
html => "The HTML Msg..." ,
msgid => "0101" ,
) ;

if (!$status) { print $mail->error ;}

STRUCTURED

use Mail::SendEasy ;

my $status = Mail::SendEasy::send(
smtp => localhost ,
user => foo ,
pass => 123 ,
from => sender@foo.com ,
from_title => Foo Name ,
reply => re@foo.com ,
error => error@foo.com ,
to => recp@domain.foo ,
cc => recpcopy@domain.foo ,
subject => "MAIL Test" ,
msg => "The Plain Msg..." ,
html => "The HTML Msg..." ,
msgid => "0101" ,
) ;

if (!$status) { Mail::SendEasy::error ;}

Mail Avenger is a highly-configurable, MTA-independent SMTP server daemon. Mail Avenger lets users run messages through filters like ClamAV and SpamAssassin during SMTP transactions, so the server can reject mail before assuming responsibility for its delivery.
Other unique features include TCP SYN fingerprint and network route recording, verification of sender addresses through SMTP callbacks, SPF (sender policy framework) as a general policy language, qmail-style control over both SMTP-level behavior and local delivery of extension addresses, mail-bomb protection, integration with kernel firewalls, and more.
Enhancements:
- Several minor bugs were fixed.
- The SMTPCB configuration directive was changed to give more options.
- An InsecureSASL configuration option was added by request of users.

Mail::Summary is a Perl module that can scan read your mail!

SYNOPSIS

my $ms = Mail::Summary->new({ maildir => /home/mwk/Maildir });

my @mail_summaries = $ms->summaries;

Too busy to read your mail? Subscribe to too many mailing lists? Take two folders into the shower? Well, for the busy on the go geek of today, here is the answer! Get all your messages summarised, to save you having to read them, or to read them by which summary looks better!

new

my $ms = Mail::Summary->new({ maildir => /home/mwk/Maildir });

This will make a new Mail::Summary object.

maildir

my $maildir = $ms->maildir;

This is the mail directory as defined by the user.

summaries

my @mail_summaries = $ms->summaries;

This will return a list, with every entry in the list being a summary of an individual message.

Mail::Field is a base class for manipulation of mail header fields.

SYNOPSIS

use Mail::Field;

$field = Mail::Field->new(Subject, some subject text);
print $field->tag,": ",$field->stringify,"n";

$field = Mail::Field->subject(some subject text);

Mail::Field is a base class for packages that create and manipulate fields from Email (and MIME) headers. Each different field will have its own sub-class, defining its own interface.

This document describes the minimum interface that each sub-class should provide, and also guidlines on how the field specific interface should be defined.

Mail::Abuse is a Perl module that helps parse and respond to miscellaneous abuse complaints.

SYNOPSIS
use Mail::Abuse;

This module and the accompaining software can be used to automatically parse and respond to various formats of abuse complaints. This software is geared towards abuse desk administrators who need sophisticated tools to deal with the complains.
Mail::Abuse is actually a bundle of modules that provide various services. This documentation provides a general description of the functions provided by each one. No useful code is provided in the Mail::Abuse module, appart from this documentation and the version information below.

The following classes/packages are part of this distribution.

Mail::Abuse::Report

A report is a collection made of the received report and ths incidents it describes. See Mail::Abuse::Report for more information.

Mail::Abuse::Incident

An incident is each of the individual policy violations that are presented in a given report. A report should have at least, one incident. See Mail::Abuse::Incident for more information.

Mail::Abuse::Processor

Once the reports are analyzed and its incidents are extracted, you will want to do something with the information. This is the job of a processor. See Mail::Abuse::Processor for more information.

Mail::Abuse::Reader

Abuse reports can be fetched from a variety of places and through various protocols. This is what readers do: Read a report. See Mail::Abuse::Reader for more information.

Mail::Abuse::Filter

An abuse report might contain incidents that are not to be handled by us. A filter remove incidents that does not belong to our network. See Mail::Abuse::Filter for more information.

All of the modules take a lot of their configuration information from a specially formatted file.

This distribution also includes a number of scripts. See the bin/ directory for more information.

Mail::Client::Yahoo is a Perl module with programmatically access Yahoos web-based email.

SYNOPSIS

use Mail::Client::Yahoo;

$y = Mail::Client::Yahoo->login(
username => bob,
password => secret,
secure => 1, # for the paranoid and patient
);

$y->select_folder(Inbox);

$m = $y->message(0); # is equivalent to...
@ids = $y->message_list();
$y->message($id[0]);

$y->delete_message(0);

$y->logout();

This module allows you to access your web-based Yahoo Mail account programatically. Similar in function to Mail::Webmail::Yahoo, this module is more geared towards manipulation of individual messages, rather than simple bulk download. This module is also probably more reliable than Mail::Webmail::Yahoo, as well.

Mail::Digest::Tools is a Perl module that has tools for digest versions of mailing lists.

SYNOPSIS

use Mail::Digest::Tools qw(
process_new_digests
reprocess_ALL_digests
reply_to_digest_message
repair_message_order
consolidate_threads_multiple
consolidate_threads_single
delete_deletables
);
%config_in and %config_out are two configuration hashes whose setup is discussed in detail below.
process_new_digests(%config_in, %config_out);

reprocess_ALL_digests(%config_in, %config_out);

$full_reply_file = reply_to_digest_message(
%config_in,
%config_out,
$digest_number,
$digest_entry,
$directory_for_reply,
);

repair_message_order(
%config_in,
%config_out,
{
year => 2004,
month => 01,
day => 27,
}
);

consolidate_threads_multiple(
%config_in,
%config_out,
$first_common_letters, # optional integer argument; defaults to 20
);

consolidate_threads_single(
%config_in,
%config_out,
[
first_dummy_file_for_consolidation.thr.txt,
second_dummy_file_for_consolidation.thr.txt,
],
);

delete_deletables(%config_out);

Mail::Digest::Tools provides useful tools for processing mail which an individual receives in a daily digest version from a mailing list. Digest versions of mailing lists are provided by a variety of mail processing programs and by a variety of list hosts. Within the Perl community, digest versions of mailing lists are offered by such sponsors as Active State, Sourceforge, Yahoo! Groups and London.pm. However, you do not have to be interested in Perl to make use of Mail::Digest::Tools. Mail from any of the thousands of Yahoo! Groups, for example, may be processed with this module.

If, when you receive e-mail from the digest version of a mailing list, you simply read the digest in an e-mail client and then discard it, you may stop reading here. If, however, you wish to read or store such mail by subject, read on. As printed in a normal web browser, this document contains 40 pages of documentation. You are urged to print this documentation out and study it before using this module.

To understand how to use Mail::Digest::Tools, we will first take a look at a typical mailing list digest. We will then sketch how that digest looks once processed by Mail::Digest::Tool. We will then discuss Mail::Digest::Tools exportable functions. Next, we will study how to prepare the two configuration hashes which hold the configuration data. Finally, we will provide some tips for everyday use of Mail::Digest::Tools.

Mail::Summary::Tools are tools for mailing list summarization.



SYNOPSIS

# create a summary from anything Mail::Box can open.
# you may also programatically create summary objects and serialize
# them if you dont have the threads in a standard mail format.

% mailsum create --dates --posters --clean -i foo.mbox -o summary.yaml


# edit the text in your editor, if you dont like YAML files

% mailsum edit --skip --dates --posters --links --archive gmane summary.yaml


# create pretty outputs

% mailsum totext --shorten -a google summary.yaml > summary.txt
% mailsum tohtml --archive google summary.yaml > summary.html

This distribution contains numerous classes useful for creating summaries, and an App::Cmd based frontend to those classes.
The main usage is illustrated in the "SYNOPSIS" section.