Test

Test

Thanks - Joe

[Nathanael D. Noblet]

[e-mail] wrote:
> Test

Test success!

Quoting "Nathanael D. Noblet" :
> [e-mail] wrote:
> > Test
>
> Test success!

Arggg, this is the only email I have recieved from the list  
today......something crazy is going on here......

Thanks - Joe

[pyro]

Greetings,

There seems to be a bit of jitter there. Yesterday, I didn't get much,
then this morning it all caught up at once.

G'day,
sjames

On Tue, 8 Apr 2008 [e-mail] wrote:
> Quoting "Nathanael D. Noblet" :
> > [e-mail] wrote:
> > > Test
> >
> > Test success!
>
> Arggg, this is the only email I have recieved from the list
> today......something crazy is going on here......
>
> Thanks - Joe

||||| |||| |||||||||||||  |||
by Linux Labs International, Inc.
   Steven James, CTO

866 824 9737 support

[Stefan Reinauer]

pyro wrote:
> Greetings,
>
> There seems to be a bit of jitter there. Yesterday, I didn't get much,
> then this morning it all caught up at once.

This is weird. Yahoo seems to temporarily block mails from coreboot.org 
"due to user complaints".
Other than that the mailserver seems to work just fine.

Stefan

Quoting pyro :
> Greetings,
>
> There seems to be a bit of jitter there. Yesterday, I didn't get much,
> then this morning it all caught up at once.
>
> G'day,
> sjames
>
> On Tue, 8 Apr 2008 [e-mail] wrote:
> > Quoting "Nathanael D. Noblet" :
> > > [e-mail] wrote:
> > > > Test
> > >
> > > Test success!
> >
> > Arggg, this is the only email I have recieved from the list
> > today......something crazy is going on here......

Well, I rebooted my email server, let's see if that helps....

Thanks - Joe

Quoting [e-mail]:
> Quoting pyro :
> > Greetings,
> >
> > There seems to be a bit of jitter there. Yesterday, I didn't get much,
> > then this morning it all caught up at once.
> >
> > G'day,
> > sjames
> >
> > On Tue, 8 Apr 2008 [e-mail] wrote:
> > > Quoting "Nathanael D. Noblet" :
> > > > [e-mail] wrote:
> > > > > Test
> > > >
> > > > Test success!
> > >
> > > Arggg, this is the only email I have recieved from the list
> > > today......something crazy is going on here......
>
> Well, I rebooted my email server, let's see if that helps....

Arggg again. I can see my emails in pipermail, but I am not getting  
any of them. Can someone look at the email headers and see it anything  
looks crazy?

Thanks - Joe

Thanks - Joe

[Ward Vandewege]

Hi Joe,

On Tue, Apr 08, 2008 at 05:09:28PM -0400, [e-mail] wrote:
> Arggg again. I can see my emails in pipermail, but I am not getting  
> any of them. Can someone look at the email headers and see it anything  
> looks crazy?

The problem seems to be that khepri (the coreboot.org server) can't connect
to port 25 on smittys.pointclark.net:

khepri:/var/log/exim $ telnet smittys.pointclark.net 25
Trying 65.175.181.44...

... that times out.
> From here in Boston:

$ telnet smittys.pointclark.net 25
Trying 65.175.181.44...
Connected to smittys.pointclark.net.
Escape character is '^]'.
220 smittys.pointclark.net ESMTP Postfix
quit
221 Bye
Connection closed by foreign host.

Traceroute looks normal:

khepri:/var/log/exim $ traceroute smittys.pointclark.net
traceroute to smittys.pointclark.net (65.175.181.44), 30 hops max, 40 byte
packets
 1  gw.rtr1.colo1.NBG1.ip-exchange.de (212.123.124.185)  0.317 ms   0.490 ms
0.501 ms
 2  ge3-5.cr2.NBG1.content-core.net (212.123.127.65)  0.224 ms   0.227 ms
