Free mailserver software for linux

vislog is a set of perlscripts written to bring virus and spamdetection to a mailserver running postfix for smtpd and cyrus-imap for local delivery.

It accepts mail from postfix sends them to clamav-virusscanner und spamassassin and afterwards give the tagged and scanned mail to cyrus-imap for local delivery.

It has a small perlscript to examine its own logfile about the found viruses and generate a html overview about it.

PHPwebmail is a Web-based IMAP and SMTP mail client. Often it is not possible to make outside mail connections from networks behind strict firewalls, or to configure a regular mail client (for example in an Internet cafe).

With PHPwebmail a mail client only needs a WWW connection to the mailserver. Specifically it only needs a connection to the webserver hosting PHPwebmail.

Most of the times the Web and mail server will be the same machine but PHPwebmail can connect to other mailservers as well as long as an IMAP connection between these two machines is allowed.

Openmailadmin is a little administration interface to every complete IMAP mail server daemon. Openmailadmin supports every feature IMAP provides, and fits in most MTA configurations.
A key feature is the non-standard, generic administration hierarchy which not only seperates "normal users" from "administrators", but enables the mailserver-master to create instances between them.
You will be able to let other users create their own sub-users and thus either share a single mail server between different organizations or project your companys employee structure. It excels with features such as regex addresses and folder ACL management.
Installation:
1. Copy all the files into your DocumentRoot-folder.
2. Modify following files by changing usernames and passwords:
- samples/pam/imap
- inc/database.sql
And either of these:
- samples/postfix/*
- samples/oma_mail.daimon.*
3. Create the required database and users in MySQL. Modify database.sql and have it executed inside the new database.
4. Copy samples/pam/imap settings to your /etc/pam.d folder
{{{
chmod 600 samples/pam/imap
cp samples/pam/imap /etc/pam.d/imap
ln -s /etc/pam.d/imap /etc/pam.d/pop
ln -s /etc/pam.d/imap /etc/pam.d/sieve
ln -s /etc/pam.d/imap /etc/pam.d/smtp
}}}
5. For security reasons, remove these files from your DocumentRoot-folder:
{{{
rm inc/database.sql
rm -r samples/pam
rm samples/oma_mail.daimon.* samples/postfix
}}}

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).

WormWarner is a tool designed to warn hosts that are probably infected by worms. This is done by scanning the Apache log files and sending email to the host or the ISP when an worm or attack is detected. Wormwarner started in September 2002 as a small project written in Perl.
Wormwarner has a simple pattern database which makes it easy to add new worm patterns as they appear. Another important feature is the build in rate and mail size control which avoids that wormwarner sends out to much email to an ISP. Wormwarner has also the option to excute external commands, which makes it easy to adapt i.e. firewalls based on the attacks and worms detected by wormwarner.
However there were features requests and the application grown in complexity. The goal of the wormwarner project is to provided users with a powerful and flexible, but benign tool to take action against worms and attacks on their webserver(s).
Enhancements:
- The attack complaint message was changed to a less offensive one.
- "GET /scripts/nsiislog.dll" was added to the attack patterns.
- Various formmail exploits were added to the attack patterns.
- Added the smtp option to specify a mailserver to use to send the warnings to the ISP.
- Patterns are now stored in pattern.db which makes it easier to add patterns.
- The IIS WebDAV exploit was added to the patterns

fetchExc project is java utilily which retrieves mail from your MS Exchange (2000/2003) inbox and forwards it to SMTP server of your choice or mbox type file.
FetchExc uses webDAV (OWA) to retrieve mail either over http or https. This is also means that you administrator must have left Outlook Webaccess available in Exchange in order to get this utility to work.
Although version number is still below 1.0 I consider this program usable in production environment.
There are still many places that should be polished and improved but atleast there havent been major problems in over an half a year. Before you install read installation instructions from below carefully.
Installing:
So far this only covers *nix systems (windows instructions may follow if they are needed)
Extract fetchExc-*.tar.gz or make directory for fetchExc.jar. If you are downloading Jakarta components yourself put them in the same directory as fetchExc.jar.
Create fetchExc.properties file in your home directory. Remember to protect it with chmod 700 (it contains your password). If you took .tar.gz package there should be example included.
ExchangeServer=xxx.dddddd.com
ExchangePath=exchange
ExchangeUser=exuser
MailServer=yyy.dddddd.com
DestinationAddress=user@yyy.dddddd.com
Username=domainuser
Password=domainpassword
Domain=DOMAIN
Delete=false
All=false
Secure=true
FBApath=/exchweb/bin/auth/owaauth.dll
ExchangeServer - Name of your MS Exchange server.
ExchangePath - Exchange path for MS Exchange OutLook WebAccess.
ExchangeUser - Name of you MS Exchange User.
You can test first three properties by making URL out of them: http://xxx.dddddd.com/exchange/exuser. This should give you a Outlook Webaccess Page.
MboxFile - Path and name of mbox-type mail box. This disables MailServer- and DestinationAddress-properties. Be careful with this because Im not 100% sure that file locking works (YMMV). If there are problems let me know. Also success reports would be nice.
MailServer - Name of your SMTP Server which receives forwarded messages. If there is MboxFile defined this property wont be used.
DestinationAddess - Address of recipient of forwarded messages. If there is MboxFile defined this property wont be used.
Username - Username for your windows domain user. It may be same as ExchangeUser but necessarily.
Password - Password for domain user.
Domain - Domain for above user.
Delete - Whether program should delete mail from Inbox or just mark them as read. If Delete is true mail will be deleted after succesful forwarding. Any other value will just mark message as read. While you are configuring other properties I strongly recommend that you use value false for this property.
All - Whether program should real all mail from Inbox or just which are not read yet. If All is true every mail will be read. Any other value will read only unread mail. While you are configuring other properties I strongly recommend that you use value false for this property.
WARNING!!! Dont combine Delete=false and All=true if you are not testing. That will fetch every mail from your Inbox everytime you start the program.
Secure - If value is true program will use https. Any other value will use http. Https should be user whenever possible.
FBApath - Path to form based authentication. If not set defaults to /exchweb/bin/auth/owaauth.dll. This can be found on FBA login page source (hint: search for "destination")
ForceFrom - If this is set to true forwarded mail will be forwarded with address from ForceFromAddr parameter. This only happens when sender address is not valid. For example if there is two From: fields in mail header Exchange can join addresses. NOTE: This may help spam to get through so use carefully.
ForceFromAddr - E-mail address that forwarding server will accept. Only used if ForceFrom is true
NoEightBitMime - If this is true SMTP forwarding doesnt use BODY=8BITMIME. Default is false.
Now you just need to include JRE in you path. If it is in you path you can run program:
java -jar /install/fetchExc/fetchExc.jar
You can now (>0.80) use -p switch to change properties file. For example:
java -jar /install/fetchExc/fetchExc.jar -p test.properties
would run program using properties from test.properties
I use fetchExc with following little shell script and crontab entry so that it keeps fetching mail every two minutes.
fetchExc
#!/bin/bash
export PATH=$PATH:/usr/local/jre/bin
java -jar /install/fetchExc/fetchExc.jar $* >> fetchExc.log 2>> fetchExc.err
If you use this script replace /usr/local/jre/bin with path to your java runtime environment. Same applies to location of your installation on next line.
crontab entry:
*/2 * * * * ~jrauti/bin/fetchExc
Enhancements:
- Java has been changed from 1.4 to 1.5.
- The Jakarta HHTTP client has been upgraded from 2.0 to 3.0.
- Proxying also works with HTTPS.
- Code cleanups.
- A small fix in mbox saving (in Mac OS X, messages were coalesced).

