>>>> The problem starts when you receive 10 email seconds to >>>> [EMAIL PROTECTED] always using always a new ip . >>>> It overloads Validate Recipient Addresses , believe me.
>>> I can't see why looking up an IP address in a list would be any quicker >>> than looking up a From: address - so the load of performing the lookup >>> isn't an issue. >>> >>> The only real difference is that the incoming mail has to be read up to >>> the rcpt to: line - but if the IP address is constantly changing the >>> email is going to have to be read up to the point of determining it's >>> SPAM anyway. So Validating the Recipient is the appropriate (and really >>> only) defence against this. >> Hmmm... does Validate Recipient happen *before* the IP is read? > No - connections are refused from IP addresses without any conversation > at all. Ummm - I knew that. Thats what I get for asking questions when I'm still asleep... ;) But in this case we cannot blacklist the IP address anyway - > it's constantly changing. The only defence against it is content > analysis and recipient validation is one of the least costly. It might > be worth investigating if it is performed before other more costly > checks such as RBL etc.. and move it nearer the front if it isn't. I > favour rejecting as much as possible with as little overhead as possible > first before doing costly checks. But of course. I recall Fritz or someone posted a listed order of the checks - I wonder where that is now... ahh, found it... http://www.asspsmtp.org/wiki/Processing_Order -- Best regards, Charles ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ Assp-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/assp-user
