Free mail sendeasy 1.2 software for linux

Mail::Send is a simple electronic mail interface.

SYNOPSIS:

require Mail::Send;

$msg = new Mail::Send;

$msg = new Mail::Send Subject=>example subject, To=>timbo;

$msg->to(user@host);
$msg->to(user@host, user2@example.com);
$msg->subject(example subject);
$msg->cc(user@host);
$msg->bcc(someone@else);

$msg->set($header, @values);
$msg->add($header, @values);
$msg->delete($header);

# Launch mailer and set headers. The filehandle returned
# by open() is an instance of the Mail::Mailer class.
# Arguments to the open() method are passed to the Mail::Mailer
# constructor.

$fh = $msg->open; # some default mailer
# $fh = $msg->open(sendmail); # explicit

print $fh "Body of message";

$fh->close; # complete the message and send it

$fh->cancel; # not yet implemented

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 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::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::QmailRemoteXS is a lightweight C-code (XS) SMTP send function based on Qmails qmail-remote.

SYNOPSIS

use Mail::QmailRemoteXS;

$ret = Mail::QmailRemoteXS::mail($to_domain,$from_address,$to_address,$msg,$helo,$net_timeout,$net_timeoutconnect);

This module provides a single function mail that sends an email via SMTP. It uses an XS implementation of Qmails qmail-remote binary written in C so is very lightweight and fast (compared to Net::SMTP).

The difference between Mail::QmailRemote (IKEBE Tomohiro) and Mail::QmailRemoteXS is that the former requires the qmail package to be installed and simply invokes a wrapper around the qmail-remote binary for each send. This module statically links code based on qmail-remote and has no dependencies other that a working resolver.

FUNCTIONS

mail

$ret = Mail::QmailRemoteXS::mail($to_domain,$from_address,$to_address,$msg,$helo,$net_timeout,$net_timeoutconnect);

Send an email message $msg (which includes rfc822 headers) to $to_address from $from_address using $helo as the SMTP HELO greeting. $net_timeoutconnect is for the initial SMTP connection and $net_timeout is for the wait time for SMTP responses.
See Qmails qmail-remote manpage for more information and details on the return value $ret.

Mail::LMLM::Render is a Perl module for rendering backend for LMLM.

SYNOPSIS

use Mail::LMLM::Render::HTML;

open O, ">out.html";
my $r = Mail::LMLM::Render::HTML->new(*O);

$r->start_document("My Document", "Head Title");

$r->start_section("Google", { title_url => "http://www.google.com/", });

$r->para("Google is a very nice search engine.");
$r->end_section();
$r->end_document();
close(O);

The Mail::LMLM::Render is a base class for rendering hypertext. It is used by LMLM extensively as a thin layer around the actual format.

To use it open a filehandle, and call the packages new constructor with a refernce to the filehandle. Afterwards call the start_document method (documented below), and when youre done call the end_document method. For each section call start_section and end_section explicitly.