On 10/25/06, Daniel Bauer wrote:

<trimmed> b.t.w.: untill today I only received 2 "warnings", but I miss several mails from time to time, so the problems could be on both sides... I'm curious to know what others experience

I am getting all the mails without any problem. I guess you need to talk to your ISP. --

Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com

-- http://mckagan.googlepages.com

On Thursday 26 October 2006 02:09, Carlos E. R. wrote:

The Wednesday 2006-10-25 at 20:51 -0800, John Andersen wrote:

...

I had this problem over the weekend. It got suddenly fixed on monday and I have no clue what it was. I too found tons in the archives that did not arrive in my mailbox, and I can't blame my ISP since I run my own sendmail.

Are there rejections in your logs?

Nope, no rejections, and other mailing lists were comeing in fine. Since more than one person reported a slow-down over the week end, I'm assuming it was not JUST me.... -- _____________________________________ John Andersen

* Carlos E. R. [10-27-06 06:20]:

I have seen few posts these days, but then, comparing to the list archive I haven't found lost emails. But then, I'm in Europe, and you chaps seem to be thinking it is a problem in the USA or in transit.

But it that case the list server would be seeing rejects, and it will send a probe and/or a complaint or bounce report to you sometime, maybe in days.

I still see high traffic and no *late* mails. Located west-southwest of Indianapolis, Indiana, on roadrunner cable. List mail traffic is routed: Indianapolis, Indiana --> Columbus, Ohio --> Chicago, Illinois --> Frankfurt, Germany -- Munich Germany again, I see no dropped/late posts, usual traffic. -- Patrick Shanahan Registered Linux User #207535 http://wahoo.no-ip.org @ http://counter.li.org HOG # US1244711 Photo Album: http://wahoo.no-ip.org/gallery2

Basil Chupin wrote:

John Andersen wrote:

...

On Wednesday 25 October 2006 07:26, Basil Chupin wrote:

...

Those who are not having trouble getting mail from this list, would you please check if there is some sort of a problem with SUSE's server? Thanks.

I had this problem over the weekend. It got suddenly fixed on monday and I have no clue what it was. I too found tons in the archives that did not arrive in my mailbox, and I can't blame my ISP since I run my own sendmail.

Interesting. I know that you are in Alaska, I'm in Australia. You had this problem over the weekend and I am having this problem day ago and again yesterday.

Are blocks of IP addresses being closely interrogated for the contents of mail? Anything is possible in this now crazy world.

Cheers.

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. I saw this thread about 8 hrs. ago on the archives, but this is the first portion of it that has actually reached me at 11:15 P.M., here. I seem to be getting list mail in cycles, nearly normal on Mondays, diminishing on Tue., minimal on Wed. then picking up again toward the weekend or the next Mon. It has been this way since about the 25th of Sept. I've been told someone is working on the problem, but each time it starts to look better, it doesn't last. I know I haven't got all of today's mail, I'm still waiting for the Skype thread to come through (that may have been for the 25th, if so I'll never see it). -- ED --

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? -- _____________________________________ John Andersen

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 From - Fri Oct 27 15:55:15 2006 X-Account-Key: account2 X-UIDL: f6af85877e0a0000 X-Mozilla-Status: 0011 X-Mozilla-Status2: 00000000 X-Mozilla-Keys: X-From_: suse-linux-e-return-285935-blchupin=tpg.com.au@suse.com Fri Oct 27 15:53:14 2006 X-TPG-Antivirus: Passed Received: from lists.suse.com (lists.suse.de [195.135.221.131]) by mail9.tpgi.com.au (envelope-from suse-linux-e-return-285935-blchupin=tpg.com.au@suse.com) (8.13.6/8.13.6) with SMTP id k9R5r79R010310 for ; Fri, 27 Oct 2006 15:53:13 +1000 Received: (qmail 13749 invoked by alias); 27 Oct 2006 05:53:00 -0000 Mailing-List: contact suse-linux-e-help@suse.com; run by ezmlm Precedence: bulk list-help: mailto:suse-linux-e-help@suse.com list-unsubscribe: mailto:suse-linux-e-unsubscribe-blchupin=tpg.com.au@suse.com list-post: mailto:suse-linux-e@suse.com X-MIME-Notice: attachments may have been removed from this message X-Mailinglist: suse-linux-e X-Message-Number-for-archive: 285935 Delivered-To: mailing list suse-linux-e@suse.com Received: (qmail 13736 invoked from network); 27 Oct 2006 05:52:59 -0000 From: John Andersen To: suse-linux-e@suse.com Date: Thu, 26 Oct 2006 21:52:55 -0800 User-Agent: KMail/1.9.5 References: <453F823F.8000707@tpg.com.au> <454179E0.3010103@tpg.com.au> <45418171.3080809@bellsouth.net> In-Reply-To: <45418171.3080809@bellsouth.net> X-message-flag: Friends don't let friends use OutLook. MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Message-Id: <200610262152.56018.jsa@pen.homeip.net> X-Virus-Scanned: by amavisd-new at Relay1.suse.de X-Spam-Status: No, hits=2.2 tagged_above=-20.0 required=5.0 tests=BAYES_50, FORGED_RCVD_HELO, RCVD_IN_SORBS_DUL X-Spam-Level: ** Subject: Re: [SLE] Something wrong with the mail END Nothing I can see above shows what used to be shown as to which servers the message went through before getting here. Or is this only because I am using Thunderbird and it discards/doesn't display some fields? Cheers. -- I'm dangerous when I know what I'm doing.

