Free message software for linux

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.

X Message Daemon is used to overlay graphical information messages on your X display.

You can choose parameters such as color, font, icon, and duration.

It also has a frontend Perl daemon and client.

Installing:

# ./configure
# make
# make install

then edit /usr/local/share/Xmsgd/etc/msgmaild.conf and change the configuration to your preferences.

Basic Usage:

- tailing your /var/log/messages :
# tail -f /var/log/messages | msgclient.pl &

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.

Mail::Message::Convert is a Perl module for conversions between message types.

INHERITANCE

Mail::Message::Convert
is a Mail::Reporter

Mail::Message::Convert is extended by
Mail::Message::Convert::Html
Mail::Message::Convert::HtmlFormatPS
Mail::Message::Convert::HtmlFormatText
Mail::Message::Convert::MailInternet
Mail::Message::Convert::MimeEntity
Mail::Message::Convert::TextAutoformat

SYNOPSIS

Available methods are very converter-specific.

This class is the base for various message (and message parts) converters. When the conversion does not change the contents of the body, most of the converters will return the source object. In any case, an Mail::Message::Body is returned with the conversion applied but as much of the other meta data stored in the source body unchanged.

In most cases, converters are created by Mail::Message when they are needed; have a look at the encode and decoded methods on message objects.

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.

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

Mail::Message::Head::Partial is a subset of header information of a message.

INHERITANCE

Mail::Message::Head::Partial
is a Mail::Message::Head::Complete
is a Mail::Message::Head
is a Mail::Reporter

SYNOPSIS

my $partial = $head->strip;
$partial->isa(Mail::Message::Head) # true
$partial->isDelayed # false
$partial->isPartial # true

$partial->removeFields( qr/^X-/ );
$partial->removeFieldsExcept( qw/To From/ );
$partial->removeResentGroups;
$partial->removeListGroup;
$partial->removeSpamGroups;

Header information consumes a considerable amount of memory. Most of this information is only useful during a short period of time in your program, or sometimes it is not used at all. You then can decide to remove most of the header information. However, be warned that it will be lost permanently: the header (and therefore the messsage) gets mutulated!