Free reliably delivered messages software for linux

Sendmail delivery stats is a Perl script to analyze Sendmail log files and produce mean delivery times. It dumps all data in CSV format.
Recently I had to bear with mail server analyze, serving traffic on level +10k messages a day. And there were some degradation of services felt by users, but there was no stright pattern what mails are delivered with bigger latency. Since this was Sendmail powered site I wrote simple tool in Perl to help with analysis.
I hope it is simple to use. What it does ? It collects all log entries, which are related to successful mail delivery. Groups it by domain and calculates average delivery time (time to leave queue - I is rather impossible to estimate time spend in others servers queues). Most useful (for me) is -a option, which makes all output in CSV format, for easy use in further analysis.
It was tested on logs from Sendmail 8.13.x and I belive it calculates proper values.
Enhancements:
- The HTML output format was added, with possible template use.
- Output is now sorted.
- Minor bugfixes and code cleanup were done.

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.

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.

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.

Smarty and MIME message integration is a PHP class library that can send e-mail messages using Smarty templates.

This package can be used to compose and send e-mail messages using Smarty templates.

It wraps around Smarty and MIME message class by Manuel Lemos, and prepares the body and headers of the messages to send.

It can set several message options at once passing an array of options values.

Currently it supports options to define HTML or text message template files, the sender, recipient, bounce and reply names and addresses, whether to send messages in plain text, HTML or both, whether to automatically wrap the message text, message character set, and the bulk precedence header to prevent that notification messages be returned due to temporary delivery errors.

Once the message options are set, the class composes and send message according to the specified option values.

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).

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.