9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: erik quanstrom <quanstro@coraid.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] $smtp dns failure
Date: Tue, 16 Jan 2007 14:05:05 -0500	[thread overview]
Message-ID: <0bfd32bfe8981a44d7e61aa8de388107@coraid.com> (raw)
In-Reply-To: <ee9e417a0701161044i5fc77ddfrbfa3585f3cd91036@mail.gmail.com>

§5 of rfc 2821 spells out how to do the lookup.  smtpd should do that.
if there are any huristics to apply while running the lookup, it
would make sense to me to do as sendmail/postifix/qmail do.
smtp is an interface to the world.  being different isn't a virtue
in this case.

- erik

On Tue Jan 16 13:46:09 EST 2007, rsc@swtch.com wrote:
> > 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.
> 
> if there is a dns failure, the logic there is that since the
> mx could not be determined due to some transient dns error,
> we are not going to blindly try the underlying host name,
> because that is likely to be wrong.  i am sure that i put this
> in because of actual problems.
> 
> the real problem is that smtp is doing a dns lookup on 192.168.0.22,
> which ndb/dns interprets as a request for a reverse lookup
> (that is, it looks up 22.0.168.192.in-addr.arpa), which fails.
> mxlookup should probably check whether ds->host is a
> valid ip address all by itself, and then return 0 if so, rather
> than ask dns anything at all.  unfortunately i don't think there
> is a library routine that will tell us whether a string is a valid
> ip address.  parseip doesn't.
> 
> russ


  parent reply	other threads:[~2007-01-16 19:05 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
2007-01-16 18:44             ` Russ Cox
2007-01-16 18:52               ` lucio
2007-01-16 19:05               ` erik quanstrom [this message]
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=0bfd32bfe8981a44d7e61aa8de388107@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).