At 8:18 AM -0800 11/1/01, Fokko van Duin wrote: >Ok, so I also tried dnsreport, but it keeps saying "Could not connect to your >mailserver", ns.lanbox.com: timed out!
I went all through this with the dnsreports.com guy yesterday. Basically, his time-outs are set pretty short -- not up to RFC standards. He's concerned that users of the web page will grow impatient if they have to wait too long for the report results. As I told him... At 3:58 PM -0700 10/31/01, Warren Michelsen wrote: >To keep from causing undue concern, why not just start the results page with the >notation: "I am now conducting umpteen different tests on [domain]. This may take >several minutes to get all results back." Or something similar. > >I mean, had you used longer time-outs, I'd not have spent an hour of my time trying >to figure out why you could not contact my mail servers. I'd, personally, rather have >a test that was complete and accurate than fast. > >Not to mention that I've taken more of YOUR time than necessary and added load to >your server by running the test on my domain half a dozen times. > >All in all, you may think that shorter-than-RFC timeouts are doing us a favor but, in >reality, I don't think so. So, the problem is likely not on your end. > >Is something wrong with SIMS, dnsreport, or is it just me;-) dnsreport.com -- Internet Tools for Business -- <http://www.CyberSpaces.net/> E-commerce web hosting ############################################################# This message is sent to you because you are subscribed to the mailing list <[EMAIL PROTECTED]>. To unsubscribe, E-mail to: <[EMAIL PROTECTED]> To switch to the DIGEST mode, E-mail to <[EMAIL PROTECTED]> To switch to the INDEX mode, E-mail to <[EMAIL PROTECTED]> Send administrative queries to <[EMAIL PROTECTED]>
