From: kaih@khms.westfalen.de (Kai Henningsen)
To: linux-kernel@vger.kernel.org
Subject: Re: DNS goofups galore...
Date: 12 Feb 2001 22:20:00 +0200 [thread overview]
Message-ID: <7vh2HM81w-B@khms.westfalen.de> (raw)
In-Reply-To: <968mjv$l9t$1@forge.intermeta.de>
In-Reply-To: <95ulrk$aik$1@forge.intermeta.de> <20010209080454.A17656@beops-jg2.be.uu.net> <968mjv$l9t$1@forge.intermeta.de>
hps@tanstaafl.de (Henning P. Schmiedehausen) wrote on 12.02.01 in <968mjv$l9t$1@forge.intermeta.de>:
> jan.gyselinck@be.uu.net (Jan Gyselinck) writes:
>
> >There's not really something wrong with MX's pointing to CNAME's. It's
> >just that some mailservers could (can?) not handle this. So if you want to
> >be able to receive mail from all kinds of mailservers, don't use CNAME's
> >for MX's.
>
> No. It breaks a basic assumption set in stone in RFC821. It has
> nothing to do with mailer software.
May I point out that RFC 821 does not mention either CNAME or MX anywhere.
The successor (which is currently finished and waiting for publication as
RFC 2821) mentions both, but does not say if MX->CNAME is allowed or
forbidden. (And it says it's tightened up from RFC 974.)
Incidentally, it's also silent on the name vs. address MX question.
Looking at 974 and RFCs referenced from there might help to find
ammunition. But note that this is significantly later than 821.
So don't tell us about stuff set in stone in RFC XYZ, when it's plain
you've never looked at that RFC.
MfG Kai
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://vger.kernel.org/lkml/
next prev parent reply other threads:[~2001-02-12 21:49 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-08 13:06 DNS goofups galore Matti Aarnio
2001-02-08 13:35 ` Mr. James W. Laferriere
2001-02-08 17:43 ` Henning P. Schmiedehausen
2001-02-08 21:46 ` Gerhard Mack
2001-02-08 22:58 ` H. Peter Anvin
2001-02-08 23:32 ` Michael H. Warfield
2001-02-08 23:47 ` H. Peter Anvin
2001-02-08 23:54 ` Michael H. Warfield
2001-02-09 0:01 ` H. Peter Anvin
2001-02-09 0:08 ` Michael H. Warfield
2001-02-09 0:11 ` H. Peter Anvin
2001-02-09 0:31 ` Michael H. Warfield
2001-02-09 0:43 ` Johannes Erdfelt
2001-02-12 12:55 ` Henning P. Schmiedehausen
2001-02-12 19:19 ` James Antill
2001-02-13 19:52 ` Henning P. Schmiedehausen
2001-02-20 23:45 ` James Antill
2001-02-09 7:04 ` Jan Gyselinck
2001-02-12 12:57 ` Henning P. Schmiedehausen
2001-02-12 20:20 ` Kai Henningsen [this message]
2001-02-13 20:39 ` Henning P. Schmiedehausen
[not found] <linux.kernel.20010208193120.C1640@alcove.wittsend.com>
2001-02-09 1:50 ` Aaron Denney
2001-02-09 3:05 ` Michael H. Warfield
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=7vh2HM81w-B@khms.westfalen.de \
--to=kaih@khms.westfalen.de \
--cc=linux-kernel@vger.kernel.org \
/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