Free mta software for linux

Secure MTA is a daemon for SMTP passwords and a starter for ssmtp or msmtp.
Options:
smta [-d [-l < numer >] [-t < timer >] [-b]] | [[-e]|[-mta < mta >]] [-sock]
-d | --daemon daemon function
-l | --listen listen number [default: 2]
-t | --timer timer [default: 0=disactivated]
-b | --background background
-e | --exit close a daemon
-s | --socket unix socket [default /home/bakunin/.smta.sock]
-m | --mta msmtp|ssmtp
-h | --help this help
Usage:
smta -d -> starts as daemon, asks the password, and accepts request to unix socket.
smta -m -> connects to smta daemon, gets the password and runs the mta.
Exemple:
set to .muttrc the lines:
set sendmail="/usr/bin/smta -m ssmtp -au bakunin"
---- ~/bin/posta ----
#!/bin/bash
# download new emails:
fetchmail -a
# Set the smtp password:
smta -d -b -t 3600
# Mutt
mutt
# Close the smta
smta -e
mutt runs smta, and smta runs ssmtp -au bakunin -ap password
Enhancements:
- Man page updates and a bugfix for the Unix socket path.

SMTPGuard is a tool which controls the flow of email traversing an MTA (Mail Transfer Agent). It is designed to be used on an SMTP server for incoming mail, and currently supports postfix.
SMTPGuard was originally created to meet the needs of Internet Service Providers (ISPs). ISPs typically receive tremendous amounts of email from their local (user) network.
Within a wide variety of users, some are spammers, many unknowingly have virus infected PCs; each of these can send large quantities of mail through the ISPs SMTP (Simple Mail Transfer Protocol) servers.
This is especially a problem for ISPs who are connected to their users via high speed lines such as fiber or ADSL. SMTPGuard was developed to prevent SMTP servers from being overwhelmed by unexpected spikes in usage from specific (often malicious) users.
For a large ISP, their only problem isnt just with overloaded incoming SMTP servers. SPAM will also be queued on the outgoing server (perhaps the same server) for delivery to the Internet.
Because the mail is SPAM it will likely bounce, then double bounce putting extreme load on the outgoing server and its queue. smtpguard is designed to stop this type of extreme load by stopping floods of mail at the gate (incoming server).
SMTPGuard is point based. Each time a client connects to the SMTP server, SMTPGuard adds points according to the rules file. SMTPGuard uses information acquired during the SMTP session, adds points according to the rules file, and finally takes actions based on its settings. For example, the information below is used:
- Remote IP Address
- Character string provided by MAIL FROM command
- Character string provided by RCPT TO command
The following actions can be taken:
ok - white list
wait - delay processing
reject - reject messages
mail - send alert email to administrator
log - output message to log
delete - delete record in database
Enhancements:
- postfix/flexguard.c: remove word flexguard. use smtpguard instead. rename filename to postfix/smtpguard.c
- postfix/Makefile.am: rename flexguard -> smtpguard
- configure.in: 1.1.1
- rename FLEXGUARD_{CFLAGS,LIBS} -> SMTPGUARD_{CFLAGS,LIBS}
- smtpguard/Makefile.am,postfix/Makefile.am,test/Makefile.am: Ditto
- debian/postfix-smtpguard.files: added
- README.postfix: added

Tagspam is a program which adds the word: SPAM into the subject line of a mail message which it identifies as spam. Identification is done by tracing Received: mail headers to identify the origin. The origin is then looked up in DNS black and whitelists.

