Free message in a bottle police software for linux

Message::Style is a Perl module to perform stylistic analysis of messages.

SYNOPSIS

use Message::Style;

my $score=Message::Style::score(@article);
# or
my $score=Message::Style::score(@article);

This Perl library does an analysis of a RFC2822 format message (typically email messages or Usenet posts) and produces a score that, in the authors opinion, gives a good indication as to whether the poster is a fsckwit, and therefore whether their message should be ignored.

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.

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.

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::Field contains one line of a message header.

INHERITANCE

Mail::Message::Field
is a Mail::Reporter

Mail::Message::Field is extended by
Mail::Message::Field::Fast
Mail::Message::Field::Flex
Mail::Message::Field::Full

SYNOPSIS

my $field = Mail::Message::Field->new(From => fish@tux.aq);
print $field->name;
print $field->body;
print $field->comment;
print $field->content; # body & comment
$field->print(*OUT);
print $field->string;
print "$fieldn";
print $field->attribute(charset) || us-ascii;

This implementation follows the guidelines of rfc2822 as close as possible, and may there produce a different output than implementations based on the obsolete rfc822. However, the old output will still be accepted.

These objects each store one header line, and facilitates access routines to the information hidden in it. Also, you may want to have a look at the added methods of a message:

my @from = $message->from;
my $sender = $message->sender;
my $subject = $message->subject;
my $msgid = $message->messageId;

my @to = $message->to;
my @cc = $message->cc;
my @bcc = $message->bcc;
my @dest = $message->destinations;

my $other = $message->get(Reply-To);

Message Level Authentication for WebMail is a Firefox extension that authenticates mail from Message Level Network users, Mail Reputation provided by Sender Score for each message and Anti-Phishing Data from PhishTank. Registration is FREE but not required.

Currently works with the following web mail providers: Google Mail (GMail), Yahoo Mail and Comcast Mail.

Use these best practices to thwart spam and phishing attempts.

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.

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.