From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <9ab217670704130902u7ccd520dxf962088208268679@mail.gmail.com>
Date: Fri, 13 Apr 2007 12:02:50 -0400
From: "Devon H. O'Dell" <devon.odell@gmail.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
Subject: Re: [9fans] SMTP Woes
In-Reply-To: <ee9e417a0704130844m793257a3j5cf7ae204364a431@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <9ab217670704130734j7cad283ara8a51628d605be24@mail.gmail.com>
	<ee9e417a0704130844m793257a3j5cf7ae204364a431@mail.gmail.com>
Topicbox-Message-UUID: 46e4c110-ead2-11e9-9d60-3106f5b1d025

2007/4/13, Russ Cox <rsc@swtch.com>:
> > 9top% upas/smtp -d -as -h yourdomain.dom 'net!$smtp' dho devon.odell@gmail.com
> > expanding /net!$smtp
> > sending /net/dns 'smtp.gmail.com mx'
> > dns: dns: resource does not exist
> > mxdial trying /net/net!smtp.gmail.com!smtp
> > smtp: connection timed out (net!smtp.gmail.com)
>
> Your network connection is timing out (as it says).
>
> Yourdomain.dom is used for various purposes
> during the smtp conversation.  Smtp didn't even
> bother looking for the MX of gmail.com.
> So both of those are irrelevant.
>
> Smtp did look to see if there was an MX for
> smtp.gmail.com, but it didn't find one so it is
> trying to connect directly.  That's just fine too.
>
> You have a good error right there:
>
> > mxdial trying /net/net!smtp.gmail.com!smtp
> > smtp: connection timed out (net!smtp.gmail.com)
>
> The network connection smtp is trying to make is timing out.
> You don't have a mail problem; you have a network problem.
> At least that is simpler.

Not really. Because this is with the same laptop I use to manage the
changes, I can run abaco and browse to my heart's content. I can IRC
from here, I can VNC to my Mac Mini.

> Try connecting with a simple program:
>
>   con -l tcp!smtp.gmail.com!smtp
>
> When that fails, verify that you can resolve the name
> smtp.gmail.com using ndb/dnsquery.
>
> When that succeeds, try connecting directly to the IP address:
>
>   con -l tcp!209.85.133.109!smtp
>
> When that fails, make sure you can connect to other
> systems:
>
>   con -l tcp!plan9.bell-labs.com!http
>
> When that succeeds, try connecting to the SMTP port using
> a different operating system or machine on the same network.
>
> It could be that your ISP is blocking external SMTP connections,
> for example.

I'd be inclined to say that this is the most likely culprit. What's
weird is that, using the same ISP at work, I don't have this issue at
work. I'll call them up and see what the issue is. Sorry for the
noise.

> Russ

--dho