0.217 ms
 3  Tenge2-4-57.cr3.FRA3.content-core.net (212.123.123.203)  3.525 ms   3.471
ms   3.484 ms
 4  4G-p2.cr1.FRA3.content-core.net (212.123.123.42)  3.503 ms   3.458 ms
3.402 ms
 5  193.159.224.21 (193.159.224.21)  3.707 ms   3.700 ms   3.509 ms
 6  f-ea5.F.DE.net.DTAG.DE (62.154.16.161)  3.741 ms   3.753 ms   3.759 ms
 7  te-4-4.car2.Frankfurt1.Level3.net (4.68.110.253)  4.089 ms   4.119 ms
4.101 ms
 8  ae-32-54.ebr2.Frankfurt1.Level3.net (4.68.118.126)  6.728 ms   16.346 ms
13.799 ms
 9  ae-1-100.ebr1.Frankfurt1.Level3.net (4.69.132.125)  13.597 ms   6.701 ms
6.489 ms
10  ae-2.ebr2.Paris1.Level3.net (4.69.132.141)  13.381 ms   26.367 ms
25.514 ms
11  ae-44.ebr2.Washington1.Level3.net (4.69.137.62)  100.867 ms
ae-41.ebr2.Washington1.Level3.net (4.69.137.50)  97.342 ms
ae-42.ebr2.Washington1.Level3.net (4.69.137.54)  97.593 ms
12  ae-82-82.csw3.Washington1.Level3.net (4.69.134.154)  107.265 ms
ae-92-92.csw4.Washington1.Level3.net (4.69.134.158)  97.440 ms
ae-62-62.csw1.Washington1.Level3.net (4.69.134.146)  101.640 ms
13  ae-71-71.ebr1.Washington1.Level3.net (4.69.134.133)  97.547 ms
ae-81-81.ebr1.Washington1.Level3.net (4.69.134.137)  103.698 ms *
14  ae-4-4.car1.Cleveland1.Level3.net (4.69.132.193)  101.302 ms   102.199 ms
102.147 ms
15  ae-11-11.car2.Cleveland1.Level3.net (4.69.132.198)  102.603 ms   101.464
ms   101.079 ms
16  ROADRUNNER.car2.Cleveland1.Level3.net (4.78.59.46)  122.099 ms   122.230
ms   121.963 ms
17  gig15-0-0.ptldmeptl-rtr02.nyroc.rr.com (24.24.7.150)  134.609 ms
135.359 ms   134.807 ms
18  rrcs-24-39-3-2.nys.biz.rr.com (24.39.3.2)  134.779 ms   136.254 ms
135.865 ms
19  * * *
...

And from here in Boston:

$ traceroute smittys.pointclark.net
traceroute to smittys.pointclark.net (65.175.181.44), 30 hops max, 40 byte
packets
 ...
 3  vl200.aggr1.sbo.ma.rcn.net (209.6.160.100)  16.420 ms  16.833 ms  17.103
ms
 4  ge3-4.border1.sbo.ma.rcn.net (207.172.19.85)  46.691 ms  47.108 ms
47.312 ms
 5  gigabitethernet6-24.car2.bos1.Level3.net (63.211.176.17)  17.384 ms
20.025 ms  20.415 ms
 6  ae-5-5.ebr1.NewYork1.Level3.net (4.69.132.250)  28.679 ms  27.749 ms
25.022 ms
 7  ae-81-81.csw3.NewYork1.Level3.net (4.69.134.74)  28.837 ms
ae-91-91.csw4.NewYork1.Level3.net (4.69.134.78)  31.413 ms
ae-61-61.csw1.NewYork1.Level3.net (4.69.134.66)  22.518 ms
 8  ae-74-74.ebr4.NewYork1.Level3.net (4.69.134.117)  25.795 ms