Phpfw is a framework for PHP that provides a base on which various database backend applications can be built. Phpfw project allows for easy creation of CRUD applications - apps where most of the code is focussed on Create Read Update Delete operations on the database. It uses MVC-ish patterns to allow for simpler and cleaner organization of code.
Phpfw leverages popular PHP libraries so as to avoid reinventing the wheel. For example, the database abstraction layer is a thin wrapper that supports ADOdb and ADOdb Lite. Hence, Phpfw is able to support multiple databases thanks to these excellent libraries.
Phpfw requires minimal configuration. All the database information is directly obtained from the database itself. The configuration file is a simple .ini file and is adequately commented to explain the different elements.
Phpfw comes built in with an elementary templating class to generate HTML output. Further it also supports templating frameworks like Smarty and PHPTAL. The combination of these templating facilities provides adequate power to generate simple to complex output.
Phpfw is the result of several PHP projects I undertook over the years. It grew inside active projects and has finally taken a life of its own. It has been written from scratch based on all the code that was written over the years with a focus on simplifying the process of creating new applications with minimal effort. I hope this work proves useful to those of you who would like to put together applications quickly and easily.
Enhancements:
- Several enhancements were made in the core API such as AJAX support, database schema auto-load and optional database usage.
- New modules include Config, MailServer, and PelWrap.
- Enhancements were made to existing modules to allow login from file.

SMTP Relay Checker is a fully configurable, multithreaded open mail relay scanner. It supports scanning of IP blocks, and can print the results to a Web page.
SMTP Relay Checker is intended for Systems Administrators to check IP blocks under their control.
Compilation / Installation
To build SmtpRC please run "make" in the package directory. This will build the package and create the binary "smtprc". To install the package, please run "make install".
By Default, the binary will be installed into /usr/local/bin/, configuration files will be installed under /usr/local/etc/smtprc/ and all documentation files will be installed under /usr/local/share/doc/smtprc/. Please see below for a full list of installed files.
/usr/local/bin/smtprc
/usr/local/bin/gsmtprc
/usr/local/etc/smtprc/auto.conf
/usr/local/etc/smtprc/email.tmpl
/usr/local/etc/smtprc/rcheck.conf
/usr/local/share/doc/smtprc/README
/usr/local/share/doc/smtprc/FAQ
/usr/local/man/man1/smtprc.1
/usr/local/man/man1/gsmtprc.1
Using Smtprc
SmtpRC can be run by specifying options on the command line, or by configuring an "auto configuration" file and letting SmtpRC parse the options from there. The latter is recommended.
When SmtpRC is installed, a example "auto configuration" file is installed in "/usr/local/etc/smtprc/auto.conf". Edit this file, changing the values to suit your specific network requirements and run smtprc with the following option (a full list of options
is detailed below):
"/usr/local/bin/smtprc -j /usr/local/etc/smtprc/auto.conf"
To be sure that a mailserver relays third-party email, SmtpRC will attempt to relay mail to an address specified. It is recommended that this address is a mailbox on the local machine that is being used to run SmtpRC - pop support is a planned feature, but for now, SmtpRC only supports checking local mailboxes (mbox and Maildir). Create a new user account (smtprc), specify the email address for this account, and the local mailbox (on the command line or in the "auto configuration" file), and SmtpRC will attempt to relay emails to this address and check for recieved emails after scanning.
There is also a GUI interface to smtprc (gsmtprc) that is installed in /usr/local/bin. This requires Perl Tk to run.
Enhancements:
- Fixes a race condition between the master and reaper threads.