Free instance message software for linux

Secure Messaging is a Web-based, alternative mail system for sending and receiving messages.

Use secure messaging to send and receive messages from a alternative web-based mail system. Using the secure messaging system no actual mail is transmitted through any 3rd party servers.

Only an optional message notice is sent to the recepient, the user needs to visit the site in order to read the message.

Normal SMTP mail can hit multiple servers and can possibly be read, stored, or changed anywhere within the process.

Setup secure messaging on an SSL enabled website to enhance the privacy even more.

THCNET Message System project is a customizable PHP-enabled Web application which provides a moderated message system using a backend MySQL database.
Installation
download and install MySQL. download and install apache with mod_rewrite
and php4 or php5 compiled with the pspell libraries.
note: I use MySQL 5.0 and PHP 5.1 in development of THCNET, but it should
work with earlier versions.
do the following
modify the *.template *.css files to make things look how you want
modify the any and all source code as you see fit.
As of release 1.0.pre5 thcnet has an auto-installer/revision control
feature that makes the initial setup much easier.
copy all the files into your htdocs directory on your web server
open index.php in your browser. It will prompt you for values it needs
to perform the installation. Click on setup and it will create the
database for you and populate it.
Now that you have THCNET setup, the first task will be to apply as a new
user. The first user to apply will be given sys-admin rights.
Now you can customize features by clicking on the Admin link to the
left.
Enhancements:
- This release adds the ability to further control the system based on policy maps.

Wily::Message is a Perl extension to handle Wily Messages.

SYNOPSIS

use Wily::Message;
use Wily::Connect;

# opens a file in wily and exits when the window is destroyed

my $win_id;

my $ws = Wily::Connect::connect();

my $wm = Wily::Message->new(Wily::Message::WMnew, 0, 0, 0, 1,
/tmp/file_to_edit);
$ws->syswrite($wm->flatten());

my $buffer = ;
until (Wily::Message::complete_message($buffer)) {
$ws->sysread($buffer, 1024, length($buffer));
}

$buffer = $wm->from_string($buffer);

if ($wm->{type} == Wily::Message::WRerror) {
die "Error WMnew: $wm->{s}n";
} elsif ($wm->{type} == Wily::Message::WRnew) {
$win_id = $wm->{window_id};
$wm = Wily::Message->new(Wily::Message::WMattach, $win_id, 0, 0,
Wily::Message::WEdestroy);
$ws->syswrite($wm->flatten());
until (Wily::Message::complete_message($buffer)) {
$ws->sysread($buffer, 1024, length($buffer));
}
$buffer = $wm->from_string($buffer);
if ($wm->{type} == Wily::Message::WRerror) {
die "Error WMattach: $wm->{s}n";
} elsif ($wm->{type} == Wily::Message::WRattach) {
} else {
die "Expected a WRattach, but didnt get one";
}
} else {
die "Expected a WRnew, but didnt get one";
}

while (1) {
until (Wily::Message::complete_message($buffer)) {
$ws->sysread($buffer, 1024, length($buffer));
}
$buffer = $wm->from_string($buffer);
if ($wm->{type} == Wily::Message::WEdestroy and $wm->{window_id} == $win_id) {
last;
}
}

A simple object wrapper around Wily messages with a helper function to assist in extracting messages from the wily connection.

Debug::Message is a Perl module that eases the use of debug print with level, indentation and color.

SYNOPSIS

use Debug::Message;
use Log::Dispatch;
use Log::Dispatch::Screen;

my $dispatcher = Log::Dispatch->new;
$dispatcher->add( Log::Dispatch::Screen->new( name => screen,
min_level => 0 ));

my $info = Debug::Message->new(1);
$info->add_dispatcher($dispatcher);
$info->print("print");
$info->yellow("warn");
$info->red("err");
$info->printcn("error message", bold red);

my $critical = Debug::Message->new(5);
$critical->add_dispatcher($dispatcher);
$critical->redn("err");
For disabling the debugging simply do not attach any dispatchers.
$critical->disable; # Will detach the attached backend

There was no module for simple debug messages supporting debug/verbosity levels and indentation. So this is the one, that is supposed to take this place.
This module is an art of frontend to Log::Dispatch as Log::Dispatch itself supports levels, but no colors and the functions calling is tedious.

