Re: Personal IP blacklists

[Richard O. Hammer]

My dream SMTP server has a GUI reminiscent of the control room at a 
power plant, with gauges which show every parameter which might be 
important to the operator, and with valves to throttle or completely 
shut down any segment of the operation which seems to be getting out 
of hand.

Parameters such as the following would have both gauges (and/or 
warning lights and whistles) and values (operator-settable limits):

total incoming messages/(unit time)
total incoming connections/(unit time)
total incoming bytes/(unit time)
total outgoing ... (the same three as above)
total volume of mail held in local mailboxes
total volume of mail held in local spools
ip addresses generating most of the traffic/(recent unit of time)
ip addresses generating most of the connections/(recent unit of time)
local addresses receiving large quantities of mail
local addresses sending large quantities of mail
Also, another approach, I would prefer to have the server return an 
error upon RCPT TO: <unknownJoe>, rather than accept the message as 
James does at present.  I think Noel said there were plans to change 
this in an upcoming James.

Rich

Serge Knystautas wrote:
This weekend spammers felt the need to send my James installation over 
50,000 emails that they knew wouldn't get relayed.  I'm thinking of 
creating a db-based personal blacklist and was wondering if anybody has 
thought of something similar.

I already am using the db for the message stores, so it's convenient 
(for me) to have this as another table.  Right now I have to edit 
config.xml and restart James, which is therapeutic right now, but I'm 
sure will get old.

Anyone try to do something similar?



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]