From: erik quanstrom <quanstro@coraid.com>
To: rsc@swtch.com, 9fans@cse.psu.edu
Subject: Re: [9fans] $smtp dns failure
Date: Tue, 16 Jan 2007 15:31:31 -0500 [thread overview]
Message-ID: <81c03baf080b2b71267e6095a9927d2c@coraid.com> (raw)
i'm not sure why you're taking offence. to me it seemed clear that mxlookup
differs from the algorithm in section 5 of 2821 and what other mailers do.
the rfc doesn't say that we need to abort of the mx lookup fails. i think this
is important because it's possible for an mx lookup to fail and an a/a6 lookup on
the same name return results. i had quite a bit of trouble with this when using
level-5's dns last year. in addition, a quick inspection of postfix' src/smtp/smtp_addr.c
seems to confirm that they perform a/a6 lookup on mx lookup failure. since
other smtp agents don't notice the misconfiguration, we are left to find it.
anyway, i put the effort into pulling together my notes from last year on this
to help, not to annoy. hopefull this information is not a further annoyance.
- erik
next reply other threads:[~2007-01-16 20:31 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-16 20:31 erik quanstrom [this message]
2007-01-16 20:50 ` geoff
-- strict thread matches above, loose matches on Subject: below --
2007-01-16 17:01 erik quanstrom
2007-01-15 19:28 erik quanstrom
2007-01-15 19:42 ` Paul Lalonde
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
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=81c03baf080b2b71267e6095a9927d2c@coraid.com \
--to=quanstro@coraid.com \
--cc=9fans@cse.psu.edu \
--cc=rsc@swtch.com \
/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).