Free email client applications software for linux

Mnemona GUI Client is a Java application that provides a GUI interface for accessing sets in a trove managed by a Mnemona Trove Server.

It communicates with the trove server via Java RMI and supports SSL.

It uses the same GUI design as Fingerstring. It contains a full range of commands for creating, searching, and modifying Mnemona sets.

It also has a command for creating users, so it can be used (by a root user) to manage a Mnemona trove server. Commands are invoked through a standard menu arrangement.

MiniUPnP Client and Daemon is an UPnP IGD client lightweight library and UPnP IGD daemon.
The UPnP protocol is supported by most home adsl/cable routers and Windows 2K/XP. The aim of the MiniUpnp project is to bring a free software solution to support the "Internet Gateway Device" part of the protocol.
The Linux SDK for UPnP devices (libupnp) seems too heavy for me. I want the simplest library possible, with the smallest footprint and no dependencies to other libraries such as XML parsers or HTTP implementations. All the code is pure ANSI C.
Compiled on a x86 PC, the miniupnp client library have less than 15KB code size. For instance, the upnpc sample program is around 20KB.
The project is divided in two main parts : the client library, enabling applications to access the services provided by an UPnP "Internet Gateway Device" present on the network, and the miniupnpd daemon, providing these services to your network from a linux or bsd box being the gateway. At the moment the miniupnpd is developped on OpenBSD 3.0+ with pf. You can see some of the work I have done to integrate with pf on this page.
As pf is also available under FreeBSD, guys at the pfSense project have ported miniupnpd to this system.
For some reasons, it may be not the good solution for you to use the code from the MiniUPnP project directly.
As the code is small and simple to understand, it is a good base to take inspiration for your own UPnP implementation. The KTorrent team UPnP plugin in C++ is a good example.
If you are wondering which home router is working with the miniupnp client, you can find the answer here. In fact, you are more likely to help me fill the list by sending me an email.
Usefulness of the miniUPnP client library
The usage of the miniUPnP client library is useful whenever an application needs to listen for incoming connections.
Examples : P2P applications, FTP clients for active mode, IRC (for DCC) or IM applications, network games, any server.
The typical usage of UPnP capabilities of a router is a file tranfert using MSN messenger. The MSN Messenger software uses the UPnP API of Windows XP to open port for incoming connection. To mimic the MS software, it is a good idea to use UPnP as well.
Enhancements:
- This release adds changes to accommodate the Linux 2.6.22 kernel.

Claws Mail Extra Plugins package contains plugins for Sylpheed-Claws e-mail client.
Claws Mail is the extended version of Sylpheed, a GTK+ based, lightweight, and fast email client. Almost all commands are accessible with the keyboard.
It also has many features such as multiple accounts, POP3/SMTP/IMAP/NNTP support, OpenSSL, GnuPG, and LDAP support, a plugin system, spell checking, filtering, Actions, spam and virus filters, an address book, internationalization, and more.
As the mechanism offered by Claws Mail to add new plugin functionality is under active development it is subject to change, therefore the required version is also given. The author has verified that the plugin works with this required version, however it may or may not work with other versions.
Enhancements:
- This release contains 15 plugins.
- It fixes a bug in the PDF Viewer plugin with GTK 2.6.x where the button images were not shown.

reacTIVision is an open source, cross-platform computer vision framework for the fast and robust tracking of fiducial markers in a real-time video stream. reacTIVision project was mainly designed for the rapid development of table-based tangible user interfaces.

Its tracking core is using Ross Bencinas fidtrack library which is basically a newer high-performance implementation of Enrico Costanzas original d-touch concept. This framework was developed by Martin Kaltenbrunner et.al. at the Music Technology Group, IUA, UPF in Barcelona, Spain as part of the reacTable* project, a novel electro-acoustic musical instrument with a tangible user interface.

reacTIVision is a standalone application, which sends OpenSound Control messages via a UDP network socket to any connected client application. It implements the TUIO protocol, which was specially designed for transmitting the state of tangible objects on a table surface. This framework includes a set of free example client projects for various programming languages, which serve as a base for the easy development of tangible-user interface applications.

The reacTIVision application compiles and runs under the follwing operating systems: Win32, MacOS X and Linux. Under Win32 it suports any camera with a proper WDM driver, such as USB, USB2, FireWire and DV cameras. Equally under MacOS X any such camera supported by QuickTime will work in reacTIVision. Under Linux, FireWire cameras are best supported, as well as a few Video4Linux USB cameras.

NEW: Support the reacTIVision project and buy T-Shirts, posters and other merchandise featuring the reacTIVision fiducial symbols in our web-shop! All designs on these products can be recognized and tracked by the actual reacTIVision software.

Application Handling

Before starting the reacTIVision application make sure you have a supported camera connected to your system. The application can and will not work at all without a camera. Under Win32 and MacOS X the application will ask to select and configure the camera upon startup. Under Linux the camera will be selected automatically. Once configured the application will show a video window with the current camera image in black&white.

Pressing T will show the binary tresholded image, pressing the N key will turn the display off, which reduces its CPU usage significantly!

