On Friday 27 October 2006 00:24, Basil Chupin wrote:
John Andersen wrote:
On Thursday 26 October 2006 19:48, Ed McCanless wrote:
Hi All, If I read this right, Basil is in Australia and John is in Alaska. I am in North Carolina, US. I've been having the same problems. Maybe the spread of locations will help somebody find what's happening.
The list server still appears to be in Germany, so perhaps its some transatlantic routing issue.
Basil, when you traceroute to the list server to you go via a USA routing?
Sorry John, I'm a bit rusty on the "traceroute" business. I used to see much more info in the Header than I can see now so do you mean something else other than what's in the Header, such as this from your msg to which I am replying?-
BEGIN
Yeah, this has nothing to do with headers. Its a question about routing of tcp packets rather than mta-to-mta routing. I was operating on the assumption that since several US buys reported slow mail, that perhaps your mail came via US circuits. It only takes one Joe Sixpack on a back hoe on the outskirts of Butcrack Arkansas to rip up a major fiber link. If your packets came via the US that would explain why you and I and the guy on the US east coast were affected but the guys in Gernany were not. As root, in a shell, type traceroute lists.suse.de From the output of each hop, you can kind of map out the route the packets took by the router names involved. Mine go from Alaska to Seattle, to Chicago (via sprintlink) then over to versatel in Germany. -- _____________________________________ John Andersen