Free messaging 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.

simple instant messaging (sim) is an IRC client specialized for use with bitlbee. It is based on sic (http://suckless.org). It reads commands from standard input and prints all server output to standard output.
simple instant messaging also multiplexes all channel traffic into one output, so you dont have to switch to different channel buffers. sim must be customized by editing its source code to insert the correct username, server, password, and identification information.
Enhancements:
- The command operator was changed.
- Some code simplifications were done.
- The output format was adjusted.

Mobile::Messaging::ParlayX is a Perl interface to ParlayX OSA.

SYNOPSIS

use Mobile::Messaging::ParlayX;

Mobile::Messaging::ParlayX is an interface to ParlayX web service by Sony Ericsson for SMS and MMS messaging, among other things. This being a Web Service SOAP::Lite would probably be better suited to the task, but I decided to stick with LWP::UserAgent, HTTP::Request and XML::LibXML until things in SOAP::Lite stabilize (it is currently under rewrite as far as I know) and I have more time (not that this will happen anytime soon).

Besides, I cannot fully grasp ParlayX just yet, thanks to inadequate documentation and JAVA only code samples for it. Anyway, you need LWP::UserAgent, HTTP::Request and XML::LibXML for this module to work. Most are in the standard distribution already, but any of them are available at your local CPAN mirror.

I tried not to stray too far off the ``native JAVA names of methos and properties, but chances are some differences exist.

Akeni Instant Messaging - Pro is a client/server instant messaging platform that allows companies to host their own secured private IM system. The client has an user interface similar to AIM, ICQ, or MSN Messenger. It supports all the standard IM features such as chat, group conference, presence management, file transfer, offline messages and emergency alert/notification. Extra features include contact management and optional tabbed chat sessions.

The server has administration tools like managing user accounts, client-side logging capabilities and peer-to-peer file transfers. Akeni Pro Messenger can be setup on a private network without connecting to the internet and can easily be setup for use inside and outside the company firewall.

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.

Locale::Messages is a Perl module with Gettext Like Message Retrieval.

SYNOPSIS

use Locale::Messages (:locale_h :libintl_h);

gettext $msgid;
dgettext $textdomain, $msgid;
dcgettext $textdomain, $msgid, LC_MESSAGES;
ngettext $msgid, $msgid_plural, $count;
dngettext $textdomain, $msgid, $msgid_plural, $count;
dcngettext $textdomain, $msgid, $msgid_plural, $count, LC_MESSAGES;
textdomain $textdomain;
bindtextdomain $textdomain, $directory;
bind_textdomain_codeset $textdomain, $encoding;
bind_textdomain_filter $textdomain, &filter, $data;
turn_utf_8_on ($variable);
turn_utf_8_off ($variable);
nl_putenv (OUTPUT_CHARSET=koi8-r);
my $category = LC_CTYPE;
my $category = LC_NUMERIC;
my $category = LC_TIME;
my $category = LC_COLLATE;
my $category = LC_MONETARY;
my $category = LC_MESSAGES;
my $category = LC_ALL;

The module Locale::Messages is a wrapper around the interface to message translation according to the Uniforum approach that is for example used in GNU gettext and Suns Solaris. It is intended to allow Locale::Messages(3) to switch between different implementations of the lower level libraries but this is not yet implemented.

Normally you should not use this module directly, but the high level interface Locale::TextDomain(3) that provides a much simpler interface. This description is therefore deliberately kept brief. Please refer to the GNU gettext documentation available at http://www.gnu.org/manual/gettext/ for in-depth and background information on the topic.
The lower level module Locale::gettext_pp(3) provides the Perl implementation of gettext() and related functions.