Free sendmail 0.79 software for linux

usendmail is a replacement for the sendmail program in the qmail package.
Nomenclatura:
- usendmail is usendmail
- qsendmail is the qmail sendmail clone
- sendmail is plain old sendmail (getroot)
Enhancements:
- Adds more sendmail options (-G, -L, -X).
- the -f option now also influences the generation of the "from" header field, unless its already there or the QMAILHOST or QMAILUSER environment variables are set.

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.

PerlSendmail is a small script to imitate having sendmail installed.
If you have scripts that require SendMail for sending emails, but do not want to install sendmail on your server then you can use this wrapper instead.
This simple Perl script will send email by connecting to a user specified SMTP server directly. This means that no queue daemons or directories are needed.
If the SMTP server can not be reached then the email will be discarded.
Main features:
- Suitable for use in a chroot environment
- Supports the following sendmail command line options:
-f
-F
-t
- Simple installation
- Simple configuration

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.

msn2mail is a MSN-to-e-mail gateway.

For install follow these steps:
make
make install

This program needs fvhlib v2.1 or later!

Create a .msn2mailrc with:
username = your msn passport address
password = password
mailer = path to sendmail
forwardto = e-mail adres to forward to

You can have multiple forwardto-lines.

example:

username = folkert@hotmail.com
password = secret
mailer = /usr/bin/sendmail
forwardto = folkert@vanheusden.com
forwardto = flok@xs4all.nl

Net::DNS::Sendmail is a Simple Mail Transfer Mail Client with MX lookup. Which will basically act as a primitive sendmail MTA.

SYNOPSIS

use Net::DNS::Sendmail;

# Constructors
$smtp = Net::DNS::Sendmail->new();
$smtp->to("john@gmail.com, mary@yahoo.com, goliath@hotmail.com");
$smtp->from("srikanth@cpan.org");
$smtp->subject("This is the subject line.");
$smtp->data("This allows for sending single or multiple emailsn " .
directly to sendmail servers.");
$smtp->data(" This program runs directly on the public domain just like");
$smtp->data(" sendmail.");
$smtp->sendmail();

This module implements a client interface to the SMTP and EMSMTP ( as mentioned in RFC821 and RFC2821) servers which allow you to use it as a SMTP/ESMTP client. This module connects directly to Yahoo/Hotmail/Gmail servers and delivers the mail without the need for intermediate Mail Transfer Agents(MTA) like sendmail(sendmail.org).

A new Net::DNS::Sendmail object must be created with the new method. Once this has been done then the to, from, subject and data sections of an email are created with the following methods using the object.

spfmilter provides a Sender Policy Framework (SPF) milter for Sendmail.
spfmilter is a milter (sendmail mail filter) which implements the Sender Policy Framework (SPF). SPF is a strategy for preventing junk mail. The SMTP standard for email allows anyone to forge anyone elses email address.
SPF verifies that the Sender address of an email message matches (according to some policy) the client IP address that submitted it.
The idea of SPF is to prevent email forgery. Each participating site sets up a little definition of which hosts are allowed to send mail claiming to be from that site. When another site receives mail, it checks the permitted-senders definition for the originating site. If the check fails, the mail is rejected.
Setting up the permitted-senders definition is very easy, you go to the SPF Wizard and fill out a little form, then put the resulting string into your DNS records. This milter implements the second half of SPF, checking the mail you receive against other sites SPF records.
Enhancements:
- Some improvements to the redhat rcscripts. (Paul Howarth)
- Deal with the unknown-family connections which occasionally show up on some OSs, such as Solaris. (Joel Lord)