On Sat, Feb 21, 2004 at 07:16:30AM -0500, Hector Santos wrote:
|
| SPF itself has added atleast 1 to 3 seconds to the session time. But the
| high delays are way too high with DMP to further ignore.
|
Hector, I really believe there is a serious problem in your DNS stack.
20040221 00:58:32 000130b1 -------------------------------------
20040221 00:58:32 000130b1 version : 1.55 / 1.54
20040221 00:58:32 000130b1 calltype : SMTP
20040221 00:58:32 000130b1 state : rcpt
20040221 00:58:32 000130b1 cip : 68.122.222.252
20040221 00:58:32 000130b1 cdn : oricom.ca
20040221 00:58:32 000130b1 from : <nroe_yo(_at_)carleton(_dot_)ca>
20040221 00:58:32 000130b1 srvdom : mail.winserver.com
20040221 00:58:32 000130b1 srvip : 208.247.131.9
20040221 00:58:32 000130b1 sapfilter : pass (time:15)
20040221 00:58:38 000130b1 sapspf : v=spf1 ip4:134.117.0.0/16
20040221 00:58:38 000130b1 sapspf : neutral (time:6469)
20040221 00:58:38 000130b1 sapdmp : testing
252.222.122.68.in-addr._smtp-client.carleton.ca
20040221 00:58:40 000130b1 sapdmp : testing
252.222.122.68.in-addr._smtp-client.oricom.ca
20040221 00:58:46 000130b1 sapdmp : none (time:7703)
20040221 00:58:46 000130b1 saprbl : testing 252.222.122.68.sbl.spamhaus.org
20040221 00:58:47 000130b1 saprbl : testing 252.222.122.68.list.dsbl.org
20040221 00:58:49 000130b1 saprbl : blocked at list.dsbl.org (127.0.0.2)
20040221 00:58:49 000130b1 result : reject (0)
20040221 00:58:49 000130b1 smtp code : 554
20040221 00:58:49 000130b1 reason : Rejected by WCSAP RBL Host
list.dsbl.org
20040221 00:58:49 000130b1 wcsap finish (17187 msecs)
If I read this correctly,
- the SPF lookup takes 6.5 seconds to return
- the DMP lookup takes 7.7 seconds
- the dsbl lookup takes 2 seconds
On my system, even with the overhead of loading Perl, then doing the
lookup, then parsing the result, SPF takes 0.056 wall-clock seconds.
20040221-10:49:32 mengwong(_at_)dumbo:~% time perl -MMail::SPF::Query -le
'my $query = Mail::SPF::Query->new(ipv4=>shift, helo=>shift, sender=>shift);
print "result: $_" for $query->result; print $query->{directive_set}'
208.210.125.24 mengwong(_at_)carleton(_dot_)ca
result: neutral
result: Please see
http://spf.pobox.com/why.html?sender=carleton.ca&ip=208.210.125.24&receiver=dumbo.pobox.com
result: dumbo.pobox.com: 208.210.125.24 is neither permitted nor denied by
domain of carleton.ca
result: v=spf1 ip4:134.117.0.0/16
DirectiveSet=HASH(0x83205b4)
perl -MMail::SPF::Query -le 208.210.125.24 mengwong(_at_)carleton(_dot_)ca
0.09s user 0.03s system 213% cpu 0.056 total
20040221-10:49:42 mengwong(_at_)dumbo:~%
Granted, I had done a couple of straight txt digs against carleton.ca,
so the result is cached; but in a recent round of analysis, we performed
SPF analysis against 18,000 unique domains starting with an empty
resolver cache. The average time to complete a lookup was 0.47 seconds.
On the second run, when the domain was already in the cache, the average
time went down to under 0.2 seconds.