John Andersen wrote:

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.

In which case, the traceroute is: Traceroute to lists.suse.de (195.135.221.131), 30 hops max, 40 byte packets 1 * * * 2 cbr-pow-ibo-tit-2-loo-20.tpgi.com.au (202.7.162.164) 13.461 ms 13.467 ms 14.603 ms 3 cbr-pow-ibo-tit-1-fe-0-0.tpgi.com.au (203.26.16.193) 15.907 ms 20.007 ms 22.241 ms 4 Vlan222.12NOC76FF.optus.net.au (202.139.133.77) 26.783 ms 28.174 ms 31.218 ms 5 203.208.148.201 (203.208.148.201) 191.977 ms 192.484 ms 197.367 ms 6 so4-2-0-622M.ar2.PAO2.gblx.net (208.50.13.185) 198.525 ms 201.620 ms 204.366 ms 7 * * * 8 * * * 9 * * * 10 * * * 11 * * * 12 * * * 13 * * * 14 * * * 15 * * * 16 * * * 17 * * * 18 * * * 19 * * * 20 * * * 21 * * * 22 * * * 23 * * * 24 * * * 25 * * * 26 * * * 27 * * * 28 * * * 29 * * * 30 * * * See anything relevant? Cheers. -- I'm dangerous when I know what I'm doing.

John Andersen wrote:

On Friday 27 October 2006 02:17, Basil Chupin wrote:

...

6 so4-2-0-622M.ar2.PAO2.gblx.net (208.50.13.185) 198.525 ms 201.620 ms 204.366 ms

See anything relevant?

Only that once you get to Global Crossing's network pings aren't being returned any more.

Is this normal?

Global crossing has headquarters in Phoenix, but without the next hop being reported you really have no way to know the route taken.

Disclaimer: Even if you did know the route with traceroute its no guarantee the same route would be taken by mail originating from lists.suse.de. Its provides a good guess, but its only that.

I tried this again just a short time ago and got the exact same result.

So the mystery remains...

Indeed. Cheers. -- I'm dangerous when I know what I'm doing.

* John Andersen [10-28-06 00:18]:

Its not totally abnormal. Some carriers configure long haul lines (especially busy ones) to not return these. Traceroute itself is not much of a load, its regular ping floods they are worrying about.

try tcptraceroute tcptraceroute-1.5beta7-1.guru.suse101 tcptraceroute is a traceroute implementation using TCP packets. The more traditional traceroute(8) sends out either UDP or ICMP ECHO packets with a TTL of one, and increments the TTL until the destination has been reached. By printing the gateways that generate ICMP time exceeded messages along the way, it is able to determine the path packets are taking to reach the destination. The problem is that with the widespread use of firewalls on the modern Internet, many of the packets that traceroute(8) sends out end up being filtered, making it impossible to completely trace the path to the destination. However, in many cases, these firewalls will permit inbound TCP packets to specific ports that hosts sitting behind the firewall are listening for connections on. By sending out TCP SYN packets instead of UDP or ICMP ECHO packets, tcptraceroute is able to bypass the most common firewall filters. It is worth noting that tcptraceroute never completely establishes a TCP connection with the destination host. If the host is not listening for incoming connections, it will respond with an RST indicating that the port is closed. If the host instead responds with a SYN|ACK, the port is known to be open, and an RST is sent by the kernel tcptraceroute is running on to tear down the connection without completing three-way handshake. This is the same half-open scanning technique that nmap(1) uses when passed the -sS flag. -- Patrick Shanahan Registered Linux User #207535 http://wahoo.no-ip.org @ http://counter.li.org HOG # US1244711 Photo Album: http://wahoo.no-ip.org/gallery2