Free esmtp software for linux

qmail-smtpd-auth is a patch for qmail that enables it to support SMTP AUTH protocol with the following auth types: LOGIN, PLAIN and CRAM-MD5. Its based on a previous patch by Mrs.Brisby that implemented LOGIN type. This version has some enhancements and allows easy adding of new auth methods.
If you want to learn more about SMTP AUTH itself, then visit my SMTP AUTH page.
This patch adds the ESMTP AUTH option to qmail-1.03, allowing the LOGIN, PLAIN, and CRAM-MD5 AUTH types. An appropriate checkpassword tool is necessary to support the authentication. See http://cr.yp.to/checkpwd.html for more information on the interface. Note that the checkpassword tool should support all of the AUTH types
advertised by qmail-smtpd.
As reflected in the modified qmail-smtpd(8) man page, qmail-smtpd must be invoked with three arguments: hostname, checkprogram, and subprogram. If these arguments are missing, qmail-smtpd will still advertise availability of AUTH, but will fail with a permanent error when AUTH is used.
hostname is simply used to form the CRAM-MD5 challenge. qmail-smtpd invokes checkprogram, feeding it the username and password, in the case of LOGIN or PLAIN, or the username, challenge, and response, in the case of CRAM-MD5. If the user is permitted, checkprogram invokes subprogram, which just has to exit with a status of 0 for the user to be authenticated. Otherwise, checkprogram exits with a non-zero
status. subprogram can usually be /usr/bin/true (or /bin/true, depending on your flavor of OS).
If the user is successfully authenticated, the RELAYCLIENT environment variable is effectively set for the SMTP session, and the TCPREMOTEINFO environment variable is set to the authenticated username, overriding any value that tcpserver may have set. The
value of TCPREMOTEINFO is reflected in a Received header.
Enhancements:
- bug: AUTH PLAIN 334 response not RFC compliant. Reported by Mark Crispin
- .
- change: Set TCPREMOTEINFO environment variable to authenticated username. (Previously only set locally to qmail-smtpd.)