With version 0.4 CSV processing based on CSV/CSA v.1 (draft-ietf-marid-csv-csa-02) is also included ( using pyCSV.py # csv-0.3x.py David MacQuigg (c) 8/19/05 ), enabling domain owners to publish records enabling forgeries claiming mail HELO greetings misusing their domain to be rejected.

Tagspam is useful for situations where you need to filter spam to individual users and where you dont have the ability to tag the spam at the MTA (Message Transport Agent) e.g. due to virtual hosting arrangements, or because you need to use a backup MX mail relay for when your own server is down which you dont administrate yourself, to improve mail delivery.

Other situations where tagspam is useful include where you wish to test a DNS blacklist to see if it tags spam accurately, but are not willing to risk message rejection based on this blacklist.

Alternatively, if like me you receive very many spams each day, you might decide to use very low false-positive probability DNSBLs at the MTA rejection level, and more agressive DNSBLs at the tagging and filtering level in order to achieve an acceptable level of mail filtering.

You should do this only if you are willing to risk delayed viewing of occasional false positives in filtered mail directed to a spam folder which you check manually, but more occasionally and faster than messages in your normal inbox.

Tagspam is written in Python, and can be run on the Unix/Linux computer running the MTA or a machine using a mail alias or on similar machine which uses fetchmail to obtain mail from a POP server, and sendmail to distribute the mail locally.

Dbmail is the name of a group of programs that enable the possiblilty of storing and retrieving mail messages from a database. Currently PostgreSQL and MySQL can be used as database backends.
The upcoming version 2.2 that is under development also supports SQLite, an embedded SQL database system, and ldap for storing userdata. Development and support of dbmail is done by IC&S and NFG, two Dutch companies specializing in Linux development and support.
Main features:
Scalability
- Dbmail is as scalable as the database system that is used for the mail storage. In theory millions of accounts can be managed using dbmail. One could, for example, run 4 different servers with the pop3 daemon each connecting to the same database (cluster) server.
Manageability
- Dbmail is based upon a database. Dbmail can be managed by changing settings in the database (f.e. using PHP/Perl/SQL), without needing shell access.
Speed
- Dbmail uses very efficient, database specific queries for retrieving mail information. This is much faster then parsing a filesystem.
Security
- Dbmail has got nothing to do with the filesystem or interaction with other programs in the Unix environment which need special permissions. Dbmail is as secure as the database its based upon.
Flexibility
- Changes on a Dbmail system (adding of users, changing passwords etc.) are effective immediately.
How does it work?
DBMail is made up of several components. A normal MTA (Postfix, SendMail, QMail, Exim) is used for accepting messages. The MTA hands the messages over to dbmail-smtp, using a pipe interface, or dbmail-lmtpd, using LMTP (Local Mail Transport Protocol). These programs take care of delivering the message into the database. Messages can be retreived from the database using dbmail-pop3d, using the POP3 protocol, and dbmail-imapd, using the IMAP4Rev1 protocol.
The whole email is stored in the database. That includes attachments. The DBMail programs do not have to touch the filesystem to retreive or insert emails. User information is also stored in the database, so users do not need an account on the machines DBMail is running on.
Enhancements:
- This release features greatly improved handling of UTF8 email, has many fixes for IMAP protocol errors, and resolves a number of serious memory leaks.
- A new feature was added to dbmail-export to allow fine-grained message selection and post-export deletion.

PowerMail provides a redundant and distributed system for receiving and storing mail.
PowerMail is a redundant and distributed system for receiving mail via SMTP and storing it for users to access with POP. The way PowerMail works is quite unorthodox, and its design emphasizes speed and efficiency.
Modified Maildir mailboxes allow PowerMail to employ hardlinks to save diskspace and deliver messages with thousands of recipients instantly.
PowerMail can operate self-sufficiently or cooperate with a regular MTA to support mail forwarding.
Enhancements:
- fixes for older gcc compilers (Ruben dArco)
- pptool ignored SYSCONFDIR and only did /etc/powermail (Ruben dArco)
- added ldap-forwarding-attribute
- --help display was somewhat screwed (Ruben dArco)
- run-as-uid/run-as-gid broken (Ruben dArco)
- TOP cleaned up (Ruben dArco)

libESMTP is an SMTP client which manages posting (or submission of) electronic mail via a preconfigured Mail Transport Agent (MTA).
libESMTP library may be used as part of a Mail User Agent (MUA) or other program that must be able to post electronic mail but where mail functionality is not that programs primary purpose.
The availability of a reliable lightweight thread-safe SMTP client eases the task of coding for software authors thus improving the quality of the resulting code.
Main features:
- libESMTP supports many SMTP extensions, notably PIPELINING (RFC 2920), DSN (RFC 1891) and SASL authentication (RFC 2554). SMTP AUTH is implemented using a SASL client library integrated into libESMTP. Supported SASL mechanisms include CRAM-MD5 and NTLM.
- libESMTP is also efficient. Because it buffers all network traffic, when used in conjunction with a pipelining SMTP server libESMTP significantly increases network performance, especially on slow connections and those with high latency. Even without a pipelining server libESMTP offers significantly better performance than would be expected with a simple client.
- libESMTP is not designed to be used as part of a program that implements a Mail Transport Agent. This is not because the code is unsuitable for use in an MTA, in fact the protocol engine is significantly better than those in many MTAs. Rather, by eliminating the need for MX lookup and next-hop determination, the design of libESMTP is simplified; thus goals are made achievable. Besides, such features are undesirable in a program that is not an MTA, particularly if the client is behind a firewall which blocks access to port 25 on the Internet.
Enhancements:
- This release applies bugfixes and plugs some memory leaks.
- It also attends to a few autoconf-related issues.

Nullmailer, a sendmail/qmail/etc replacement MTA for hosts which relay to a fixed set of smart relays. It is designed to be simple to configure, secure, and easily extendable.
Installation:
The `configure shell script attempts to guess correct values for various system-dependent variables used during compilation.
It uses those values to create a `Makefile in each directory of the package. It may also create one or more `.h files containing system-dependent definitions.
Finally, it creates a shell script `config.status that you can run in the future to recreate the current configuration, a file `config.cache that saves the results of its tests to speed up
reconfiguring, and a file `config.log containing compiler output (useful mainly for debugging `configure).
If you need to do unusual things to compile the package, please try to figure out how `configure could check whether to do them, and mail diffs or instructions to the address given in the `README so they can be considered for the next release.
If at some point `config.cache contains results you dont want to keep, you may remove or edit it.
The file `configure.in is used to create `configure by a program called `autoconf. You only need `configure.in if you want to change it or regenerate `configure using a newer version of `autoconf.
The simplest way to compile this package is:
1. `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.
Running `configure takes awhile. While running, it prints some messages telling which features it is checking for.
2. Type `make to compile the package.
3. Optionally, type `make check to run any self-tests that come with the package.
4. Type `make install to install the programs and any data files and documentation.
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.
There is also a `make maintainer-clean target, but that is intended mainly for the packages developers. If you use it, you may have to get all sorts of other programs in order to regenerate files that came with the distribution.
Enhancements:
- Fixed problem with multiple arguments to protocol modules.
- Fixed extraneous spaces in SMTP sender.
- Made permissions on queued files more strict.
- Handle the "-bs" flag in the sendmail wrapper by dieing when we see it.
- Fixed the address parser handling domain names with trailing periods.
- Fixed bug in header parsing that would cause the last header line to be repeated if there was no body.
- Fixed bug in handling headers containing CR+LF line endings.

ExiBomb is a system designd to monitor mail traffic on the Exim based MTA server. The interface is developed in PHP. It reads the maillogs in a tail method and stores all relevant data in a MYSQL Database.The script reading the logs was developed in PERL.

Installation:

Exibomb.pl needs your exim configuration to have this set:
log_selector = +all

ExiBomb.pl will scan through the log and store data in the MySQL Database. Configure database paramters for exibomb.pl by editing the file. The web interface database settings can be found in config.php

Database schema exibomb.sql can be imported easily for example:
mysql database_name<<less