> What would cause an SPF lookup to timeout? For example: > Apr-10-12 17:53:25 id-33409-03026 178.20.64.93 <nore...@microsoft.com> > to: some...@mydomain.com SPF: timed out after 21 secs.; > > The above sender is not actually from valid Microsoft.com servers.
Hm... probably slow resolvers, by the way, it could be useful to also see the HELO string used by that host; anyhow... ;; QUESTION SECTION: ;93.64.20.178.in-addr.arpa. IN PTR ;; ANSWER SECTION: 93.64.20.178.in-addr.arpa. 172800 IN PTR aten-09.cloud.mit.ovea.com. the above is the PTR related to that IP and, as for Microsoft SPF... "v=spf1 include:_spf-a.microsoft.com include:_spf-b.microsoft.com include:_spf-c.microsoft.com include:_spf-ssg-a.microsoft.com ip4:131.107.115.215 ip4:131.107.115.214 ip4:205.248.106.64 ip4:205.248.106.30 ip4:205.248.106.32 ~all" so, maybe one of those includes causes the SPF checker to slowdown a bit (just guessing) but even in this case, the issue is due to the DNS resolver(s) you're using ------------------------------------------------------------------------------ Better than sec? Nothing is better than sec when it comes to monitoring Big Data applications. Try Boundary one-second resolution app monitoring today. Free. http://p.sf.net/sfu/Boundary-dev2dev _______________________________________________ Assp-test mailing list Assp-test@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/assp-test
