Free kerio 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.

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

PhpWatchDog is a network monitor application which provides a simple way to check if a service (HTTP, FTP, SSH, etc.) is running or not. PhpWatchDog project can send email to the servers administrator to report malfunctions.
This little script is running into my servers from some time (even from two years!). Its very usefull to alert a system administrators team by email. Its a PHP script, so you can setup a cronjob that run the URL of phpwatchdogs installation when you want (I suggest every hour).
Main features:
- check if service is UP or DOWN
- no need to install anything into monitored servers
- report to one email address if service is DOWN
- simple and light
- easy to install and configure
- can set the timeout for probing the service status
- can use fsockopen (PHP) or IO::Socket (PERL) - if for any reasons the fsockopen can operate correctly
- can monitor n servers with a single instance
- can alert a custom email address per server
- to work properly need only APACHE+PHP, no databases or various plugins
- collect each downtime event into a plain text file
Installation:
unpack the downloaded archive
# tar jxvf phpwatchdog-*.tar.bz2
enter into phpwatchdog/ directory and edit the config file (config.php)
# cd phpwatchdog
# nano config.php
Note: here you can see nano, that is an easy to use text editor, but I strongly encourage to learn to use vim (the enhanced version of vi)
put your servers into config.php
$i++;
$config[Servers][$i][host] = 66.35.250.203;
$config[Servers][$i][server_name] = www.sourceforge.net;
$config[Servers][$i][service][1] = 80;
$config[Servers][$i][service][2] = 443;
Every server configuration block must begin with the line "$i++;"
customize your email account for alert reporting into config.php
fire up your browser and go to phpwatchdog installations path
You can schedule the execution of this script putting a similar command into /etc/cron.hourly/ /usr/bin/php-cgi -q /path/of/phpwatchdog/index.php > /dev/null
or using lynx
lynx -dump http://webhost/path/of/phpwatchdog/index.php > /dev/null 2>&1
or with wget
wget -O /dev/null http://webhost/path/of/phpwatchdog/index.php > /dev/null 2>&1
The directory tools contains some usefull scripts:
chk_socket2.pl - its a Perl script used to check the service status if PHP mode is disabled
generate.sh - its a bash script used to generate (with the help of generate.awk) a configuration block from nmap output
sh generate.sh
Usage:
generate.sh IPADDR SERVERNAME
eg:
generate.sh 192.168.0.1 MailServer.com

EXACT is a UNIX daemon that provides mail relay control. It is written for those who operate a mailserver and wish to allow mail relaying, conditionally on users authenticating to an IMAP or POP server.
It supports UW-imap, Qpopper, Cyrus, Perdition, TeaPOP, cucipop, EXIM, Postfix and Sendmail out of the box.
It will work as is with these POP/IMAP servers:
- UW-IMAPD
- Cyrus
- Courier (IMAPD and POPD)
- Perdition
- Qpopper
- TeaPOP
- Cubic Circles cucipop
and these MTAs:
- Exim
- Sendmail
- Postfix
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:
- Bugfix release. Building without db didnt work.
- Also changed back to dbmnz format for the db, because the other format seemed to cause exim problems.

