-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On August 31, 2004 6:23 am, Mike Roest wrote: > This one is the sticky wicket, it took 50 minutes to get from the line > below till it was delivered to cpweb1.idig.net but that could be caused > by anything. Network problem between shaw and idig, the idig mail server > being congested and not handling the shaw SMTP threads etc. With just > the headers there is no way to say that it wasn't a network problem or > something external to the shaw mail server. The only way to know for > sure would be to examine the logs on both sides, and from that track > down exactly the culprit. With only the headers the only thing you can > say with certainty is it took 50 min for the final delivery hop. There > is no way to lay blame on shaw's door step. > If this were the only Shaw email that I ever saw exhibit this behaviour, I'd agree there's not enough info to truly blame Shaw. But as I run the email server here at my work and have access to the log files, and on numerous occassions had people on Shaw icq me to say "Just sent you an email" and then not see it even knock at my proverbial door until two hours later (and no, it's not a busy server), I most definitely blame Shaw for that. I'd know if it gets lost in my network for hours on end. And like I said, I'm not the only one seeing this problem. Many people I know are complaining about it, and the only common denominator is Shaw. Look at the replies to Graham's email. Who voiced a similar (serious) complaint? Cameron (Shaw email address) and Katrina (also Shaw). It's Shaw that's broken, I'd bet you a beer. :-)
Ian -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.3 (GNU/Linux) iD8DBQFBNJAJSiY+RXI7JS4RAnDKAJ4jHJ/ay+0DvRkkYfcCV+UahcFAWgCdFASG cQofbkgB3O3NmZHcAe3FR4o= =YKW5 -----END PGP SIGNATURE----- _______________________________________________ clug-talk mailing list [EMAIL PROTECTED] http://clug.ca/mailman/listinfo/clug-talk_clug.ca