Pressing the S key will return to the original source image. For convenience and debugging porposes hitting the R key saves a raw image frame, while hitting the B key will save an image in the BMP format.

The P pauses the image analysis completely, hitting ESC will quit the application. The F key toggles the diplay of FPS info in the titlebar. In order to produce some more verbose debugging output, hitting the V key will print the currently recognized symbols to the console.

Command Line Options

The reacTIVision application per default sends the TUIO messages to port 3333 on localhost (127.0.0.1)

In order to change these parameters you can invoke the application with the -h [ip-address] and -p [port-no] options.

reacTIVision needs a so called "tree file" in order to function properly. The default "all.trees" is included and loaded automatically. If you want to use you own tree file you can invoke the application with the -t [tree-file] option.

Optionally if you dont want to analyze the complete image - for example in a square or round table setup - the application can mask a part of the video image with a black region, which speeds up the segmentation algorithm. In order to apply this mask You can invoke the application with the -m [square,circle] option.

Applying the -h or -help option will print a usage message to the console.

Calibration and Distortion

Some tables, such as the reacTable are using a convex mirror in order to increase the area visible to the camera at a minimal distance. This mirror as well as a fish-eye lens unfortunately distort the image. reactIVision includes a correction algorithm, which corrects this distortion with the help of a so called "grid file". These grid files can be generated during a prior calibration process.

To calibrate reacTIVision invoke the application with the option: reacTIVision -c 9 -g [grid_file]

In order to use the this calibration invoke the application with: reacTIVision -g [grid_file]

Kahemba is a client server application written in wxPython.
It support multiple databases, Mysql, Postgresql, Firebird, SQLite.
Kahemba support multi languages using gettext. Kahemba can work in a network and support multi-user. Kahemba runs on Windows, GNU/Linux and MacOS X.
The main pourpose of Kahemba is to act as base to build other applications.
For example I build on Kahemba:
- a simple accounting software
- a contact list
- a dvd-divx film list.
Kahemba is released as GPL free software so you can use, modify and redistribute (sell for money is ok) your work.
If you are requested to build a business application, probably you can get Kahemba, add nedded features and you get quick what you want.
Enhancements:
- This release adds searching for contacts.

Ascension is my attempt at an email client. It makes use of the KDE libraries, so you will need KDE installed if you wish to use it (works with 3.2, might work with 3.1). Although the code is still in alpha, I have been using it as my main email client for over a year.
If you wish to try it, you would be sensible to backup your email first. Using imap should be relatively safe, but pop3 and Unix (local) mailboxes have not been so extensively tested. I take no responsibility for any loss of data while using this program. Ascension has only been tested under Linux.
The current version supports:
- IMAP (not SSL) mailboxes.
- Pop3 (not SSL) mailboxes.
- Unix mailboxes.
- Viewing of HTML messages (no HTML composing).
- Limited searching of headers.
- Dockable parts.
- Fonts and colours are configurable, as is much of the behvaiour.
Still to do:
- Support SSL connections (probably requires a rewrite of a good portion of the mailbox subsystem).
- PGP and S/MIME support.
- Virtual folders.
- A ton of ideas yet to come.
Enhancements:
- This is the first public release

Pluto Request Action Library allows you to create a client/server application, where client sends requests, server replies with responses and optional actions. Very object oriented, and takes only minutes to get going. Same library used for both server & client side.

How does it work?

The client creates "Requests" which it sends to the server. The server will process the request, set some return variables, and can optionally add "Actions" it wants the client to execute in response. An example is a cashiers computer (the client) sends the central credit card processing server a request to "process a credit card", the server responds with the authorization code and also includes an action "give customer a message" which causes a message to appear on the cashiers computer.
Both the client and server use the same library. Both create an instance of RA_Processor.

The only difference is the server calls "ReceiveRequest" and the client creates the actual requests, and calls RA_Processors "SendRequest".
To create a request, just create a class derived from RA_Request. Add some member variables for the request and variables for the response. Your request must be derived from SerializeClass--a base class that facilitates taking an object (a request in this case), serializing the variables into a binary block, and then on the other end reconstructing the class with all the data. The framework handles everything. You just add the data members.

In the above example, the request variables would probably be the credit card information and maybe the customer ID, and the response variables would be the authorization code. RA_Request has a pure virtual function "ProcessRequest" which will be called on the server to handle the request. Both the client and the server have the same Request/Action classes. When the client side passes a request to the RequestProcessor, the framework handles serializing all the request member variables, making the socket connection to the server and sending the request to the server.

On the server, the framework will create an instance of the request class and deserialize all the data and call the "ProcessRequest" member function. That is the only function the server needs to implement. From within ProcessRequest, the server needs to set the response variables. When ProcessRequest returns, the framework will serialize the response variables, send them back to the client, update the clients original request with the response, and execution will continue. Less than 10 lines of code are required to make it work, and the project includes a sample client/server application you can extend.

WebSphere::MQTT::Client is a WebSphere MQ Telemetry Transport Client.

SYNOPSIS

use WebSphere::MQTT::Client;

my $mqtt = WebSphere::MQTT::Client->new( Hostname => localhost );

$mqtt->disconnect();

WebSphere::MQTT::Client
Publish and Subscribe to broker.