Free messaging solution software for linux

Postfix SMTP Monitoring Solution is a set of three Perl CGI scripts used to monitor the SMTP queue, allowing the deletion of messages that for one reason or another become "stuck" in the queue.

I needed a web-based solution to monitor my Postfix SMTP relay, which enabled me to remove messages that become "stuck" in the queue. I wrote three simple Perl scripts, and used Sudo to give me the desired functionality.

I am uploading these scripts in case they are useful to others. Assuming you have Apache configured correctly on your Postfix server, it should be as easy as placing the three .cgi files into your webservers cgi-bin directory, and making the appropriate modifications to your /etc/sudoers file (see the README contained in the tarball).

E/AS Automation Solutions is open source software system for help automate your solutions even for personal and/or corporate ones.
E/AS written on CLIP language (CA-Clipper dialect, compiler can be obtained from ITK.ru) and uses CODB (CLIP Object Database) as data storage.
Main features:
- client-server technology (both data and interface forms)
- component infrastructure with interaction between components by messages
- interface forms on XML
- MDI
E/AS contains in typical distribution:
- client software written on clip-ui library
- server software with wrapper for run as daemon
- maintenance tools: CODB console and component manager
- base (form, auth) and example (contact) components
Enhancements:
- completely rewrite code for implement E/AS architecture
- component infrastructure
- own server program instead COBRA
- maintenance tools: CODB console and component manager
- base and example components
- autoupdate views

Lua Messaging Engine (LuME) is a set of scripts that offer abstract functions for communication via AOLs OSCAR protocol (as used by ICQ and AIM clients), Microsoft Messengers MSNP, and Yahoos YIM protocol. Lua Messaging Engine also includes utility functions for string operations, SHA hashing, and basic HTTPS communication.

An increasing number of software developers are making use of the simplicity and power behind employing a Lua script interface.

Meetroduction, LLC has been using a Lua script interface as a core design concept for the multi protocol messaging component of its proximity based people finder client: Meetro. Beyond that, the interface offers its users a flexible way to vastly extend the clients functionality.

Fast Messaging Peer to Peer (FM P2P) is a simple P2P program that forms a TCP-based overlay network by which a user may chat or share files.

Why name this FastMessaging when its anything but fast? Simply put, it is a reference to the underlying functioning of the application. TCUP, the protocol used to do the overlay network (the network we build ontop of an existing TCP/IP network) is message based.

We think it is Fast because there is no queueing or long searches. FastMessaging is built to construct moderately sized networks which have reasonably high responsiveness at the cost of global information sharing.

Perhaps thats not the best reasoning, but it works. Its just a name and the application needs a better name anyway. For now I just refer to it as FM.

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.

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.

Los Alamos Message Passing Interface is an implementation of the Message Passing Interface (MPI) motivated by a growing need for fault tolerance at the software level in large high-performance computing (HPC) systems.
This need is caused by the vast number of components present in modern HPC systems, particularly clusters. The individual components -- processors, memory modules, network interface cards (NICs), etc. -- are typically manufactured to tolerances adequate for small or desktop systems.
When aggregated into a large HPC system, however, system-wide error rates may be too great to successfully complete a long application run. For example, a network device may have an error rate which is perfectly acceptable for a desktop system, but not in a cluster of thousands of nodes, which must run error free for many hours or even days to complete a scientific calculation.
LA-MPI has two primary goals: network fault tolerance and high performance.
Network fault tolerance is acheived by implementing a highly efficient checksum/retransmission protocol. The integrity of delivered data is (optionally) verified at the user-level using a checksum or CRC. Data that is corrupt (or never delivered) is retransmitted.
As for high performance, LA-MPIs lightweight checksum/retransmission protocol allows us to achieve low latency messaging. Furthermore, the flexible approach taken to the use of redundant data paths in a network-device-rich system leads to high network bandwidth since different messages and/or message-fragments can be sent in parallel along different paths. Also, since LA-MPI is developed for use on the the large systems at Los Alamos National Laboratory we have verified that LA-MPI is scalable to over 3,500 processes.
An alternative solution to the network fault tolerance problem is to use the TCP/IP protocol. We believe, however, that this protocol -- developed to handle unreliable, inhomogeneous and oversubscribed networks -- performs poorly and is overly complex for HPC system messaging, and that LA-MPIs lightweight checksum/retransmission protocol is a more appropriate choice.
Main features:
- Standard compliant (MPI version 1.2 integrated with ROMIO for MPI-IO)
- Highly portable
- Open source (LGPL)
- Thread safe
- Optimized for SMP systems, including NUMA architectures
- Network fault tolerant (data integrity checked at user level)
- Message-fragment striping across multiple network devices
Enhancements:
- Namespace conflicts have been fixed.
- Error detection and handling of fragments has been improved.
- Bugs in memory barriers and spinlocks for x86 and x86_64 architectures have been fixed.
- Profiling and backtracing support have been added.
- Asynchronous I/O has been disabled by default as a workaround for problems with some filesystems.
- Minor timeout bugs have been fixed.