Free socks galore software for linux

tsocks provides transparent network access through a SOCKS version 4 or 5 proxy (usually on a firewall).

SOCKS servers are a form of proxy that are commonly used in firewalled LAN environments to allow access between networks, and often to the Internet. The problem is that most applications dont know how to gain access through SOCKS servers. This means that network based applications that dont understand SOCKS are very limited in networks they can reach. An example of this is simple telnet.

tsocks role is to allow these non SOCKS aware applications (e.g telnet, ssh, ftp etc) to use SOCKS without any modification. It does this by intercepting the calls that applications make to establish network connections and negotating them through a SOCKS server as necessary. If youre on a network firewalled from the internet with a SOCKS server for outside access, telnet cant use this server and thus cant telnet out to the Internet., sou you cannot get out.

tsocks is based on the shared library interceptor concept. Through use of the LD_PRELOAD environment variable or the /etc/ld.so.preload file tsocks is automatically loaded into the process space of every executed program. From there it overrides the normal connect() function by providing its own. Thus when an application calls connect() to establish a TCP connection it instead passes control to tsocks. tsocks determines if the connection needs to be made via a SOCKS server (by checking /etc/tsocks.conf) and negotiates the connection if so (through use of the real connect() function )

Socks via HTTP provides a socks tunnel via HTTP.

Socks via HTTP is a program converting SOCKS requests into HTTP requests and tunnelling them through HTTP proxies if needed.

The SOCKS protocol allows programs to traverse firewalls on any port number and is used by many popular programs, like Napster, MSN Messenger, CRT(telnet client) and many others.

Many companies restrict firewall traversals only to HTTP requests, disabling SOCKS proxy.

Socks via HTTP provides a miniature SOCKS server for the SOCKS client, performing its connection through an HTTP proxy to a remote server, which establishes the real connection.

Socks via HTTP is 100% Java, and can run on any OS. It is entirely written in Java.

SS5 is a socks server that implements the SOCKS v4 and v5 protocol. As a proxy server, SS5 authenticates, profiles and processes network requests for clients.
Socks Server 5 establishes connections to application hosts for client applications. When the client attempts to access the network, the client connects to the SS5 daemon instead of the application host.
Following authentication, clients request that SS5 perform network activities for the client.
The activities might include:
CONNECT
BIND
UDP ASSOCIATE
The SS5 protocol is independent of application protocols, and can assist with different networking services, including telnet, ftp, finger, whois, gopher, and WWW access.
Enhancements:
- Fix code

bufsock.py is a python module that makes it a little bit easier to work with sockets, and may also make your I/O faster if youre reading and/or writing lots of tiny packets.

Also, you may find that it makes your network applications more reliable, as the network is allowed to split apart your packets into multiple smaller packets, or aggregate two or more packets into one larger packet, if it decides it needs to do so for reliability or performance.

So you might do a s.recv expecting to get one line of input, but the network decided to batch together two remote s.sends into one s.recv, for example. But the network usually, but not always, will batch up your packets the way youd expect - so this can be a difficult problem to track down.

It supports the following methods:

read(length) brings in a specific number of bytes.
readto(char) reads up thru the next occurence of char
readtomax(char,length) reads up thru the next occurence of char, or length bytes, whichever is less
set_chunk_len(length) says "do reads and writes in increments of length". The chunk length defaults to 4096. You should make this larger on networks that employ jumbo frames to squeeze out more performance!
send(buf) writes the bytes in buf.
flush() is just like stdios (the C librarys) flush function. Call it when you want an output buffer flushed (written immediately).
shutdown(v) just like for a regular socket, except it flushes first.

Usage:

Code snippet:
sock = socket.socket(socket.AF_INET,socket.SOCK_STREAM)
sock.connect((hostname,port))
bs = bufsock.bufsock(sock)
version = bs.readto(n)
print version

Scam-Archiver project copies all mail going through your mail server to a mailbox. This feature is useful for archiving email.

NOTICE

Scam-archiver should only be used if its features is in full compliance with local laws and regulations regarding electronic communication and email.

Installation

Please read the INSTALL and README files for more information.

Prerequisites

You should have sendmail version 8.12.x or higher installed. Sendmail should have been built with MILTER support enabled.
You should have the milter library and development kit installed

Build

1. Extract the scam-archiver tarball
2. Change the current directory to the one where the scam-archiver source code was extracted.
3. If you are using FreeBSD, OpenBSD or NetBSD, rename the Makefile.bsd file to Makefile

If you are using a Linux distribution, rename the Makefile.linux file to Makefile

4. Type make and press Enter to compile scam-archiver

Install

1. Copy the scam-archiver file created above to the appropriate location (/usr/local/sbin for example)
2. Generate a new sendmail configuration (sendmail.cf) with the following additional settings:

INPUT_MAIL_FILTER(`scam-archiver, `S=unix:/var/spool/scam/scam-archiver.sock, F=T, T=S:240s;R:240s;E:5m)dnl
3. Create a user (scamarchiver for example) which will be used to run the milter
4. Create the /var/spool/scam directory
5. Verify that the user created in step 3 has read-write access to the /var/spool/scam directory

Using Scam-archiver

Startup

1. Start scam-archiver milter as a daemon scam-archiver -p unix:/var/spool/scam/scam-archiver.sock -u scamarchiver -D
4. Restart sendmail if you have generated a new sendmail configuration when installing scam-archiver

Shutdown

Type the following command to stop scam-archiver kill -USR1 `cat /var/spool/scam/scam-archiver.pid`

Configuration

The configuration file used is /etc/mail/scam.conf.

The following entry defines the email address where all mail is archived.

AchiverAddr=scam@example.com