ae-83-83.ebr3.NewYork1.Level3.net (4.69.134.105)  21.125 ms
ae-93-93.ebr3.NewYork1.Level3.net (4.69.134.109)  19.931 ms
 9  ae-3.ebr3.Washington1.Level3.net (4.69.132.89)  26.395 ms
ae-3.ebr4.Washington1.Level3.net (4.69.132.93)  26.157 ms
ae-3.ebr3.Washington1.Level3.net (4.69.132.89)  27.952 ms
10  ae-74-74.csw2.Washington1.Level3.net (4.69.134.182)  27.395 ms
ae-83-83.csw3.Washington1.Level3.net (4.69.134.170)  35.010 ms
ae-94-94.csw4.Washington1.Level3.net (4.69.134.190)  33.347 ms
11  ae-61-61.ebr1.Washington1.Level3.net (4.69.134.129)  26.157 ms
ae-71-71.ebr1.Washington1.Level3.net (4.69.134.133)  26.932 ms
ae-81-81.ebr1.Washington1.Level3.net (4.69.134.137)  26.572 ms
12  ae-4-4.car1.Cleveland1.Level3.net (4.69.132.193)  32.026 ms  32.630 ms
32.396 ms
13  ae-11-11.car2.Cleveland1.Level3.net (4.69.132.198)  32.929 ms  33.136 ms
35.418 ms
14  ROADRUNNER.car2.Cleveland1.Level3.net (4.78.59.46)  34.417 ms  34.816 ms
35.012 ms
15  gig15-0-0.ptldmeptl-rtr02.nyroc.rr.com (24.24.7.150)  42.779 ms  42.381
ms  46.577 ms
16  rrcs-24-39-3-2.nys.biz.rr.com (24.39.3.2)  49.243 ms  48.864 ms  48.490
ms
17  rrcs-24-39-50-36.nys.biz.rr.com (24.39.50.36)  51.890 ms  48.315 ms
51.254 ms
18  * * *
19  * * *
20  * * *
21  * * *
...

So, "the internet is broken". Routing problem somewhere between Germany and
the US?

Or... you're not doing fancy antispam based on RBLs or something are you,
that would just drop incoming tcp connections from 'suspicious' IPs?

If you hop on IRC, we can discuss further there.

Thanks,
Ward.

[Stefan Reinauer]

