Free message queue server software for linux

Messa is an instant messager client and server. The client has a curses interface and works on the console.

Messa project supports multilingual messages and private messages. The server supports monoprocess operation (without threads), the ability to choose the listening port, and the ability to run under the console.

Putmail Queue provides a queuing system for putmail.py from the Putmail project.

It allows you to compose your email messages offline, keep them in a queue, and send them all together later.

This is my first try at providing a queuing system for putmail.py. Inside, youll find two programs: putmail_enqueue.py and putmail_dequeue.py.

To use them, you must first create the directory $HOME/.putmail/queue/. Its recommended that only you have access to it.

Install the program by running install.sh as root if necessary. Optionally, edit the file first to specify destination directories.

Usage instructions are in the man page. Use "man putmail-queue" to read it. It is a recommended one-time read.

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.

Dwarf Mail Server is a full-featured mail server developed on the Java platform, implementing SMTP, POP3 and IMAP4rev1 protocols.
Dwarf Mail Server provides support for rich application message processing via pluggable mail filters and agents, as well as full handling of virtual domains for the SMTP/POP3/IMAP4 protocols, and is free of charge for the binary redistribution.
Since the server is based on the Dwarf framework, it also shares its common design principles and features - simplicity, high modularity and extensibility, authentication and authorization, XML-based configuration, logging and remote management.
Main features:
- ESMTP, POP3 and IMAP4rev1 implementation
- application logic layer provided by mail filters and agents
- virtual mail hosts in SMTP/POP3/IMAP4 server
- application-independent authentication and authorization
- sample JSP-based webmail interface
Dwarf Mail Server is targeted for both end users who are just looking for simple, secure and robust mail server as well as developers who need an extensible and powerful framework for application message processing.
For users with minimal requirements it can offer portability, simple configuration as well as strong security.
- Portability: several OS platforms are supported via the Java technology, including MS Windows, UNIX/Linux/BSD, MacOS X and others.
- Configuration: just 3 lines have to be changed to fire up a sample mail server and a few of them to run a full featured SMTP/POP3/IMAP4 server.
- Security: it uses Java Platform Security Architecture in combination with Java Authentication and Authorization Service (JAAS), as well as SSL/TLS for the secure communication.
Advanced or enterprise users can additionally appreciate performance scalability, multiple domain handling, enhanced security features and modular design easing to incorporate it to the existing infrastructure.
- Scalability: gaining from multithreaded design and dynamically adjustable allocation of resources.
- Multiple domains: server is able to handle multiple virtual domains in a single instance for all SMTP, POP and IMAP protocols.
- Enhanced security: includes subject-based permissions and access control lists for IMAP, SMTP relaying control rules, host-based filtering, SSL/TLS communication, basic anti-spam filtering, etc.
- Robustness: client/server network communication is by design separated from the resource-expensive application logic layer. The server implementation is based on the unparsed byte streams whenever possible, including its own and highly efficient MIME parser.
Dwarf Mail Server also appears to be a suitable platform for application development and customization. Its modular structure and lightweight API allows enhancing existing functionality or completely exchanging the certain part as a whole:
- Message processing: mail filters and agents provide an unique infrastructure for rich message processing.
- Mail queue: physical mail queue representation is abstracted by the API specification and may replaced by a custom implementation.
- Storage subsystem: physical data representation (i.e. messages, folders, configuration options, ACLs) is abstracted by API and may be replaced by a custom implementation based on filesystem, SQL database, etc.
- MIME parser: the parsing engine may be reimplemented for the top efficiency according to the currently used mail storage.
Dwarf Mail Sever has been tested with the most popular mail clients like MS Outlook, Mozilla, Thunderbird, Opera, Apple Mail, Becky!, Pegasus, Eudora, Pine, The Bat! and others.
Other features:
- multi-threaded server
- dynamically adjusted number of active threads
- server API for mail, user data and ACL storages
- robust SMTP server architecture with flexible queue design
- simultaneous deliveries to remote SMTP hosts
- transparent Delivery System Notification (DSN) mechanism
- support for shared mail folders
- fast and universal stream-oriented MIME parser
- runtime server configuration
- built-in SSL/TLS support
- full documentation with user guides and tutorials
- samples with source code

BitTorrent Queue Manager is a console-based BitTorrent client running on top of BitTornado that provides built-in queue management functions.
BitTorrent Queue Manager also provides a remote interface compatible with ABC for Web-based control. Furthermore, peer information can be queried, including country and network names, and a built-in crawler can gather new torrents on specified trackers or catalog sites for downloading automatically.
This is the new beginning of BTQueue. By upgrading to 0.1.0, you are able to:
- Utilize DHT network compatible to Bram Cohens client and BitComet
- Query IP location from updated database plus AS number (see ip2cc)
- Change client identifier to Azureus, Bram Cohens client, or BitComet

POE::XS::Queue::Array is an XS implementation of POE::Queue::Array.

This class is an implementation of the abstract POE::Queue interface. It implements a priority queue using C, with an XS interface supplied.

The current implementation could use some optimization, especially for large queues.

Please see the POE::Queue documentation, which explains this ones functions, features, and behavior.

The following extra methods are added beyond POE::Queue::Array:

dump

Dumps the internal structure of the queue to stderr.

verify

Does limited verification of the structure of the queue. If the verification fails then a message is sent to stderr and the queue is dumped as with the dump() method, and your program will exit.

NNML::Server is a minimal NNTP server.

SYNOPSIS

perl -MNNML::Server -e server
perl -MNNML::Server -e unspool

NNML::Server server implements a minimal NNTP server. It is (hope-) fully conformant to rfc977. In addition the commands XOVER and AUTHINFO are implemented.

Supported commands:

ARTICLE, AUTHINFO, BODY, GROUP, HEAD, HELP, IHAVE, LAST, LIST,
MODE, NEWGROUPS, NEWNEWS, NEXT, POST, QUIT, SLAVE, STAT

XOVER, XHDR, LIST NEWSGROUPS ng-spec

The main reason for writing this was to synchronize my mail directories across different hosts. The Mail directories are MH-Style with a .overview file in each folder and an active file in the base directory. These are maintained by the Emacs Gnus backend NNML. To get started, you can generate/update this files using the overview program. Upon POST and IHAVE commands this files will also be updated.

To start from scratch use:

touch /tmp/active;
perl -MNNML::Server -e server(base => "/tmp", port => 3000)

To export your mh-Mail use:

perl overview -base ~/Mail
perl -MNNML::Server -e server(base => "$ENV{HOME}/Mail", port => 3000)

The command POST and IHAVE honour the Newsgroups header if not overwritten by the X-Nnml-Groups header. Articles will contain an appropriate X-Nnml-Groups header when retrieved by message-id.

When the client submits the SLAVE command, all forther post requests are spooled in $Config-spool> (usually ~/Mail/NNML.spool) for performance reasons. You can process the spooled articles by submitting the XUNSPOOL command or by calling

perl -MNNML::Server -e unspool

Rejected articles will be saven in $Config-bad> (usually ~/Mail/NNML.bad)