Xqm 1.27 And Agent 1.13 Released, New: Analyzing on the fly!

[hschneider]

You can download the latest release of XQM and XQM Agent at
http://xmail.marketmix.com

What's new:
1. Message analyzing on the fly
An additional column in the grid view now contains a diagnosis tag for each message.
E.g. QUOTA if the message bounced because the user's mailbox was full,
RELAY_DENIED if you were not allowed to relay etc. 98% of the queue content can
be recognized by this method.

This allows you to quickly view a bulk of frozen messages without digging through
the SLOGs by hand. You can also sort and delete by that new attribute.

2. XQM remembers its column widths now.

3. Scalable number of threads
The number of threads collecting the queue content in parallel can be scaled
from 1 to 25 for best possible performance also on slow machines.

4. Debug info
The Agent can be run in a debug mode on Win32 where it dumps a log to the console.
Just start it with paramter -debug from a command prompt.
On Linux it gives some useful informations during startup.

[hschneider]

There is an updated Agent 1.14 for WinNT available. It fixes a connection problem appearing in some environments. The Linux platform release was not affected.

[chabral]

Harald,
I've tried using the admin protocol by hand to view queued messages and delete them, and it's very fast in my "slow" server (do you remember?) What do you think about doing some things interacting with the admin protocol and others by yourself? I mean, for example, getting the list of queued messages using the protocol and getting more info by hand (I mean the way you're doing it now). This way may improve performance in slow server. Getting the list this way it took about 8 seconds in my server, instead of 15 minutes using the Agent.
Regards,

chabral

[hschneider]

There are 2 problems:
- The ctrl protocol only returns the frozen messages. That means no resending and no sending ones.
- Things have to be encoded to XML and transferred via XML-RPC. I think here is also a bottleneck between your slow machine and the Python implementation.

I have some ideas about gaining speed on low resource machines - just need the time to implement'em. E.g.:
- A faster XMLRPC lib, written in C or C++
- A caching daemon written in C, which prepares the nested structure for the slower Python routines.

I'll let you know, when things are ready to test.

[chabral]

I just don't know if I expressed myself correctly. I meant that the Agent delegates some work to the administration protocol, not the GUI.
Regards,

chabral

[hschneider]

The GUI only displays the data collected by the agent.

Surely the agent can get the list of frozen messages faster from the ctrl protcol. But in order to find the sending and resending messages, the agent has to search the whole spool which costs the same amount of time.

Remote access by the ctrl protocol is faster, but also fails by the limited capabilities of the protocol ...