There are some methods defined. Each outputs a different color, optionally it can add a newline after the messaage. They dispatch the messages to all added dispatchers, but generaly only one will be needed as the Log::Dispatch itself can have more backends.

Genoa Active Message MAchine is a low-latency, high-throughput driver wrapper for the Linux kernel, using Active Ports (a version of Active Messages).
Genoa Active Message MAchine runs parallel to the IP stack and is designed for LANs only.
Main features:
- A low latency, high throughput communication system for clusters of PCs
- Supports both single and dual CPU processing nodes (Intel IA-32 or x86_64)
- Runs on Gigabit Ethernet
- SPMD parallel processing with message passing
- Can run IP traffic when not in use
- Good programmability thanks to fairly high abstraction level
- Reliable thanks to mechanisms for retransmission of missing packets
- Implemented as a network device driver for Linux 2.6, and released under GNU GPL
Network Of Workstations (NOWs) and clusters of PCs interconnected by modern, industry-standard LAN fabrics (Gigabit Ethernet, Myrinet, SCI) and running the Linux operating system, have became an attractive and cost-effective architecture for parallel and distributed applications. The usual drawback of a standard PC cluster is the poor performance of the support to inter-process communication over the interconnect. Current implementations of industry-standard communication primitives, APIs, and protocols, usually show high communication latencies and low communication throughput.
We have developed a system for inter-process communication, called the Genoa Active Message MAchine (GAMMA). GAMMA runs on Linux clusters of PCs with Intel IA-32 processors (Intel Pentium, AMD K6, and superior models), or x86_64 processors (AMD Athlon64, AMD Opteron, Intel EMT-64), networked by a Gigabit Ethernet.
The core of GAMMA is a custom Linux network device driver, which operates the Network Interface Card (NIC). The GAMMA driver delivers low latency, high throughput communication services based on Active Ports, a mechanism derived from Active Messages. Both point-to-point and broadcast communications are provided. Broadcast communication exploits the Ethernet broadcast directly.
The GAMMA driver is able to manage standard IP traffic as long as no parallel job is running. Therefore, all IP services are up and running whenever the cluster is not in use by any parallel job.
The communication mechanisms implemented in the GAMMA driver are made available to application writers through the GAMMA user library. The GAMMA library provides support to application launch, process grouping, point-to-point/broadcast communications based on the Active Ports mechanisms, and some collective routines (barrier synchronization, and broadcast).
GAMMA provides two levels of QoS. The lower one, corresponding to the fastest communications, is a best-effort service. With this service, network congestion and ``hot spots may cause the receiver NIC or even the LAN switch to loose packets by overrun. The other QoS level provides flow-controlled communication, ensuring reliability up to hardware faults, at a negligible performance penalty.
Installing the GAMMA driver requires only two small and marginal patches to the original Linux kernel. The Linux kernel extended by the GAMMA driver must be installed on each PC in the cluster.
A porting of MPI atop GAMMA is available, called MPI/GAMMA.

Mail::Message::Body is the data of a body in a message.

INHERITANCE

Mail::Message::Body has extra code in
Mail::Message::Body::Construct
Mail::Message::Body::Encode

Mail::Message::Body
is a Mail::Reporter

Mail::Message::Body is extended by
Mail::Message::Body::File
Mail::Message::Body::Lines
Mail::Message::Body::Multipart
Mail::Message::Body::Nested
Mail::Message::Body::String

Mail::Message::Body is realized by
Mail::Message::Body::Delayed

SYNOPSIS

my Mail::Message $msg = ...;
my $body = $msg->body;
my @text = $body->lines;
my $text = $body->string;
my IO::Handle $file = $body->file;
$body->print(*FILE);

my $content_type = $body->type;
my $transfer_encoding = $body->transferEncoding;
my $encoded = $body->encode(mime_type => text/html,
charset => us-ascii, transfer_encoding => none);n";
my $decoded = $body->decoded;

The encoding and decoding functionality of a Mail::Message::Body is implemented in the Mail::Message::Body::Encode package. That package is automatically loaded when encoding and decoding of messages needs to take place. Methods to simply build an process body objects are implemented in Mail::Message::Body::Construct.

The body of a message (a Mail::Message object) is stored in one of the many body types. The functionality of each body type is equivalent, but there are performance differences. Each body type has its own documentation with details about its implementation.

