From: "Henning P. Schmiedehausen" <hps@tanstaafl.de>
To: linux-kernel@vger.kernel.org
Subject: Re: DNS goofups galore...
Date: Tue, 13 Feb 2001 19:52:29 +0000 (UTC) [thread overview]
Message-ID: <96c39t$o1g$1@forge.intermeta.de> (raw)
In-Reply-To: <95ulrk$aik$1@forge.intermeta.de>, <nn4rxz7lqy.fsf@code.and.org>
james@and.org (James Antill) writes:
>"Henning P. Schmiedehausen" <hps@tanstaafl.de> writes:
>> % telnet mail.bar.org smtp
>> 220 mail.foo.org ESMTP ready
>> ^^^^^^^^^^^^
>>
>> This kills loop detection. Yes, it is done this way =%-) and it breaks
>> if done wrong.
> This is humour, yeh ?
No.
> I would be supprised if even sendmail assumed braindamage like the
>above.
> For instance something that is pretty common is...
>foo.example.com. IN A 4.4.4.4
>foo.example.com. IN MX 10 mail.example.com.
>foo.example.com. IN MX 20 backup-mx1.example.com.
>; This is really mail.example.org.
>backup-mx1.example.com. IN A 1.2.3.4
No. This is a misconfiguration. Yes, RFC821 is a bit rusty but as far
as I know, nothing has superseded it yet. And Section 3.7 states
clearly:
Whenever domain names are used in SMTP only the official names are
used, the use of nicknames or aliases is not allowed.
And the 220 Message is defined as
220 <domain>
On sendmail, this is enforced by the "k" flag in the mailer definition.
>...another is to have "farms" of mail servers (the A record for the MX
>has multiple entries).
> If it "broke" as you said, then a lot of mail wouldn't be being routed.
You're correct. A lot of mail isn't routed or just routed because the
mailers believe in the "be liberal in what you accept" policy. Or
plainly non-RFC-compliant.
There is a concept behind CNAMEs just like behind IP Fragmentation and
the NT domains. Noone stated that it is a _SANE_ concept but it is now
here and we have to live with it. CNAMES ARE NOT ALIASES.
A CNAME is a reference. It states "the canonical name of "xxxx" is
podunk.org". You write it as
xxx IN CNAME podunk.org.
SMTP requests that you use the canonical name in the 220 greeting,
according to RFC 821. Everything else is misconfiguration.
Regards
Henning
--
Dipl.-Inf. (Univ.) Henning P. Schmiedehausen -- Geschaeftsfuehrer
INTERMETA - Gesellschaft fuer Mehrwertdienste mbH hps@intermeta.de
Am Schwabachgrund 22 Fon.: 09131 / 50654-0 info@intermeta.de
D-91054 Buckenhof Fax.: 09131 / 50654-20
next prev parent reply other threads:[~2001-02-13 19:58 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 [this message]
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
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='96c39t$o1g$1@forge.intermeta.de' \
--to=hps@tanstaafl.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