From: "Russ Cox" <rsc@swtch.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
Subject: Re: [9fans] $smtp dns failure
Date: Tue, 16 Jan 2007 14:30:12 -0500 [thread overview]
Message-ID: <ee9e417a0701161130r2cfb6fddk342f3c776b5a6daa@mail.gmail.com> (raw)
In-Reply-To: <0bfd32bfe8981a44d7e61aa8de388107@coraid.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.
Until you explain precisely which part of rfc 2821 you claim that
smtp.c does not follow and which part of smtp.c is not following it,
I don't see a point to continuing this conversation.
The particular case that I was talking about is when dns returns
"dns: dns failure", meaning that looking up the MX record produced
an error (like maybe the DNS server choked on the request),
not that the lookup returned "there are no MX records".
My reading of the RFC is that it does not cover this case.
Russ
next prev parent reply other threads:[~2007-01-16 19:30 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
2007-01-16 19:30 ` Russ Cox [this message]
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=ee9e417a0701161130r2cfb6fddk342f3c776b5a6daa@mail.gmail.com \
--to=rsc@swtch.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).