Xqm Diagnosis Extention, How to customize ...

Hi, Harald !

I couldn´t live without XQM: it´s my primary tools each day to control my Xmail 1.21´s servers.
I use the filtering feature, and usually a message is freezed by them.
But the 'Diagnosis' column from XQM say "User unknown" as the cause of rejection by Xmail. I know the rejection is due to filters, of course, but it would be very handy to get a message like "Rejected by server filters" or something else.

Can I configure something to do that?

Thanks.


Sergio Perrone

You can and it's simple ;-)

Just open "Xmail Queue Manager\parse.lib" with your favourite ASCII editor and read the instructions there:

Excellent !!!

Thanks a lot, Harald.

Sergio

You can also customize its diagnosis text. If your custom tag is e.g. FILTERED, then place an ASCII file named FILTERED.txt in the "XMail Queue Manager\kbase" folder.

If you have any improvements for existing rules or some new rules which are of public interest, please let me know.

OK:

I´m doing some definitions to explain Filter Rejects, and AV filter rejects.
Where can I find information about SLOG entries and logic?

Sergio

Examine existing SLOG files of frozen messages.
All which XQM does, is to read these entries into variables, which can be checked against the patterns from its parse.lib.

If a pattern matches, the message is classifed (tagged).

There is a chapter ("Inspector") in XQM's helpfile, which explains like SLOG entries are built up and how to interprete them.

Harald:

After many days working with 'parse.lib' and 'parse.usr.lib', I have my XQM diagnosing correctly the messages frozen due to content filters and AV filters.
BUT (always there´s a 'but'), I had to modify the 'parse.lib' file.

I know, I know: the user shouldn´t modify that file.

The problem is the definition of the 'ANTISPAM' rule. It includes strings like 'reject' and 'message' BEFORE 'parse.usr.lib' reach them. Then, XQM applies the 'ANTISPAM' rule instead of the new ones.

Solution?

I think there´s two possible:
1. The 'parse.usr.lib' should be the first aplied (before 'parse.lib´)
2. Modify 'parse.lib' (You should): but this will be a temporal solution, since with another change in Xmail, the file will need another update.

Sergio

The file has to be named parse_usr.lib, not parse.usr.lib. The mechanism still gives priority to the userlib. Can you test again, please ?

I'll add a hint if parse_user.lib is loaded or not in XQM's info dialog. Will be useful in such situation.

Ok:
I´ll try.
Sorry for my mistake. I´ll let you know when finish (soon) and I´ll send you the new definitions.

Sergio

Harald:

Now I have another problem.
As a filter (eg: xscanner) or avfilter stops a message, Xmail frozes it (if you setup this) but does not write any cue in SLOG file.
I can´t find a way to scan something to evaluate a expression and make XQM diagnose this kind of events.
I know Xmail does a filter.log writing but I can´t scan it from XQM.

Another question:
Actually, XQM shows the diagnosis for my frozen messages as "DNS": this is the default behaviour? Why XQM chooses DNS without any information in SLOG files?

Thank you


Sergio

To examine the messagefile itself, you have:
# Spoolfile.slog = The complete SLOG file
# Spoolfile.lastslog = The latest SLOG entry
# Spoolfile.content = The complete spoolfile
# Spoolfile.envelope = Its envelope only
# Spoolfile.header = Its header only
# Spoolfile.body = Its message content only

If your filter writes an X-Header, then it should be no problem to identify.

Messages without slog should be tagged as unknown.
Could you send me your zipped spool folder, please ?