Cone project is a text-based mail client. Cone seamlessly handles multiple POP3, IMAP accounts, and local mail folders.
Cone is also a simple newsreader. Cones interface is foolproof enough to be used by inexperienced users, but it also offers advanced features for power users.
Main features:
- An online tutorial provides a quick overview of Cones main features.
- A built-in text editor for editing new messages, with search/replace and spell checking (requires aspell or pspell).
- Shortcuts - assign frequently used text to a function key, or to an abbreviation. Insert the text by pressing the function key or typing its abbreviation.
- Supports UTF-8 consoles (requires the wide-character version of the curses library).
- Displays HTML mail, with automatic de-moronization ("smart quotes", and similar clutter, is replaced by plain garden-variety punctuation).
- Displays attached images, if invoked from an X terminal, by running Gnomes eog, or KDEs kview image viewer. Displays PDF attachments by running xpdf. Other, or alternative, helper applications will be added as time permits.
- After attachments are downloaded, they can be optionally removed from the message.
- Handles local mail folders, maildirs, IMAP and POP3 accounts, and Usenet newsgroups. All folders are shown in a hierarchical tree-like display.
- Supports access to servers through a Socks 5 proxy, using the Courier Socks 5 API toolkit.
- Sends mail using an external SMTP server (with/without authentication), or the local sendmail command.
- All network protocols support SSL/TLS and SASL (CRAM-MD5, CRAM-SHA1, and LOGIN).
- Address books (which can be stored in an IMAP folder).
- Remote configuration (share a common configuration between different instances of Cone).
- An optional "single sign-on". Use a single master password for multiple remote mail server accounts.
- PGP/GPG based encryption, and digital signatures. Sent messages are automatically signed. Different signing keys may be selected for different mail accounts, and the appropriate key is automatically selected when replying to a message from an account. Selecting a message for an encryption automatically looks up keys that match the recipients E-mail addresses.
- Import, export, forward and receive PGP/GPG keys as MIME attachments.
- When a single sign-on master password is installed, the master password also handles access to passphrase-protected keys.
- Cone shares a lot of its code base with the Courier mail server, which is why they share the same web site together.
- Cone also serves as a platform for development of a new experimental network mail access protocol, SMAP, that offers additional functionality not available with IMAP or POP3.
- Cone owes its versatility in handling a large variety of mail protocols to the fact that its based on LibMAIL, a generic C++ library that provides a high-level mail-handling API. Using the --with-devel configuration setting installs the LibMAIL toolkit, which allows for development of independent E-mail software.
Enhancements:
- This release fixes a bug in GPG signing of multi-part messages whose main content contains 8-bit text.

bogom is a simple sendmail milter to interface bogofilter.
SYNOPSIS
bogom [-R | -D] [-t] [-v] [-u user] [-s conn] [-b bogo_path] [-x exclude_string] [-c conf_file] [-l body_limit] [-p pidfile] [-f forward_spam] [-q quarantine_mdir] [-d]
The bogom plugin can be used with the milter API of sendmail(8) to filter mails using bogofilter(1) bayesian filter.
bogom is intended to be used with only one words database for the whole system.
The options are as follows:
-R Reject mail classified as spam
-D Discard mail classified as spam
-t Train bogofilter with the mail classified as spam/ham
-v Verbose logging
-u user User to run the milter. Default: bogofilter
-s conn Path to the pipe to connect sendmail. Default:
unix:/var/spool/bogofilter/milter.sock
-b bogo_path Path to the bogofilter(1) binary. Default:
/usr/local/bin/bogofilter
-x exclude_string If this string is found in the Subject of a message,
it will be automatically accepted and no filtering op-
eration will be done.
-c conf_file Path to the configuration file. Default:
/etc/bogom.conf
-l body_limit Length limit in bytes to be processed from mail body.
The rest of the body will be discarded and not ana-
lyzed by the filter. Default: no limit
-p pidfile Path to the file to store the pid of the milter. The
pidfile is created after the milter drops privileges
and the user to run the milter must have write permis-
sion to the specified file. Default:
/var/spool/bogofilter/bogom.pid
-f forward_spam Set a recipient to forward any message classified as
spam. Read configuration file section for further de-
tails.
-q quarantine_mdir
Path to a directory to deliver a copy of any message
classified as spam. The messages are stored in
maildir(5) format.
-d Enable debug messages (implies verbose logging)
Default policy is to add the X-Bogosity header (Yes, No, Unsure) and deliver the mail. This can be changed with -R or -D when bogofilter classifies the mail as spam.
In bogofilters configuration the bogofilter_dir token should be set to the directory with system database, usually /var/spool/bogofilter, in bogofilters configuration, or simply the words database of the unprivileged user running the milter can be used.
bogom uses a temporal file to store each individual message and forks a new process to scan it with bogofilter. This temporal file uses /tmp directory by default, its owned by the user running the milter and has 0600 mode. When a directory is specified in quarantine_mdir, the tmp subdirectory in that maildir is used as temporal directory.
The option -t registers the mail after classifying it as spam or ham. This option can be dangerous because the filter may register errors, so you should read carefully bogofilters manual regarding this point.
Enhancements:
- Support for spamicity score in the X-Bogosity header has been added.

The Sambar Server is an open and scalable framework that provides an intuitive, secure and personalizable environment for end-users; rapid development and deployment tools for developers; and an easy-to-use console for administrators.
Main features:
- WebDAV
- Content Management
- Document Versioning
- Search Engine
- Mail Server
- Servlet Runner
- Usage Throttling
- CRON Daemon
- IRC Server
- FTP Server
- TFTP Server
- DNS Server
- DHCP Server
- Proxy Server
- Socks Proxy
- Reverse Proxy