Free pop3 server software for linux

RIPE Whois Server provides support for domain records and lookups.

This is a whois database server. The RIPE Whois server uses a backend SQL database to allow support for very large repositories. There is support for IPv6 records and lookups. Both RPSL and RIPE181 are supported.

Campus Chat Server project is a chat server intended for use in the Cadiz University campus network.
Enhancements:
- hash_maps are now used instead of maps, so the cost of lookup or insertion is O(1) in the average case, instead of O(logn).

POP3 Virus Scanner Proxy is a full-transparent proxy daemon which scans all mails for viruses using third party scanners (built-in support for AVPD and Trophie).

You have to set up a port redirection in the linux-netfilter (iptables) so that all connections from e.g. inside your office to any POP3 server outside in the world will not leave your router, but come a local port, on which POP3VScan listens. POP3VScan receives from the linux kernel the original destinations of packets (the POP3 server outside in the world) and will connect to them.

All data we receive from the client will be sent to the server, and vice versa. With a little enhancement: we parse the neccessary parts of the POP3 protocol and when an email is sent from the server, we store it into a file, invoke a virusscanner and send it if it is good, or we just replace it with a virus notification. It should be possible to use all scanners using the scannertype=basic. Also POP3VScan provides scannertype=avpd for high-speed scanning using Kaspersky Anti-Virus for Linux, every C programmer can easily adept other scan-daemons (trophie, sophie, antivir, ...).

Neither the client nor the server has to be configured, none of them will take notice that theres a mailscanner (except the client when he gets a virus notification or if he looks into the header, and the server gets our ip as source).

Net::Server is an extensible, general Perl server engine.
SYNOPSIS
#!/usr/bin/perl -w -T
package MyPackage;
use Net::Server;
@ISA = qw(Net::Server);
sub process_request {
#...code...
}
MyPackage->run(port => 160);
exit;
Main features:
- Single Server Mode
- Inetd Server Mode
- Preforking Simple Mode (PreForkSimple)
- Preforking Managed Mode (PreFork)
- Forking Mode
- Multiplexing Mode using a single process
- Multi port accepts on Single, Preforking, and Forking modes
- Simultaneous accept/recv on tcp, udp, and unix sockets
- Safe signal handling in Fork/PreFork avoids perl signal trouble
- User customizable hooks
- Chroot ability after bind
- Change of user and group after bind
- Basic allow/deny access control
- Customized logging (choose Syslog, log_file, or STDERR)
- HUP able server (clean restarts via sig HUP)
- Dequeue ability in all Fork and PreFork modes.
- Taint clean
- Written in Perl
- Protection against buffer overflow
- Clean process flow
- Extensibility
Net::Server is an extensible, generic Perl server engine. Net::Server combines the good properties from Net::Daemon (0.34), NetServer::Generic (1.03), and Net::FTPServer (1.0), and also from various concepts in the Apache Webserver.
Net::Server attempts to be a generic server as in Net::Daemon and NetServer::Generic. It includes with it the ability to run as an inetd process (Net::Server::INET), a single connection server (Net::Server or Net::Server::Single), a forking server (Net::Server::Fork), a preforking server which maintains a constant number of preforked children (Net::Server::PreForkSimple), or as a managed preforking server which maintains the number of children based on server load (Net::Server::PreFork). In all but the inetd type, the server provides the ability to connect to one or to multiple server ports.
Net::Server uses ideologies of Net::FTPServer in order to provide extensibility. The additional server types are made possible via "personalities" or sub classes of the Net::Server. By moving the multiple types of servers out of the main Net::Server class, the Net::Server concept is easily extended to other types (in the near future, we would like to add a "Thread" personality).
Net::Server borrows several concepts from the Apache Webserver. Net::Server uses "hooks" to allow custom servers such as SMTP, HTTP, POP3, etc. to be layered over the base Net::Server class. In addition the Net::Server::PreFork class borrows concepts of min_start_servers, max_servers, and min_waiting servers.
Net::Server::PreFork also uses the concept of an flock serialized accept when accepting on multiple ports (PreFork can choose between flock, IPC::Semaphore, and pipe to control serialization).

C++ Server Pages is a partial Java server pages and servlet implementation in C++. C++ Server Pages is written as Apache 2.0 modules, with the focus on performance.

QEMU Server Tools is a set of simple command-line scripts for managing multiple QEMU VMs easily without requiring a graphical frontend.

QEMU Server Tools organizes VMs into directories and mimics the usage of command line tools from VMware Server.

WMPop3 is a Window Maker dockable I wrote which will inform a user on how many messages are currently in thier pop3 mail box.

WMPop3 when first executed will check if there is a .wmpop3rc file in the users home directory, it will create this if it can not be located. This file must be edited and the following fields must
be changed :

1) popserver - this is the name of the pop3 server.
2) port - this is the port the pop3 server is on.( default 110)
3) username - users pop3 login name.
4) password - users pop3 login password.
5) autochecking - This allows to disable or enable auto mail checking. 1 enables, 0 disables
6) mailcheckdelay - Number of minutes, before checking mail. (default = 10 minutes)
7) mailclient - this is the mail client you use to send/retrieve messgaes(default pine)
8) viewallmessages - This allows for alternating mail views, 0 shows unread and read messages, 1 shows only unread messages.

Qpopper project is the most widely-used server for the POP3 protocol (this allows users to access their mail using any POP3 client). Qpopper supports the latest standards, and includes a large number of optional features. Qpopper is normally used with standard UNIX mail transfer and delivery agents such as sendmail or smail.
Qpoppers goals are: security, stability, safety, features, and performance.
The 3 and later code base has multiple levels of protection again common security vulnerabilities, so even if there is a bug at one level, the other levels can protect against an exploit. Stability means running without crashing or other problems. All bug reports are reviewed and taken seriously.
Safety means protecting the users mail. Qpopper takes extra precautions to guard against spool corruption, even if there is a system crash or power failure during an update. Qpopper provides a large number of features, such as bulletins, support for wireless devices, APOP, integration with packages such as Kerberos, drac, etc.
Qpopper strives for the maximum possible performance consistent with safety. You can also tell Qpopper when it is running in an environment where some precautions are not required, resulting in extra performance (for example, if users do not access mail using shell accounts).
This server is fully compliant with RFC 1939 (which defines the POP protocol) and RFC 2449 (which defines the POP extension mechanism and the extended response codes), and works with all known POP3 clients.
Qpopper also supports Kerberos V4 and V5 if enabled.
Main features:
- Faster start-up (1,000 times faster, in many cases)
- Reduced I/O at session end (one-third less!)
- TLS/SSL (allows authentication and email to be strongly encrypted between any TLS/SSL-enabled mail client and Qpopper 4.0.5; requires TLS/SSL)
- Plus all the great features of Qpopper 3.1 (including full sources)
- Most compile-time options now are available at run-time
- Easier administration