From mboxrd@z Thu Jan  1 00:00:00 1970
From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@cse.psu.edu, Skip Tavakkolian <9nut@9netics.com>
References: <3bf911322c8906ee1f18c636d30c6d96@9netics.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
In-Reply-To: <3bf911322c8906ee1f18c636d30c6d96@9netics.com>
Subject: [9fans] smtp timeouts with mail hosted at godaddy.com
Message-Id: <20060321021117.2B3E51D482@dexter-peak.quanstro.net>
Date: Mon, 20 Mar 2006 20:11:17 -0600
Cc:
Topicbox-Message-UUID: 1ae8c828-ead1-11e9-9d60-3106f5b1d025

unfortunately, this is expected.

outbound mail is handled by upas/smtp, which does not drop any
breadcrumbs for itself to remember past connect failures.
also, since each email is handled by a seperate upas/smtp process,
there's no hope of communicating the failure.

there's nothing wrong with this approach per se, but
it is a bit annoying.

Skip Tavakkolian <9nut@9netics.com> writes

|
| i'm getting the following failures trying to deliver mail for two
| different domains.  they're both hosted at godaddy.com.  anyone has
| seen this?
|
| sending /net/dns 'XXXXX mx'
| dns mx: XXXXX mx	10 mailstore1.secureserver.net
| dns mx: XXXXX mx	0 smtp.secureserver.net
| dns mx; got 2 entries
| mxdial trying /net/net!smtp.secureserver.net!smtp
| smtp timeout: connection to net!XXXXX timed out
|
| sending /net/dns 'YYYYY mx'
| dns mx: YYYYY mx	10 mailstore1.secureserver.net
| dns mx: YYYYY mx	0 smtp.secureserver.net
| dns mx; got 2 entries
| mxdial trying /net/net!smtp.secureserver.net!smtp
| smtp timeout: connection to net!YYYYY timed out