Ward Vandewege wrote:
> Hi Joe,
>
> On Tue, Apr 08, 2008 at 05:09:28PM -0400, [e-mail] wrote:
> > Arggg again. I can see my emails in pipermail, but I am not getting  
> > any of them. Can someone look at the email headers and see it anything  
> > looks crazy?
>
> The problem seems to be that khepri (the coreboot.org server) can't connect
> to port 25 on smittys.pointclark.net:
>
> khepri:/var/log/exim $ telnet smittys.pointclark.net 25
> Trying 65.175.181.44...
>
> ... that times out.
>
> From here in Boston:
>
> $ telnet smittys.pointclark.net 25
> Trying 65.175.181.44...
> Connected to smittys.pointclark.net.
> Escape character is '^]'.
> 220 smittys.pointclark.net ESMTP Postfix
> quit
> 221 Bye
> Connection closed by foreign host.
>
> Traceroute looks normal:
>
> khepri:/var/log/exim $ traceroute smittys.pointclark.net
> traceroute to smittys.pointclark.net (65.175.181.44), 30 hops max, 40 byte
> packets
>  1  gw.rtr1.colo1.NBG1.ip-exchange.de (212.123.124.185)  0.317 ms   0.490 ms
> 0.501 ms
>  2  ge3-5.cr2.NBG1.content-core.net (212.123.127.65)  0.224 ms   0.227 ms
> 0.217 ms
>  3  Tenge2-4-57.cr3.FRA3.content-core.net (212.123.123.203)  3.525 ms   3.471
> ms   3.484 ms
>  4  4G-p2.cr1.FRA3.content-core.net (212.123.123.42)  3.503 ms   3.458 ms
> 3.402 ms
>  5  193.159.224.21 (193.159.224.21)  3.707 ms   3.700 ms   3.509 ms
>  6  f-ea5.F.DE.net.DTAG.DE (62.154.16.161)  3.741 ms   3.753 ms   3.759 ms
>  7  te-4-4.car2.Frankfurt1.Level3.net (4.68.110.253)  4.089 ms   4.119 ms
> 4.101 ms
>  8  ae-32-54.ebr2.Frankfurt1.Level3.net (4.68.118.126)  6.728 ms   16.346 ms
> 13.799 ms
>  9  ae-1-100.ebr1.Frankfurt1.Level3.net (4.69.132.125)  13.597 ms   6.701 ms
> 6.489 ms
> 10  ae-2.ebr2.Paris1.Level3.net (4.69.132.141)  13.381 ms   26.367 ms
> 25.514 ms
> 11  ae-44.ebr2.Washington1.Level3.net (4.69.137.62)  100.867 ms
> ae-41.ebr2.Washington1.Level3.net (4.69.137.50)  97.342 ms
> ae-42.ebr2.Washington1.Level3.net (4.69.137.54)  97.593 ms
> 12  ae-82-82.csw3.Washington1.Level3.net (4.69.134.154)  107.265 ms
> ae-92-92.csw4.Washington1.Level3.net (4.69.134.158)  97.440 ms
> ae-62-62.csw1.Washington1.Level3.net (4.69.134.146)  101.640 ms
> 13  ae-71-71.ebr1.Washington1.Level3.net (4.69.134.133)  97.547 ms
> ae-81-81.ebr1.Washington1.Level3.net (4.69.134.137)  103.698 ms *
> 14  ae-4-4.car1.Cleveland1.Level3.net (4.69.132.193)  101.302 ms   102.199 ms
> 102.147 ms
> 15  ae-11-11.car2.Cleveland1.Level3.net (4.69.132.198)  102.603 ms   101.464
> ms   101.079 ms
> 16  ROADRUNNER.car2.Cleveland1.Level3.net (4.78.59.46)  122.099 ms   122.230
> ms   121.963 ms
> 17  gig15-0-0.ptldmeptl-rtr02.nyroc.rr.com (24.24.7.150)  134.609 ms
> 135.359 ms   134.807 ms
> 18  rrcs-24-39-3-2.nys.biz.rr.com (24.39.3.2)  134.779 ms   136.254 ms
> 135.865 ms
> 19  * * *
> ...
>
> And from here in Boston:
>
> $ traceroute smittys.pointclark.net
> traceroute to smittys.pointclark.net (65.175.181.44), 30 hops max, 40 byte
> packets
>  ...
>  3  vl200.aggr1.sbo.ma.rcn.net (209.6.160.100)  16.420 ms  16.833 ms  17.103
> ms
>  4  ge3-4.border1.sbo.ma.rcn.net (207.172.19.85)  46.691 ms  47.108 ms
> 47.312 ms
>  5  gigabitethernet6-24.car2.bos1.Level3.net (63.211.176.17)  17.384 ms
> 20.025 ms  20.415 ms
>  6  ae-5-5.ebr1.NewYork1.Level3.net (4.69.132.250)  28.679 ms  27.749 ms
> 25.022 ms
>  7  ae-81-81.csw3.NewYork1.Level3.net (4.69.134.74)  28.837 ms
> ae-91-91.csw4.NewYork1.Level3.net (4.69.134.78)  31.413 ms
> ae-61-61.csw1.NewYork1.Level3.net (4.69.134.66)  22.518 ms
>  8  ae-74-74.ebr4.NewYork1.Level3.net (4.69.134.117)  25.795 ms
> ae-83-83.ebr3.NewYork1.Level3.net (4.69.134.105)  21.125 ms
> ae-93-93.ebr3.NewYork1.Level3.net (4.69.134.109)  19.931 ms
>  9  ae-3.ebr3.Washington1.Level3.net (4.69.132.89)  26.395 ms
> ae-3.ebr4.Washington1.Level3.net (4.69.132.93)  26.157 ms
> ae-3.ebr3.Washington1.Level3.net (4.69.132.89)  27.952 ms
> 10  ae-74-74.csw2.Washington1.Level3.net (4.69.134.182)  27.395 ms
> ae-83-83.csw3.Washington1.Level3.net (4.69.134.170)  35.010 ms
> ae-94-94.csw4.Washington1.Level3.net (4.69.134.190)  33.347 ms
> 11  ae-61-61.ebr1.Washington1.Level3.net (4.69.134.129)  26.157 ms
> ae-71-71.ebr1.Washington1.Level3.net (4.69.134.133)  26.932 ms
> ae-81-81.ebr1.Washington1.Level3.net (4.69.134.137)  26.572 ms
> 12  ae-4-4.car1.Cleveland1.Level3.net (4.69.132.193)  32.026 ms  32.630 ms
> 32.396 ms
> 13  ae-11-11.car2.Cleveland1.Level3.net (4.69.132.198)  32.929 ms  33.136 ms
> 35.418 ms
> 14  ROADRUNNER.car2.Cleveland1.Level3.net (4.78.59.46)  34.417 ms  34.816 ms
> 35.012 ms
> 15  gig15-0-0.ptldmeptl-rtr02.nyroc.rr.com (24.24.7.150)  42.779 ms  42.381
> ms  46.577 ms
> 16  rrcs-24-39-3-2.nys.biz.rr.com (24.39.3.2)  49.243 ms  48.864 ms  48.490
> ms
> 17  rrcs-24-39-50-36.nys.biz.rr.com (24.39.50.36)  51.890 ms  48.315 ms
> 51.254 ms
> 18  * * *
> 19  * * *
> 20  * * *
> 21  * * *
> ...
>
> So, "the internet is broken". Routing problem somewhere between Germany and
> the US?
>
> Or... you're not doing fancy antispam based on RBLs or something are you,
> that would just drop incoming tcp connections from 'suspicious' IPs?

