Free server connections software for linux

savIRC project is an IRC client for Linux and Windows.
Main features:
- multiple server connections
- CTCP
- DCC also "passive"
- SOCK5 for servers and DCCs
- ignore and notify lists
- mIRC colors
- URL caption
- Tabbed-MDI
- scripting in TCL/Tk!
Enhancements:
- The savIRC handbook has been updated and converted to docbook.
- The source code has begun to be documented with ROBOdoc.
- A checkbox to hide automatic serverpings was added. /disconnect now stops autoreconnect.
- Chunks of text are broken into 400 chars or less and will be sent with a delay to prevent flooding.
- An alternate nick is used if the one tried is erroneous on the current ircd.

Port forward is a java application which gives you the ability to open tunnels between your local computer and a remote ssh server. With Port forward, tunnels can be created both local or remote.

Examples:

1. Open a local tunnel to reach a remote mysql database

- Your application needs to connect to a remote database server (mysql for example), but the database server (remote.server.example) is not configured to expose mysql to internet directly.
- Port forward will open a local port (3306) and redirect the connections to remote.server.example ssh server
- The remote.server.example ssh server will connect to its local mysql server

2. Open a local tunnel to use a remove VNC desktop

- You want to connect to your home computer which has a vnc server but from work, the firewall blocks vnc connections (generally on port 5901)
- If you have a ssh server at home, you could use it as bridge to connect to a client in your home:

Your position internet your linux ssh server ->>
-->> you client with vnc (192.168.0.40)

you office
internet >

3. Open a remote tunnel to pilot a remote linux server non reachable through internet
In this example, you will create a remote tunnel, this will give the remote man to connect to and reach you.

I used this example if I have to pilot a remote pc, but this pc has no static IP or is behind a firewall
The good solution is to activate port forward on the pc to be piloted and to connect it to a server we can access.


PC 1 (to be piloted) --||||-- firewall ----- internet ----- accessible-server

Installation:

Be sure java is in you classpath
tar zxvf portforward.tar.gz
cd portForward
sh run_linux.sh

Mail::Bulkmail::Server is a Perl module that handles server connections and communication for Mail::Bulkmail.

SYNOPSIS

my $server = Mail::Bulkmail::Server->new(
Smtp => your.smtp.com,
Port => 25
) || die Mail::Bulkmail::Server->error();

#connect to the SMTP relay
$server->connect || die $server->error();

#talk to the server
my $response = $server->talk_and_respond("RSET");

Mail::Bulkmail::Server now handles server connections. Mail::Bulkmail 1.x and 2.x had all the server functionality built into the module itself. That was nice in terms of simplicity - one module, one connection, one server, and so on. But it had some downsides. For one thing, it only allowed for one connection. And since I wanted to allow multiple server connections in 3.00, that had to go. For another, it was a pain in the butt to change the server implementation. This way, you can easily write your own server class, drop it in here, and be off to the races.

For example, the Mail::Bulkmail::DummyServer module for debugging purposes.
This is not a module that youll really need to access directly, since it is accessed internally by Mail::Bulkmail when it is needed. Specify the data you need in the conf file and the server_file attribute, and you wont ever need to touch this directly.

chaosircd project is an IRC daemon with commands, channel modes, user modes, and flood control implemented as runtime (re)loadable modules.

DNS, AUTH (ident) queries, and proxy scans are done in a single child process to avoid wasting valuable file descriptors and responsiveness.

It features a server-server protocol using timestamps for netsplit handling similar to TS5 (hybrid), and OpenSSL encrypted server-server and client-server connections.

IMAP Proxy server is a caching IMAP proxy server. It was written to compensate for webmail clients that are unable to maintain persistent connections to an IMAP server. Most webmail clients need to log in to an IMAP server for nearly every single transaction.

This behaviour can cause tragic performance problems on the IMAP server. imapproxy tries to deal with this problem by leaving server connections open for a short time after a webmail client logs out.

When the webmail client connects again, imapproxy will determine if theres a cached connection available and reuse it if possible.

How does imapproxy keep track of which server connection is for which user?

Upon the first successful login to the real IMAP server (through the proxy), imapproxy fills in a little record that contains the username, an md5 digital signature of the password and the server socket descriptor thats being used.

After you log out and then log back in again, imapproxy just has to find a record that matches your username and password. These records are stored in a hash table (with the username being the hash key) in memory, so the lookups are pretty fast.

Can IMAP Proxy support multiple backend servers?

If you want IMAP Proxy to be able to proxy to multiple backend IMAP servers, you can run multiple instances of IMAP Proxy and make sure each instance is looking at a different configuration file.

Before you do this, take a look at perdition which appears to have been designed with this specific task in mind.

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

Courier-IMAP is a fast, scalable, enterprise IMAP server that uses Maildirs. Many E-mail service providers use Courier-IMAP to easy handle hundreds of thousands of mail accounts.
With the built-in IMAP and POP3 aggregation proxy in Courier-IMAP 4.0, the only practical limit to Couriers horizontal scalability is available LAN bandwidth. In proxy mode, a pool of Courier servers receive IMAP and POP3 connections from clients, wait for the clients to send a login request, look up the mail accounts server, and establish a proxy connection to the actual server that hosts the mail account.
Please note that this IMAP server does NOT handle traditional mailbox files (/var/spool/mail, and derivatives), it was written and optimized for the specific purpose of providing IMAP access to Maildirs.
"Maildir" is a directory-based mail storage format originally introduced in the Qmail mail server, and adopted as an alternative mail storage format by both Exim and Postfix. Courier-IMAP is popular on Qmail/Exim/Postfix sites that are configured to use maildirs. The primary advantage of maildirs is that multiple applications can access the same Maildir simultaneously without requiring any kind of locking whatsoever. Maildir is a faster and more efficient way to store mail. It works particularly well over NFS, which has a long history of locking-related woes.
This is the same IMAP server thats included in the Courier mail server, but configured as a standalone IMAP server that can be used with other mail servers - such as Qmail, Exim, or Postfix - that deliver to maildirs. A Courier/Postfix combination is very popular. If you already have Courier installed, you do not need to download this version. If you install this version, you must remove it if you later install the entire Courier server. Its possible to have both versions installed, but this will require a delicate juggling act that youll have to learn on your own.
Enhancements:
- A bug in quota calculation on 64-bit platforms has been fixed.
- The IMAP server will try to log the clients bandwidth usage if the server process gets killed by a signal.
- New messages created by the IMAP server will use the servers umask setting.
- Many compiler warnings, error messages, and manual page typos were fixed.