Free away messages 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.

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.

cintoo Messages is a framework to make internationalization easier for Java applications. cintoo Messages framework supports locales for threads, and bundles can be associated with different packages.

This allows the usage of different bundles for different parts of the application, such as plugins, an installer, or a logging system. Bundles can be managed and associated with packages without any changes in the code.

This makes bundle management and refactoring much easier than with other solutions. cintoo Messages supports global locales for client applications written in Swing or SWT and thread-local ones for serverside Web applications.

Example:

Messages.setBundle("myBundle", "only.for.this.package");
...
Messages.setThreadLocale(new Locale("en", ""));
...
Messages.format(this, "myKey");

ebXML::Message is a Perl module to encapsulate an ebMS message.

SYNOPSIS

use ebXML::Message;

# create new message

my $message = ebXML::Message->new
(
CPAId => http://www.you.org/cpa/123456,
Action => NewPurchaseOrder,
MessageId => 12,
RefMessageToId => 11,
Service => ebXML::Message::Service->new
(
VALUE => QuoteToCollect,
Type => myservicetypes,
),
);

# write SOAP XML using DOM

use XML::Xerses;

# DOM Document
my $target = XML::Xerces::StdOutFormatTarget->new();
$writer->writeNode($target,$message->getOutput(DOM-Doc);

# DOM generated / munged XML
print OUT $message->getOutput(DOM-XML);


# use message with SOAP::Lite to call webservice

use SOAP::Lite;

# SOAP::Data::Builder object
my $result = SOAP::Lite->uri(http://uri.to/WebService)
->proxy(http://uri.to/soap.cgi)
->parts($message->getMIMEParts)
->call($message->getOutput(SOAP-Data))
->result;

# SOAP::Data::Builder generated / munged XML
print OUT $message->getOutput(SOAP-XML);

An ebXML message encapsulates all the details of an ebMS message.
ebXML is a mechanism for ensuring reliable delivery of XML-based messages via a transport mechanism such as SOAP. For more details on ebXML, see http://www.ebxml.org/
Large portions of this manual page are copied directly from the ebMS 2.0 specification.

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.

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.

KMess program is a MSN messenger for KDE.
Main features:
- MSN Messenger protocol compatibility
- Font and font color support, including the ability to force contact messages to appear in a particular font and color.
- Full emoticon support, featuring a custom GPLed emoticon set and the ability to use different emoticon themes.
- File transfer support, both sending and receiving.
- Picture transfer support.
- Hotmail support, with new email notifications, the inbox count, and the ability to open Hotmail at the users inbox or at the composition page.
- The ability to disable and hide email information for accounts that dont use Hotmail.
- Support for multiple user profiles.
- Autologging, either at the setting page for from the commandline (with "kmess --autologin blah@hotmail.com" for example).
- A contact list that can organize contacts by group or by online/offline status.
- Groups show a count of the contacts online (i.e. "Friends (2/5)")
- The user can specify particular contact images and sounds to be displayed when a contact comes online or in a chat.
- The user can specify a name for a contact, overriding the contacts specified name.
- The user can choose on a contact-by-contact basis whether the user should be notified when a particular contact comes online or goes offline.
- KMess can show a contacts MSN profile, and open the MSN search pages.
- In addition to the usual user statuses of "Away" and "Busy" and so on, there is the status "Away with Autoreply" that will reply to contacts chat messages with a user-specified away message.
- The chat window has been redesigned with a new sidebar (which can be toggled with Ctrl+T) with an emphasis on contact images.
- The chat window notifies the user that a contact is typing by "glowing" the contacts image.
- Chats can be logged automatically and the chats ordered in subdirectories by day, week, or month, or not ordered at all.
- Chats can be configured to show timestamps when contacts send messages.
- A "compact" chat format can be used to remove extraneous line breaks and reduce the size of the chat.
- The chat window caption in the taskbar alternates between lower and upper case to inform the user of a received message when the window is not on top.
- Internationalization support, with translations in: English, Dutch, German, Italian, Portuguese, Spanish, Turkish, Chinese, French, Catalan, Arabic, Korean, Norsk, and Thai
- There is now a method, though not absolute, to tell if a contact is blocking you. If a chat is started with a contact that appears offline, you will be informed if the contact is offline or online and blocking you.
- NetMeetingGnomeMeeting and GnomeMeetingGnomeMeeting invitations are supported.
- Users can start as invisible rather than online.
- Users can have blank, unsaved passwords but retain user settings.
- Text can be formatted with /italic/, _underlined_, and *bold*.
- Groups can be reordered.
- You can show or hide offline contacts.
- Emoticons are shown in the contact list.
- Contacts can be dragged to move between groups and dragged into a chat to be invited to it.
- A background picture was added to the contact list.
Enhancements:
- This release fixes some critical issues in 1.5-pre1.
- The most important bugfixes are better support for direct file transfer connections and links in the chat window.
- There are also some nice improvements, like file transfer previews and "now playing" information.
- The chat window has some new features.
- Writing links as slashdot.org or dot.kde.org works as well.
- Its possible to disable the shaking effect of a nudge.

Gtk2::Ex::Dialogs::Message provides a simple message dialog.

SYNOPSIS

use Gtk2::Ex::Dialogs::Message ( destroy_with_parent => TRUE,
modal => TRUE,
no_separator => FALSE );

# do some stuff like creating your apps main $window then,
# to ensure that all messages use the right parent, set it:
$Gtk2::Ex::Dialogs::Message::parent_window = $window;

# now popup a new dialog ( blocking the main loop if there is one )
new_and_run
Gtk2::Ex::Dialogs::Message ( title => "Dialog Title",
text => "This is a simple message" );

# now popup a somwhat useful dialog that doesnt block any main loop
# but on the other side of the coin, if there is no main loop the
# dialog will be completely unresponsive.
new_show
Gtk2::Ex::Dialogs::Message ( title => "Uhm",
text => "Use when there is a main loop." );

This module provides a simple dialog api that wraps Gtk2::Dialog objectively. The objective is a clean and simple message dialog (only an "OK" button).