On 7/23/2010 1:20 AM, GrayHat wrote: > My idea is the following; we already have "three" caches > which build-up while ASSP is running, that is "MX", "A" > and "SenderBase"; now, when an IP connects to our > box, ASSP may perform a cache ONLY lookup to see > if the IP is a valid mailserver (MX/A) or belongs to an > organization we trust (SenderBase) and, in such a case > the delaying will be skipped (same goes in case the > sender passes the SPF check) > > I think that, while the above won't impact on processing > time (the lookup is only performed on local caches > so it's almost immediate) it will help avoiding issues > due to hosts which "don't like" the delaying mechanism > >
If I understood you correctly,. you're saying either a valid SenderBase query OR a valid MX - ANY valid MX - will bypass the greylist? So greylist would only function for dynamic IP's and badly configured sites? Which means any spammer with a properly configured MX will bypass greylisting. -- Daniel ------------------------------------------------------------------------------ This SF.net email is sponsored by Sprint What will you do first with EVO, the first 4G phone? Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first _______________________________________________ Assp-test mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/assp-test
