> firstname.lastname@example.org (James Antill) writes:
> >"Henning P. Schmiedehausen" <email@example.com> 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 ?
This was a comment on the "loop detection" claim.
[snip ... domain example]
> 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
> Whenever domain names are used in SMTP only the official names are
> used, the use of nicknames or aliases is not allowed.
_In_ SMTP, that doesn't say anything about MX records to me and even
if it does it's very old and needs to change.
> And the 220 Message is defined as
> 220 <domain>
So... you should have the reverse for the ip address after the
220. Which most people do (but not all, mainly due to there not being
[snip CNAME lesson]
The question was, why can't you use CNAMEs. You said 'because of loop
detection'. I said 'But that doesn't work anyway, because you can have
to names pointing at one machine without a CNAME record ... and that
needs to, and currently does, work'.
> Dipl.-Inf. (Univ.) Henning P. Schmiedehausen -- Geschaeftsfuehrer
> INTERMETA - Gesellschaft fuer Mehrwertdienste mbH firstname.lastname@example.org
Let me put it this way...
tanstaafl.de. IN MX 50 mail.hometree.net.
tanstaafl.de. IN MX 10 mail.intermeta.de.
intermeta.de. IN MX 50 mail.hometree.net.
intermeta.de. IN MX 10 mail.intermeta.de.
mail.hometree.net. IN A 220.127.116.11
mail.intermeta.de. IN A 18.104.22.168
22.214.171.124.in-addr.arpa. IN PTR limes.hometree.net.
126.96.36.199.in-addr.arpa. IN PTR babsi.intermeta.de.
-- # James Antill -- email@example.com :0: * ^From: .*james@and\.org /dev/null - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to firstname.lastname@example.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/