Free mail sendmail software for linux

Sendmail application is a Mail Transfer Agent, which is the program that moves mail from one machine to another.

Sendmail implements a general internetwork mail routing facility, featuring aliasing and forwarding, automatic routing to network gateways, and flexible configuration.

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

Sendmail-Jilter is an Open Source implementation of the Sendmail milter protocol, for implementing milters in Java that can interface with the Sendmail MTA.
Enhancements:
New Features:
- Added JilterHandlerAdapter. Thanks to Neil Aggarwal (neil@JAMMConsulting.com).
Changes:
- Updated docs for return value from JilterHandler.connect to reflect the fact that the MTA doesnt listen to anything other than SMFIS_ values. Thanks to Neil Aggarwal (neil@JAMMConsulting.com).
- Refactored SimpleHandler in the test cases to use JilterHandlerAdapter.

SPF Sendmail milter is a Sendmail filter that implements the Sender Policy Framework technology with help of libSPF2 library.
It checks SPF records to make sure that the email is authorized by the domain name that it is coming from. This prevents email forgery, commonly used by spammers, scammers and email viruses/worms.
It can reject messages on SPF hardfail result. Also it adds the standard Received-SPF header with SPF results to the scanned messages.
This filter aims to be lightweight, reliable, and simple. Its written in C. Although this filter is a stable itself, libSPF2 is a beta software and can be unstable. It can affect to the filter stability. Please, use it in the production environment with caution.
Main features:
- It has a hosts/networks whitelist;
- It can reject messages on SPF hardfail result;
- It can add the standard header with SPF results;
- It logs all filter activities to syslog.
- Small code (does not exceed 320 lines);
- Fast work;
- Stability (production quality);
- Low resources are required;
- No temporary files are created.
Enhancements:
- Cosmetic enhancements were made.

Sendmail::AccessDB is an interface to the Sendmail access.db list.

SYNOPSIS

use Sendmail::AccessDB qw(spam_friend whitelisted);
$friend_or_hater = spam_friend(user@example.com);
$whitelisted = whitelisted(sender@example.com);

This module is designed so that users of the Sendmail::Milter module (or other Sendmail programmers) can ascertain if a user has elected to whitelist themselves as a "spam friend" (where there should be no spam filtering on mail to them) or, where spam-filtering is not the default, but an option, where certain receipients have been labeled as "spam haters"

USAGE

use Sendmail::AccessDB qw(spam_friend);
$friend_or_hater = spam_friend(user@example.com);

Ordinarily, this will look for such things as "Spam:user@example.com", "Spam:user@", etc., in the /etc/mail/access.db file. There is an optional second argument "Category", which could be used if you wanted to enable specific checks, for example, if you wanted to customize down to a per-check basis, you might use:

$rbl_friend_or_hater = spam_friend(user@example.com,
qualifier => maps_rbl);
$dul_friend_or_hater = spam_friend(user@example.com,
qualifier => maps_dul);

Caution should be taken when defining your own categories, as they may inadvertantly conflict with Sendmail-defined categories.

use Sendmail::AccessDB qw(whitelisted);
$whitelisted = whitelisted(sender@example.com);
$whitelisted_host = whitelisted(foo.example.com);
$whitelisted_addr = whitelisted(192.168.1.123);

Would check for appropriate whitelisting entries in access.db. Some lookups might be ambiguous, for example:

$whitelisted = whitelisted(foobar);

where it is hard to know if that is supposed to be a hostname, or a sender. whitelisted() accepts the type argument, such as:

$whitelisted = whitelisted(foobar,type=>hostname);
$whitelisted = whitelisted(postmaster,type=>mail);

Its also possible to feed the qualifier argument, if necessary, for example, to do:

$whitelisted = whitelisted(host.example.com,type=>hostname,
qualifier => Connect);

which would check to see if this host has an OK flag set for the Connect qualifier.

There is also the generic "lookup", which, at its simplest, takes a single argument:

$rc = lookup(host.example.com);

will do a lookup on host.example.com. But if you wanted to pay attention to parent-domains, you might do:

$rc = lookup(host.example.com, type=>hostname);

but if you wanted to find out if host.example.com, or any of its parent domains (example.com and com), had a value in the "MyQual" qualifier, you might do:
$rc = lookup(host.example.com,type=>hostname,qualifier=>MyQual);
which would look up, in order MyQual:host.example.com, MyQual:example.com, and MyQual:com, returning the first (most specific) one found.

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 Notification is a status icon (aka tray icon) that informs you if you have new mail.
Mail Notification works with system trays implementing the freedesktop.org System Tray Specification, such as the GNOME Panel Notification Area, the Xfce Notification Area and the KDE System Tray.
Main features:
- multiple mailbox support
- mbox, MH, Maildir, Sylpheed, POP3, IMAP and Gmail support
- SASL authentication support
- APOP authentication support
- SSL/TLS support
- automatic detection of mailbox format
- immediate notification (the status icon is updated within seconds after a mailbox changes)
- a mail summary
- HIG 2.0 compliance.