From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <88a477560701160846h5537a2b0lbe53f2e09547adbb@mail.gmail.com>
Date: Tue, 16 Jan 2007 17:46:18 +0100
From: "Matthias Teege" <mteege@gmail.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
Subject: Re: [9fans] $smtp dns failure
In-Reply-To: <825ab1b11c6efdfedc86a4826906ef65@quintile.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <88a477560701151202x7491769dwd738d2284ebccbe2@mail.gmail.com>
	<825ab1b11c6efdfedc86a4826906ef65@quintile.net>
Topicbox-Message-UUID: 04313cd6-ead2-11e9-9d60-3106f5b1d025

On 1/16/07, Steve Simon <steve@quintile.net> wrote:

> Finally you can exec smtp with the -d option (debug) to see the SMTP conversation,
> and perhaps more importantly the DNS lookups (and failures) that occur.

Yes, and it looks like smtp look for an mx record of the smtpserver

exec /bin/upas/smtp -d -h crn.mteege.de 'net!$smtp' mtg mteege@gmail.com
expanding /net!$smtp
sending /net/dns '192.168.0.22 mx'
dns: dns: dns failure

There is no mx record for 192.168.0.22. If I use 'mteege.de', which
has a mx record (192.168.0.22), sending mail works.

I'm not sure if the behavior of upas/smtp is correct.

Matthias