Fetchmail is a full-featured, robust, well-documented remote-mail retrieval and forwarding utility intended to be used over on-demand TCP/IP links (such as SLIP or PPP connections). Fetchmail supports every remote-mail protocol now in use on the Internet: POP2, POP3, RPOP, APOP, KPOP, all flavors of IMAP, ETRN, and ODMR. It can even support IPv6 and IPSEC.
Fetchmail retrieves mail from remote mail servers and forwards it via SMTP, so it can then be read by normal mail user agents such as mutt, elm(1) or BSD Mail. It allows all your system MTAs filtering, forwarding, and aliasing facilities to work just as they would on normal mail.
Fetchmail offers better security than any other Unix remote-mail client. It supports APOP, KPOP, OTP, Compuserve RPA, Microsoft NTLM, and IMAP RFC1731 encrypted authentication methods including CRAM-MD5 to avoid sending passwords en clair. It can be configured to support end-to-end encryption via tunneling with ssh, the Secure Shell.
Fetchmail can be used as a POP/IMAP-to-SMTP gateway for an entire DNS domain, collecting mail from a single drop box on an ISP and SMTP-forwarding it based on header addresses. (We dont really recommend this, though, as it may lose important envelope-header information. ETRN or a UUCP connection is better.)
Fetchmail can be started automatically and silently as a system daemon at boot time. When running in this mode with a short poll interval, it is pretty hard for anyone to tell that the incoming mail link is not a full-time "push" connection.
Fetchmail is easy to configure. You can edit its dotfile directly, or use the interactive GUI configurator (fetchmailconf) supplied with the fetchmail distribution. It is also directly supported in linuxconf versions 1.16r8 and later.
Fetchmail is fast and lightweight. It packs all its standard features (POP3, IMAP, and ETRN support) in 196K of core on a Pentium under Linux.
Fetchmail is open-source software. The openness of the sources is your strongest possible assurance of quality and reliability.
Main features:
- STARTTLS is supported in both POP and IMAP.
- ESMTP AUTH (RFC 2554) is supported.
- Has the capability of adding trace information to the Received header to faciliate mail filtering by mailserver and remote account.
- Fetchmail now has options to handle SSL certificate validation.
- Fetchmail can be told to fall back to delivering via local sendmail if it cant open port 25.
- Support for AUTH=CRAM-MD5 under POP3, a la RFC2195.
- Support for ODMR (On-Demand Mail Relay), RFC 2645.
- Its now easy to deliver mail to a local LMTP socket.
- The interface option now checks both local and remote interface IPs.
- The plugin facility has been enhanced; %h and %p options are now available to pass in the hostname and service port number.
- Added a dropdelivered option to discard Delivered-To headers. This addresses a problem with using fetchmail and postfix as a relay inside a domain; when postfix sees incoming messages with delivered-to headers looking exactly the same as the ones it adds himself, it bounces the message.
- Added --smtpname to set username and domain portion of SMTP "RCPT TO" command. - Added "from" servers IP address to inserted Received line.
- Fetchmail now runs on BeOS, thanks to David Reid .
- In IMAP, unseen-message counting and indexing is now done by SEARCH UNSEEN at the beginning of each poll or re-poll (rather than with the UNSEEN and RECENT responses and FLAGS queries on individual messages). This significantly cuts down on traffic to and from the server, and gives more reliable results.
- The aka option now matches hostname suffixes, so (for example) saying `aka netaxs.com will match not just netaxs.com but also (say) pop3.netaxs.com and mail.netaxs.com.
- Fetchmail can optionally use the RFC 2177 IDLE extension on an IMAP server that supports it. On IMAP servers that dont, it can simulate it using periodic NOOP commands.
- Fetchmail now recognizes the RFC 2449 extended responses [IN-USE] and [LOGIN-DELAY].
- Fetchmail running in daemon mode now restarts itself quietly when the rc file is touched.
- Following recent court decisions and changes in U.S. federal regulatory policy, hooks for Secure Sockets Layer (SSL) are now part of the main fetchmail distribution. The distribution still contains no actual cryptographic code.
- NTLM support under IMAP, so fetchmail can query Microsoft Exchange servers.
- Expunge option can now be used to break POP3 retrieval into subsessions.
- Support for AUTH=CRAM-MD5 under IMAP, a la RFC2195.

For those who want to build their own mailserver from sources on different GNU/Linux distributions like Slackware, Gentoo, CentOS, SuSe, Fedora Core or Debian, we created an universal package called qinstall-src.
qinstall-src is a source package collection along with a bash script that helps an administrator to compile, configure, install and run an e-mail server, based on qmail, together with all the programs required to run properly.
Main features:
- all perl modules required for optimum runtime;
- user administration web interface(qmailadmin);
- console-based user and domain administration (vpopmail, cqadmin);
- a bash script that eases the administration of queue pending messages (qmHandle);
- personalized webmail (SSL/TLS), activated quota, password changer (squirrelmail);
- ESMTP/SMTP, IMAP/POP3 SSL services activated by default (qmail, courier imap);
- e-mail autoresponder (autorespond);
- antivirus and antispam software (clamav, spamassassin);
- email filters (procmail);
- other programs that help running the e-mail server at optimum speed;
qinstall-src is tested on Slackware, Gentoo, Fedora Core, CentOS, openSuSe and Debian.
Enhancements:
- Many packages have been upgraded to the latest version.
- All packages have been ported to Bluewhite64 Linux (64-bit).

Unified Qmail Patch provides a concatenation of various patches.
Unified Qmail Patch is a concatenation of various patches for the qmail MTA. It supports SMTP AUTH after STARTTLS, Maildir++, regexp support in badmailfrom, and lots of features for high-end production servers.
Main features:
- Maildir++
- TLS encryption
- SMTP AUTH + SMTP AUTH close
- regexps in badmailfrom and support for badmailto
- external todo
- big remote concurrency patch
- external queue manager
- oversized dns responses
- reverse dns check
- tarpitting
- ESMTP size check from Gentoo
- tab bug fix in .qmail files
- linux link sync
- errno patch (compiles with gcc 3.x too)
- auth only after TLS patch from Gentoo
- Maildir quota fix patch from Gentoo
- qregex memleak fix patch from Gentoo
- David Phillips sendmail flagf patch
- Russ Nelsons QMTP patch for qmail-remote
- Jay Austads random qmqp pickup
- Alin-Adrian Antons integer overflow fix in qmail-smtpd.c
- Added support for SMTP throttling, using relayd
- Added my own patch, that checks whether the mail from value is different from the username used for SMTP AUTH, thus preventing source address spoofing. Useful for ISPs that only relay mails from authenticated users.
- The mail from verification is now configurable through a knob defined in /var/qmail/control/spoofcheck or in the environment variable $SPOOFCHECK
- It seems that in previous versions I accidentally ommited the support for a big todo, so heres a patch that finally supports it. My apologies to all :(

mhrw is a tool for mailheader manipulation. mhrw can be useful in complex MTA setups. In general, headers shouldnt be rewritten, but i found myself configuring an MTA with special delivery methods, where delivery took place depending on spamassassins spam-level and various other things.

In this setup, smtpd and delivery were completely different tasks without any communication possible between them. So, i decided to use the mail-headers loading some additional neccessary information. To get rid of lots of slow scripts, mhrw was born.

How it works:

mhrw reads mails from < stdin > or (if argument is given) from < file >. It supports two operating modes,

a) replace some part of the header, matched by a regular expression,
b) add some part to the header below the former last headerline.

In no way the body of a message is touched. Anything below the header is passed through. Also, the message will always pass until EOF.

Examples:

To show some example, on how to use mhrw, ill define the following (not
really standard, but very simple) mail as origin:

Received: somehost (somehost.somewhere) by uid 1007 with esmtp
X-Authenticated-SMTP: username
Received: anyhost; date
Subject: some test

body
...

If this mailalike header is getting used by following command:

mhrw ^X-Authenticated-SMTP: .*$

this will result in:

Received: somehost (somehost.somewhere) by uid 1007 with esmtp
Received: anyhost; date
Subject: some test

body
...

Youre able to use any regular expression you like, limited (by default) upto 4 subqueries.

The second argument (the replacement string) interprets written n and r sequences.

Installation:

mhrw dosnt relay on libraries and is written with a very basic set of commands, so:

./configure
make
make install

should build the binary on most platforms.

Dwarf Server Framework is a Java technology-based framework for developing network server applications.
The primary goal of Dwarf is to support development of network servers based on the Internet standards. However, its architecture is quite universal and it is not limited to this kind of applications only.
The first available Dwarf-based applications are the Dwarf HTTP Server with Java Servlets and JSP and Dwarf Mail Server with ESMTP/POP3/IMAP4.
Simple design and very concise API together with an extensive documentation makes the learning and consequent work with the framework easy and fast for the development team.
Modular multithreaded architecture as well as efficient implementation guaranties the performance on top. Incorporation of Java 2 Platform Security Architecture and Java Authentication and Authorization Service (JAAS) helps to meet todays high security demands.
Dwarf Server Framework, although not an all-purpose universal wheel, offers extending the server functionality by customizing almost all its components:
- multithreaded service development
- support for TCP/UDP based services
- authentication via login modules
- authorization based on subjects
- logging and configuration
Furthemore, it comes with the full documentation, guides and examples, and is free of charge for the binary redistribution.
Main features:
Main features
- universal multi-threaded server
- generic TCP and UDP protocol handlers
- extensible remote management
- various utility classes (DNS client, queues, caches, etc.)
- XML-based configuration
Security
- application-independent authentication
- subject-based authorization
- proprietary or third party login modules
- SSL/TLS secure communication
Support
- rich documentation with tutorials
- samples with source code included
License
- free of charge binary redistribution

Dwarf Mail Server is a full-featured mail server developed on the Java platform, implementing SMTP, POP3 and IMAP4rev1 protocols.
Dwarf Mail Server provides support for rich application message processing via pluggable mail filters and agents, as well as full handling of virtual domains for the SMTP/POP3/IMAP4 protocols, and is free of charge for the binary redistribution.
Since the server is based on the Dwarf framework, it also shares its common design principles and features - simplicity, high modularity and extensibility, authentication and authorization, XML-based configuration, logging and remote management.
Main features:
- ESMTP, POP3 and IMAP4rev1 implementation
- application logic layer provided by mail filters and agents
- virtual mail hosts in SMTP/POP3/IMAP4 server
- application-independent authentication and authorization
- sample JSP-based webmail interface
Dwarf Mail Server is targeted for both end users who are just looking for simple, secure and robust mail server as well as developers who need an extensible and powerful framework for application message processing.
For users with minimal requirements it can offer portability, simple configuration as well as strong security.
- Portability: several OS platforms are supported via the Java technology, including MS Windows, UNIX/Linux/BSD, MacOS X and others.
- Configuration: just 3 lines have to be changed to fire up a sample mail server and a few of them to run a full featured SMTP/POP3/IMAP4 server.
- Security: it uses Java Platform Security Architecture in combination with Java Authentication and Authorization Service (JAAS), as well as SSL/TLS for the secure communication.
Advanced or enterprise users can additionally appreciate performance scalability, multiple domain handling, enhanced security features and modular design easing to incorporate it to the existing infrastructure.
- Scalability: gaining from multithreaded design and dynamically adjustable allocation of resources.
- Multiple domains: server is able to handle multiple virtual domains in a single instance for all SMTP, POP and IMAP protocols.
- Enhanced security: includes subject-based permissions and access control lists for IMAP, SMTP relaying control rules, host-based filtering, SSL/TLS communication, basic anti-spam filtering, etc.
- Robustness: client/server network communication is by design separated from the resource-expensive application logic layer. The server implementation is based on the unparsed byte streams whenever possible, including its own and highly efficient MIME parser.
Dwarf Mail Server also appears to be a suitable platform for application development and customization. Its modular structure and lightweight API allows enhancing existing functionality or completely exchanging the certain part as a whole:
- Message processing: mail filters and agents provide an unique infrastructure for rich message processing.
- Mail queue: physical mail queue representation is abstracted by the API specification and may replaced by a custom implementation.
- Storage subsystem: physical data representation (i.e. messages, folders, configuration options, ACLs) is abstracted by API and may be replaced by a custom implementation based on filesystem, SQL database, etc.
- MIME parser: the parsing engine may be reimplemented for the top efficiency according to the currently used mail storage.
Dwarf Mail Sever has been tested with the most popular mail clients like MS Outlook, Mozilla, Thunderbird, Opera, Apple Mail, Becky!, Pegasus, Eudora, Pine, The Bat! and others.
Other features:
- multi-threaded server
- dynamically adjusted number of active threads
- server API for mail, user data and ACL storages
- robust SMTP server architecture with flexible queue design
- simultaneous deliveries to remote SMTP hosts
- transparent Delivery System Notification (DSN) mechanism
- support for shared mail folders
- fast and universal stream-oriented MIME parser
- runtime server configuration
- built-in SSL/TLS support
- full documentation with user guides and tutorials
- samples with source code