SpamBayes is a Bayesian anti-spam classifier written in Python. The major difference between this and other, similar projects is the emphasis on testing newer approaches to scoring messages.

While most anti-spam projects are still working with the original graham algorithm, we found that a number of alternate methods yielded a more useful response.

Thats great, but whats SpamBayes?

SpamBayes will attempt to classify incoming email messages as spam, ham (good, non-spam email) or unsure. This means you can have spam or unsure messages automatically filed away in a different mail folder, where it wont interrupt your email reading. First SpamBayes must be trained by each user to identify spam and ham. Essentially, you show SpamBayes a pile of email that you like (ham) and a pile you dont like (spam). SpamBayes will then analyze the piles for clues as to what makes the spam and ham different. For example; different words, differences in the mailer headers and content style. The system then uses these clues to examine new messages.

For instance, the word "Nigeria" appears often in spam, so you could use a spam filter which identifies anything with that word in it as spam. But what if your business involves writing a guidebook on Nigerian Wildlife Conservation? Clearly a more flexible approach is necessary. Additionally spammers will adapt their content over time and will no longer use the word "Nigeria" (or the words "Lose Weight Fast", or any number of other common lines). Ideally the software will be able to adapt as the spam changes.

So, that is what SpamBayes does. It compares the spam and the ham and calculates probabilities. For instance, for me, the word "weight" almost never occurs in legitimate email, but it occurs all the time in lose weight fast spam. SpamBayes can then look at incoming email, extract the most significant clues and combine the probabilities to produce an overall rating of "spamminess". It flags the messages so that your mailer can handle the different message types. You might set it up so that ham goes straight through untouched, spam goes to a folder that you ignore (or delete without checking) and the unsure messages go to another folder which you can review for errors.

Call this script from the Autostart folder, and it will update Kopetes away message for each interval (requires Kopete 0.12 or higher). The away messages are by default defined in ~/.kopete-away-msgs. Each line can contain either:
- a comment (starting with a #)
- flags message
The flags define some properties to each away message. Flags are defined only at the start of the line, beginning and ending with a %. The following flags are supported.
[0-9]*[smhd] Determines how long this message should be shown before a new one is chosen. This is the sleep(1) syntax.
a Only show this message when youre away.
c This line is a command, use its output as away message.
i Show the contents of a file, line by line. The message should contain the path to the file. Do not use ~ but use /home/$USER instead. Empty lines in the included file are skipped.
n Use the next message in the file for the next iteration.
o Only show this message when youre online.
x Dont use this message when looking for a random message. This means this line is only accessible when the former line contains the n flag.
- Show the message less than normal times
-- Show the message even more less
--- Show the message sometimes
To determine your online status, you need to have the Web Presence plugin enabled. By default, it reads the file ~/.webstatus.xml. Adapt the variable below if you store the file somewhere else. The script wont do anything when youre offline or partially away (that is, some protocols are Away, some protocols are Online).
Because the web status plugin is used, the process of retrieving the current webstatus is not really reliable. It may happen that you turn back to online when you set the status on Away in a short time. If this doesnt happen in about 10 seconds after the status change, you may consider the status change as successful.
Example ~/.kopete-away-msgs file:
========================================================================
# Sometimes, show uptime for one minute
%1mc--% uptime
# Fortune rocks, but dont pick too long messages (the length of away
# messages is limited.
%2mc% fortune -s -n 120
# just show Hello world for the default interval
Hello world
# Show a away message for 60 seconds.
%a60% Im away now.
# Ask people to say something when youre online
%o% Please message me!
# Show all contents of the Linux README line by line. Show each line for
# 3 seconds.
%3i% /usr/src/linux/README
# Tell a little story when Im away. These lines must emerge in the
# right order, so mind the n and x flags! The x flags make sure we dont
# start in the middle of the story. And, show each line for about 5
# seconds.
%na5% Goodbye, all you people,
%nax5% Theres nothing you can say
%nax5% To make me change my mind.
%ax5% Goodbye.
==================================================================
Enhancements:
- Ability to query the online/away status directly from Kopete (DCOP). This requires a patched Kopete, see the description for more details on how to proceed.
- Fortune mode: Pick a random line from a given text file.
- First check the online/away status to prevent unnecessary command calls.
- Various bugfixes