This is weird.

host -t mx  smittys.pointclark.net
smittys.pointclark.net has no MX record

host -t mx  pointclark.net
pointclark.net mail is handled by 10 antivirus1.pointclark.com.
pointclark.net mail is handled by 10 antivirus2.pointclark.com.
pointclark.net mail is handled by 10 antivirus3.pointclark.com.
pointclark.net mail is handled by 10 antivirus4.pointclark.com.

Sending mails via the MXes of pointclark.net works fine.

So, yes, either someone's blocking the connection or it's a 
transatlantic routing problem.

[pyro]

Greetings,

Meanwhile, the delays I saw look like they were just my mail server moving
slow due to a huge blast of incoming spam. Sorry about the red herring.

G'day,
sjames

On Tue, 8 Apr 2008, Stefan Reinauer wrote:
> Ward Vandewege wrote:
> > Hi Joe,
> >
> > On Tue, Apr 08, 2008 at 05:09:28PM -0400, [e-mail] wrote:
> > > Arggg again. I can see my emails in pipermail, but I am not getting
> > > any of them. Can someone look at the email headers and see it anything
> > > looks crazy?
> >
> > The problem seems to be that khepri (the coreboot.org server) can't connect
> > to port 25 on smittys.pointclark.net:
> >
> > khepri:/var/log/exim $ telnet smittys.pointclark.net 25
> > Trying 65.175.181.44...
> >
> > ... that times out.
> >
> > From here in Boston:
> >
> > $ telnet smittys.pointclark.net 25
> > Trying 65.175.181.44...
> > Connected to smittys.pointclark.net.
> > Escape character is '^]'.
> > 220 smittys.pointclark.net ESMTP Postfix
> > quit
> > 221 Bye
> > Connection closed by foreign host.
> >
> > Traceroute looks normal:
> >
> > khepri:/var/log/exim $ traceroute smittys.pointclark.net
> > traceroute to smittys.pointclark.net (65.175.181.44), 30 hops max, 40 byte
> > packets
> >  1  gw.rtr1.colo1.NBG1.ip-exchange.de (212.123.124.185)  0.317 ms   0.490 ms
> > 0.501 ms
> >  2  ge3-5.cr2.NBG1.content-core.net (212.123.127.65)  0.224 ms   0.227 ms
> > 0.217 ms
> >  3  Tenge2-4-57.cr3.FRA3.content-core.net (212.123.123.203)  3.525 ms   3.471
> > ms   3.484 ms
> >  4  4G-p2.cr1.FRA3.content-core.net (212.123.123.42)  3.503 ms   3.458 ms
> > 3.402 ms
> >  5  193.159.224.21 (193.159.224.21)  3.707 ms   3.700 ms   3.509 ms
> >  6  f-ea5.F.DE.net.DTAG.DE (62.154.16.161)  3.741 ms   3.753 ms   3.759 ms
> >  7  te-4-4.car2.Frankfurt1.Level3.net (4.68.110.253)  4.089 ms   4.119 ms
> > 4.101 ms
> >  8  ae-32-54.ebr2.Frankfurt1.Level3.net (4.68.118.126)  6.728 ms   16.346 ms
> > 13.799 ms
> >  9  ae-1-100.ebr1.Frankfurt1.Level3.net (4.69.132.125)  13.597 ms   6.701 ms
> > 6.489 ms
> > 10  ae-2.ebr2.Paris1.Level3.net (4.69.132.141)  13.381 ms   26.367 ms
> > 25.514 ms
> > 11  ae-44.ebr2.Washington1.Level3.net (4.69.137.62)  100.867 ms
> > ae-41.ebr2.Washington1.Level3.net (4.69.137.50)  97.342 ms
> > ae-42.ebr2.Washington1.Level3.net (4.69.137.54)  97.593 ms
> > 12  ae-82-82.csw3.Washington1.Level3.net (4.69.134.154)  107.265 ms
> > ae-92-92.csw4.Washington1.Level3.net (4.69.134.158)  97.440 ms
> > ae-62-62.csw1.Washington1.Level3.net (4.69.134.146)  101.640 ms
> > 13  ae-71-71.ebr1.Washington1.Level3.net (4.69.134.133)  97.547 ms
> > ae-81-81.ebr1.Washington1.Level3.net (4.69.134.137)  103.698 ms *
> > 14  ae-4-4.car1.Cleveland1.Level3.net (4.69.132.193)  101.302 ms   102.199 ms
> > 102.147 ms
> > 15  ae-11-11.car2.Cleveland1.Level3.net (4.69.132.198)  102.603 ms   101.464
> > ms   101.079 ms
> > 16  ROADRUNNER.car2.Cleveland1.Level3.net (4.78.59.46)  122.099 ms   122.230
> > ms   121.963 ms
> > 17  gig15-0-0.ptldmeptl-rtr02.nyroc.rr.com (24.24.7.150)  134.609 ms
> > 135.359 ms   134.807 ms
> > 18  rrcs-24-39-3-2.nys.biz.rr.com (24.39.3.2)  134.779 ms   136.254 ms
> > 135.865 ms
> > 19  * * *
> > ...
> >
> > And from here in Boston:
> >
> > $ traceroute smittys.pointclark.net
> > traceroute to smittys.pointclark.net (65.175.181.44), 30 hops max, 40 byte
> > packets
> >  ...
> >  3  vl200.aggr1.sbo.ma.rcn.net (209.6.160.100)  16.420 ms  16.833 ms  17.103
> > ms
> >  4  ge3-4.border1.sbo.ma.rcn.net (207.172.19.85)  46.691 ms  47.108 ms
> > 47.312 ms
> >  5  gigabitethernet6-24.car2.bos1.Level3.net (63.211.176.17)  17.384 ms
> > 20.025 ms  20.415 ms
> >  6  ae-5-5.ebr1.NewYork1.Level3.net (4.69.132.250)  28.679 ms  27.749 ms
> > 25.022 ms
> >  7  ae-81-81.csw3.NewYork1.Level3.net (4.69.134.74)  28.837 ms
> > ae-91-91.csw4.NewYork1.Level3.net (4.69.134.78)  31.413 ms
> > ae-61-61.csw1.NewYork1.Level3.net (4.69.134.66)  22.518 ms
> >  8  ae-74-74.ebr4.NewYork1.Level3.net (4.69.134.117)  25.795 ms
> > ae-83-83.ebr3.NewYork1.Level3.net (4.69.134.105)  21.125 ms
> > ae-93-93.ebr3.NewYork1.Level3.net (4.69.134.109)  19.931 ms
> >  9  ae-3.ebr3.Washington1.Level3.net (4.69.132.89)  26.395 ms
> > ae-3.ebr4.Washington1.Level3.net (4.69.132.93)  26.157 ms
> > ae-3.ebr3.Washington1.Level3.net (4.69.132.89)  27.952 ms
> > 10  ae-74-74.csw2.Washington1.Level3.net (4.69.134.182)  27.395 ms
> > ae-83-83.csw3.Washington1.Level3.net (4.69.134.170)  35.010 ms
> > ae-94-94.csw4.Washington1.Level3.net (4.69.134.190)  33.347 ms
> > 11  ae-61-61.ebr1.Washington1.Level3.net (4.69.134.129)  26.157 ms
> > ae-71-71.ebr1.Washington1.Level3.net (4.69.134.133)  26.932 ms
> > ae-81-81.ebr1.Washington1.Level3.net (4.69.134.137)  26.572 ms
> > 12  ae-4-4.car1.Cleveland1.Level3.net (4.69.132.193)  32.026 ms  32.630 ms
> > 32.396 ms
> > 13  ae-11-11.car2.Cleveland1.Level3.net (4.69.132.198)  32.929 ms  33.136 ms
> > 35.418 ms
> > 14  ROADRUNNER.car2.Cleveland1.Level3.net (4.78.59.46)  34.417 ms  34.816 ms
> > 35.012 ms
> > 15  gig15-0-0.ptldmeptl-rtr02.nyroc.rr.com (24.24.7.150)  42.779 ms  42.381
> > ms  46.577 ms
> > 16  rrcs-24-39-3-2.nys.biz.rr.com (24.39.3.2)  49.243 ms  48.864 ms  48.490
> > ms
> > 17  rrcs-24-39-50-36.nys.biz.rr.com (24.39.50.36)  51.890 ms  48.315 ms
> > 51.254 ms
> > 18  * * *
> > 19  * * *
> > 20  * * *
> > 21  * * *
> > ...
> >
> > So, "the internet is broken". Routing problem somewhere between Germany and
> > the US?
> >
> > Or... you're not doing fancy antispam based on RBLs or something are you,
> > that would just drop incoming tcp connections from 'suspicious' IPs?
>
> This is weird.
>
> host -t mx  smittys.pointclark.net
> smittys.pointclark.net has no MX record
>
> host -t mx  pointclark.net
> pointclark.net mail is handled by 10 antivirus1.pointclark.com.
> pointclark.net mail is handled by 10 antivirus2.pointclark.com.
> pointclark.net mail is handled by 10 antivirus3.pointclark.com.
> pointclark.net mail is handled by 10 antivirus4.pointclark.com.
>
> Sending mails via the MXes of pointclark.net works fine.
>
> So, yes, either someone's blocking the connection or it's a
> transatlantic routing problem.

||||| |||| |||||||||||||  |||
by Linux Labs International, Inc.
   Steven James, CTO

866 824 9737 support