email returned, please help.

Evoir · 08-05-2001, 12:52 PM

I am having trouble with sending an important email. It gets sent abck to me like this:
------------------
Hi. This is the qmail-send program at questmail.futurequest.net.
I'm afraid I wasn't able to deliver your message to the following
addresses.
This is a permanent error; I've given up. Sorry it didn't work out.

<svelasquez@msmagazine.com>:
Sorry, I wasn't able to establish an SMTP connection. (#4.4.1)
I'm not going to try again; this message has been in the queue too long.

--- Below this line is a copy of the message.

Return-Path: <gretchen@leeworks.com>
Received: (qmail 18727 invoked from network); 4 Aug 2001 20:43:33 -0000
Received: from zoomer.futurequest.net (63.236.215.2)
by questmail.futurequest.net with SMTP; 4 Aug 2001 20:43:33 -0000
Received: (qmail 15187 invoked from network); 4 Aug 2001 20:36:40 -0000
Received: from unknown (HELO ?192.168.1.102?) (63.193.240.12)
by leeworks.com with SMTP; 4 Aug 2001 20:36:40 -0000
Subject: Melissa Etheridge Clip (Resend)
Date: Sat, 4 Aug 2001 13:36:05 -0400
x-mailer: Claris Emailer 2.0v3, January 22, 1998
From: Gretchen Lee <gretchen@leeworks.com>
To: "Shirley Velasquez" <svelasquez@msmagazine.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-transfer-encoding: quoted-printable

------------------

I am pretty darn sure the adress is correct. What could be causing this? I need to get this email to them asap.

**Terra** · 08-05-2001, 01:09 PM

The MX (mail exchanger) for msmagazine.com == mail.msmagazine.com == 209.227.43.195

Testing pure connection: $telnet mail.msmagazine.com 25

results in error message: Unable to connect to remote host: No route to host

You will need to contact the administrator for the msmagazine.com network as there is a looped route in New York within the Verio.net facility...

Quote:

tracert to mail.msmagazine.com (209.227.43.195), 30 hops max, 38 byte packets
1 065-220.maxcess.net (63.95.220.65) 0.646 ms 0.405 ms 0.414 ms
2 tpa-edge-03.inet.qwest.net (63.144.0.105) 5.027 ms 4.998 ms 4.932 ms
3 tpa-core-01.inet.qwest.net (205.171.27.25) 5.026 ms 5.346 ms 5.068 ms
4 dca-core-02.inet.qwest.net (205.171.5.73) 30.994 ms 30.740 ms 30.805 ms
5 dca-brdr-01.inet.qwest.net (205.171.9.54) 30.563 ms 31.731 ms 30.575 ms
6 iconspn.inet.qwest.net (205.171.4.110) 31.136 ms 31.090 ms 31.246 ms
7 p4-2-1-0.r01.mclnva02.us.bb.verio.net (129.250.2.250) 32.409 ms 31.311 ms 31.273 ms
8 p4-7-2-0.r00.nycmny06.us.bb.verio.net (129.250.3.181) 36.537 ms 36.931 ms 36.569 ms
9 p4-1-1-0.r00.nycmny01.us.bb.verio.net (129.250.4.49) 36.991 ms 36.669 ms 36.666 ms
10 ge-0-0-0.a08.nycmny01.us.ra.verio.net (129.250.26.13) 36.607 ms 38.882 ms 38.252 ms
11 d3-11-0-0.a00.nycmny03.us.ra.verio.net (129.250.126.90) 37.594 ms 37.337 ms 38.996 ms
12 s0.ms-magazine.ny.us.customer.verio.net (209.227.58.214) 47.107 ms 45.186 ms 45.873 ms
13 d1-2-1-0-15-0.a00.nycmny03.us.ra.verio.net (165.254.188.57) 40.901 ms 41.232 ms 40.814 ms
14 s0.ms-magazine.ny.us.customer.verio.net (209.227.58.214) 48.106 ms 47.526 ms 48.526 ms
15 d1-2-1-0-15-0.a00.nycmny03.us.ra.verio.net (165.254.188.57) 44.824 ms 44.831 ms 49.300 ms
16 s0.ms-magazine.ny.us.customer.verio.net (209.227.58.214) 51.976 ms 56.019 ms 52.423 ms
17 d1-2-1-0-15-0.a00.nycmny03.us.ra.verio.net (165.254.188.57) 47.044 ms 47.340 ms 47.334 ms
18 s0.ms-magazine.ny.us.customer.verio.net (209.227.58.214) 56.181 ms 54.623 ms 57.656 ms
19 d1-2-1-0-15-0.a00.nycmny03.us.ra.verio.net (165.254.188.57) 50.790 ms 50.864 ms 50.147 ms
20 s0.ms-magazine.ny.us.customer.verio.net (209.227.58.214) 60.095 ms 63.519 ms 58.396 ms
21 d1-2-1-0-15-0.a00.nycmny03.us.ra.verio.net (165.254.188.57) 54.267 ms 53.580 ms 56.183 ms
22 s0.ms-magazine.ny.us.customer.verio.net (209.227.58.214) 69.121 ms 62.151 ms 60.932 ms
23 d1-2-1-0-15-0.a00.nycmny03.us.ra.verio.net (165.254.188.57) 60.773 ms 57.596 ms 59.784 ms
24 s0.ms-magazine.ny.us.customer.verio.net (209.227.58.214) 65.040 ms 65.114 ms 65.810 ms
25 d1-2-1-0-15-0.a00.nycmny03.us.ra.verio.net (165.254.188.57) 61.948 ms 61.463 ms 60.526 ms
26 s0.ms-magazine.ny.us.customer.verio.net (209.227.58.214) 68.848 ms 67.782 ms 67.553 ms
27 d1-2-1-0-15-0.a00.nycmny03.us.ra.verio.net (165.254.188.57) 64.377 ms 63.681 ms 65.345 ms
28 s0.ms-magazine.ny.us.customer.verio.net (209.227.58.214) 77.814 ms 71.189 ms 71.094 ms
29 d1-2-1-0-15-0.a00.nycmny03.us.ra.verio.net (165.254.188.57) 69.472 ms 66.948 ms 68.520 ms
30 s0.ms-magazine.ny.us.customer.verio.net (209.227.58.214) 76.942 ms 74.801 ms 78.827 ms

No wonder we couldn't deliver, I bet our mail server is still dizzy...

--
Terra
--Jibber Jabber--
FutureQuest

Evoir · 08-05-2001, 01:42 PM

Thanks Terra,

I love that I get an answer within 20 minutes from the CTO on a Sunday! I love FQ!

We'll try later. Perhaps the issue will resolve itself?

Thansk again for checking into it.

Evie