> >
> > With this info, over time one would be able to finetune and optimize the
> > number of lists used and lookup order, dropping lists rarely scoring/used etc.
> 
> once you know the IP and you know that it has been rejected, getting the
> list is trivial.
> 

Well, me from an adminstrators view that logic isn't very efficient. I monitor logs
concistiently to adapt applications for best performance or adjust malconfigurations.

In the XMail case I have some 50% of all connections rejected by maps, and knowing that
XMail for each connection does a DNS query for each map until a match says me that
this will come down on performance more or less. Especially if the the map responsible 
for
most blocks is put last in a line of five, and maybe the three first ones don't catch 
anything.
Besides that grepping and looking up all rejected IPs from the smtp-log in these five 
map-databases
manually (or even automated) and from the result build some sort of statistics is 
something
I wouldn't even assign to my worst enemy.

My suggestion adding the actual map responsible for a block, would easen up a decision
of what maps to use and in what order to break optimum simple by quickly browsing thru
1-2 days of logs. If I find map E (the 5th and last map) was responsible for 99% of 
the blocks
and the three first ones (A, B, C) does 0%, the I know my CustMapsList is very poorly 
setup. Now I
simply had to drop maps A,B and C and set the 99% scorer, E frontmost to gain an 
optimized
CustMapsList directive for the time being.

Of course, I could have come to this decision by following your suggestion aswell, but 
it would require
X hours of extra work, those extra hours which one rarely have lying around. From my 
point
of view, I figure this would add up some 1 line additional code on your behalf, while 
it would save us
XMail users (atleast me ;) ) a bundle + slightly better map-based performance 
eventually.


my 2 cents.
/thomas.
 


-
To unsubscribe from this list: send the line "unsubscribe xmail" in
the body of a message to [EMAIL PROTECTED]
For general help: send the line "help" in the body of a message to
[EMAIL PROTECTED]

Reply via email to