Virge is mail scanner written in C, which replaces/substitutes procmail for a while, checks the incoming mail, and then sends the mail to the procmail. It will check mail for viruses and/or attachment names. Check the FEATURES/README/NEWS files for more details. Virge requires Sendmail and (optionally) AVPDaemon, Sophie or Trophie (to check attachments for viruses).
Virge replaces temporarily procmail. When new mail comes in, Sendmail will pass the contents of the mail to Virge. At that point, Virge performs set of checks:
Checks if the mail has attachments. If it does not, it sends it to procmail for delivery.
If mail has attachments, Virge creates temporary directory, unpacks attachments there, and asks AVP/Sophie/Trophie to scan the temporary directory for viruses. Virge was created with 2 things in mind: performance and security. Because of performance issues, it was not feasible to use any command line scanners like TrendMicro of McAfee ones.
AVP/Sophie/Trophie are instructed to scan attachments for viruses next. If it finds any viruses, mail is immediately isolated in a directory not (hopefully) accessible to anyone except administrators.
If no viruses were found, Virge will then perform attachment check, and see if any of the attachments are not allowed to be sent to the end user. A configuration file is consulted for list of extensions (or full filenames) that should not be allowed in. If any such attachments were found, tricky part comes - Virge will *hopefully* properly "rewrite" the whole email, and strip the attachments that are not allowed. Small notice is attached at the end of the mail, with names of stripped attachments. Mail is also isolated, in case poor overworked sysadmin ever gets some free time to take a closer look.
IMPORTANT: Please, keep in mind that Virge will *NOT* rewrite & send mails when virus has been found. I will *NOT* implement any such features, since it doesnt make any sense (I havent seen a mail with virus that actually had some valuable content in it for many months - maybe even years).
If AVP/Sophie/Trophie are not available (daemon is down), Virge will still deliver mails and annoy admins through syslog messages. Attachment check is still performed.
Users for which no checks should be performed can also be configured. Location of the file can be specified in the configuration file.
Virge is definitelly trying to not let any lame script kiddies abuse it in any way. It is trying to resist to race conditions, buffer overflows, and similar neat tricks. No guarantees, of course, that there are no security problems in Virge.
Virge tries to be as fast as possible, and not waste CPU time or any other resources. It is still possible to make it perform even better, although I presume it would be in 1-5% range. Will take some more time later, and try to fix all the small performance problems.
And yes - Virge *is* fast. I have made a complete Virge V1 in Perl some time ago, but it was absolute failure. Although I tried to use as little modules as possible and make it as fast as possible... it was crap. 2 minutes after I started a script that sends 3-5 mails per second, I started wondering "Why the hell cant I login to the mailserver anymore?". Perl is nice, but its not good for tools like this. Not at all (except if you have low traffic on your mailserver).
And Virge still needs a *lot* of testing. I have tried to test Virge with many different mail (MIME) formats and tried different tricks in order to bypass its decoding techniques (in order to send a virus or .exe to users), but it handles things pretty well. There are cases, though, when it is possible to trick librfc2045 and send attachments that dont get caught, but those attachments are violating RFCs anyway. If your mail client is so stupid to decode invalid/malformed attachments/mails - you deserved it. Dont use stupid mail clients then. Im not going to start adding all those crappy features into Virge that would let someone detect all possible tricks which can be used. Use good mail clients, dont rely on Virge to save you.
Main features:
- Virge can check every incoming mail for attachments, and can remove attachments that are considered dangerous.
- "Dangerous" can be defined:
- email with specific kinds of attachments (e.g., .EXE, .COM, etc.)
- email that contains a virus as identified by Sophie ( http://www.vanja.com )
- email that contains a virus as identified by trophie ( http://www.vanja.com )
- email that contains a virus as identified by AVPDaemon (http://www.avp.ch)
- Any combination of the above.
- Dangerous email can trigger:
- rewriting that removes virus.
- alert back to sender.
- alert to recepient.
- alert to system manager.
- rewrite to remove virus.
- All offending mail messages can be isolated for later reviewing.
- Written in C, so it is very fast, doesnt waste resources, and doesnt depend on a complicated perl installation (which is subject to breaking).
- Notification can be sent (configurable) to sender/recipient of suspicious/infected mail. Templates can be used to define the layout of the mail.
- Regular expressions can be used for filename matching
- Virge was made with security in mind, and should be hard to abuse
- Can be configured to fail open or fail closed if load on the machine goes too high.
- Virge 3.0 designed for easy integration with Postfix

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.

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.

SiMP (Simple Mail Parser) is a procmail-like mailparser, except that its much more easier to configure. With SiMP you can automatically store incoming mail in seperate folders, remove junkmail, send a reply, forward the mail, etc.

It has been tested with Sendmail and Postfix as a mailserver and Pine as the mailreader, but it is likely that SiMP will work with other mailservers and -clients.