The POP and IMAP troubleshooter serves to diagnose and solve connection problems from client machines to email services. It reads the client configuration files (Outlook, Windows Mail, Thunderbird, etc.), checks the individual settings, and then attempts to create POP, IMAP, and SMTP connections using these settings. The troubleshooter is coded in C++ using the Qt environment. It can be used generically, or can be customized for the demands of a particular email service.
The drkhtb project was designed with medium to major Internet Service Providers in mind. Featuring extended hashing support, error handling, and simple configuration options, it has proven to be a stable solution for shaping up to 15000 residential clients with both upload and download rules, it is considered stable and is already in use as a production platform in at least one major ISP running 4 shaping bridges, each handling up to 2 Gbit/s, with a total of 48000 active clients and over 60000 filter rules in each direction. At this point there is no reason to believe that further bandwidth cannot be handled by one bridge, but there have not been sufficient resources to extensively test it. It is believed that up to 4 Gbit/s can be shaped on one individual machine serving at least 20000 clients.
PICI-NMS is an object oriented middleware which makes possible sending messages in a networked environment or on a single host between applications using the library provided. The supported message sending mechanism is "publish/subscribe" and this is backed up by a very easy-to-use and intuitive C++ API which hides the underlying socket interface to make the message sending as transparent to the client as possible.
The SMS Server Tools 3 is a SMS gateway that can send and receive short messages through GSM modems and mobile phones. Messages are sent by simply storing text files into a special spool directory. It also stores received messages into another directory as text files. Binary messages including Unicode text and ring tones are also supported, and it is possible to send WAP Push and system messages. The program can run scripts after events like the reception of a message, successful sending, and when the program detects a problem.
When a user inputs a hostname or an IP address, MQ Port Scan will scan a range of ports looking for a queue manager's MCA, using the standard (system default) channel names, in order to make a successful connection. It is very easy to use. It has the ability to search across a range of IP addresses and scan the port range for each IP address. Any time MQ Port Scan successfully connects to a queue manager, the information is written to a CSV file. The output will include the queue manager name, MQ version, channel name, hostname or an IP address, and port number.
The Message Multiplexer (MMX) application will get a message from a WebSphere MQ queue and output it to one or more queues. Context information is maintained across the message put(s). MMX can move messages from a single source queue to (up to) 99 target queues. Messages put to each target queue are an exact replicate of the original message from the source queue (including the message's MQMD). MMX performs each MQGET and the subsequent "n" MQPUT(s) under a Unit of Work (UOW), so that message integrity is kept.
The Message Router (MRTR) application will move a message from a central WebSphere MQ queue to a specific application WebSphere MQ queue. The destination queue that the message will be placed into will be based on a keyword in the message. Context information is maintained. MRTR will look in the message for a Start Keyword and an End Keyword. The value between these two keywords is the Keyword Value (inifile Token). MRTR will search its ini file for that particular Keyword Value. The field value associated with the looked-up keyword value is the destination queue name. MRTR performs each MQGET and the subsequent MQPUT under a Unit of Work (UOW) so that message integrity is kept.