>SPF has a mode whereby a lookup could return data that requires *another*
>DNS lookup, e.g. the "include:foo.com" directive.
>Currently we have to use Mail::SPF::Query as a single method call, and
>allow it to run all necessary queries by itself and simply wait for it to
>return. A more efficient way would be to have a polling mode, so we can
>process our own code while waiting for results, and poll for results
>intermittently -- similar to how we do DNSBL and URIBL lookups.
This is exactly the stuff I rewrote inside the check function. Its the exact opposite of whats needed to be done if you can use any of these results to 'block' without needing any other scores.
I run all the rbl lookups and then wait for the results to come back. If we get a block/hit we return without running anymore rules. This gave us a large performance boost in a server environment since we can eliminate rules that are essentially ignored early on. There are better things to do with the cpu.
dale luck
Title: RE: Renaming DnsResolver::search to send
- Re: Renaming DnsResolver::search to send Justin Mason
- Re: Renaming DnsResolver::search to send Sidney Markowitz
- Re: Renaming DnsResolver::search to send Justin Mason
- Polling vs. a factory (was: Renaming DnsReso... Malte S. Stretz
- RE: Renaming DnsResolver::search to send Dale Luck
- Re: Renaming DnsResolver::search to send Justin Mason
- Re: Renaming DnsResolver::search to send Theo Van Dinter
- RE: Renaming DnsResolver::search to send Dale Luck
