From: erik quanstrom <quanstro@coraid.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] $smtp dns failure
Date: Tue, 16 Jan 2007 13:31:43 -0500 [thread overview]
Message-ID: <1ce6eebbc3d317dc6bbc8559d66eef12@coraid.com> (raw)
In-Reply-To: <f9ae8d9e3bfb827df90df3cc115efe47@quintile.net>
there is an interesting case with mxlookup1() in mxdial.c.
if a dns /failure/ is reported for the mx lookup, then mxdial doesn't
try a/cname records. i've had trouble in the past with mx failures when the
a record looks up just fine. i'm not sure if the standard says one must quit
on dns failure.
- erik
On Tue Jan 16 13:25:49 EST 2007, steve@quintile.net wrote:
> > 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.
>
> Strange, where does it get this IP address from?
> do you have smtp=192.168.0.22 in /lib/ndb/local?
>
> The smtp= should point to a FQDN rather than an IP address
> to allow upas/smtp to look up the MX and then A RRs.
>
> I get this:
>
> exec /bin/upas/smtp -d -g 'net!$smtp' -h quintile.net 'net!$smtp' steve steve.simon@mywork.com
> expanding /net!$smtp
> sending /net/dns 'smtp.myisp.com mx'
> dns: dns: resource does not exist
> mxdial trying /net/net!smtp.myisp.com!smtp
> 220 ESMTP server ready
>
> -Steve
next prev parent reply other threads:[~2007-01-16 18:31 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-15 16:55 Matthias Teege
2007-01-15 18:05 ` Federico Benavento
2007-01-15 19:22 ` Russ Cox
2007-01-15 18:10 ` geoff
2007-01-15 20:02 ` Matthias Teege
2007-01-15 23:35 ` Steve Simon
2007-01-16 16:46 ` Matthias Teege
2007-01-16 18:21 ` Steve Simon
2007-01-16 18:31 ` erik quanstrom [this message]
2007-01-16 18:44 ` Russ Cox
2007-01-16 18:52 ` lucio
2007-01-16 19:05 ` erik quanstrom
2007-01-16 19:30 ` Russ Cox
2007-01-15 19:28 erik quanstrom
2007-01-15 19:42 ` Paul Lalonde
2007-01-16 17:01 erik quanstrom
2007-01-16 20:31 erik quanstrom
2007-01-16 20:50 ` geoff
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1ce6eebbc3d317dc6bbc8559d66eef12@coraid.com \
--to=quanstro@coraid.com \
--cc=9fans@cse.psu.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).