caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Eijiro Sumii <eijiro_sumii@anet.ne.jp>
To: caml-list@inria.fr
Cc: Francis.Dupont@enst-bretagne.fr, Xavier.Leroy@inria.fr,
	webmaster@brion.inria.fr
Subject: Re: webmaster@caml.inria.fr is not a "legal" mail address
Date: Thu, 31 Mar 2005 08:05:20 -0500 (EST)	[thread overview]
Message-ID: <20050331.080520.68550579.eijiro_sumii@anet.ne.jp> (raw)
In-Reply-To: <200503311221.j2VCLd4O067700@givry.rennes.enst-bretagne.fr>

From: Francis Dupont <Francis.Dupont@enst-bretagne.fr>
> => aliases (CNAME left parts) are legal in mail addresses.

But RFC 1123 says as below, for example...?  For more details, see
also

  http://www.exim.org/pipermail/exim-users/Week-of-Mon-20030203/049446.html

for instance.  In short, it does no "harm" in _most_ environments, but
affects many systems at least.  (I wonder what Dmitry meant by
"webmaster@caml.inria.fr is not routable"...)

----------------------------------------------------------------------
5.2.2  Canonicalization: RFC-821 Section 3.1

         The domain names that a Sender-SMTP sends in MAIL and RCPT
         commands MUST have been  "canonicalized," i.e., they must be
         fully-qualified principal names or domain literals, not
         nicknames or domain abbreviations.  A canonicalized name either
         identifies a host directly or is an MX name; it cannot be a
         CNAME.
----------------------------------------------------------------------

> => it rewrites it because it checkes it and gets the canonical name as
> a side effect, not because aliases are not legal...

As explained above, they were illegal in MAIL and RCPT commands of
SMTP, at least.  Of course, you could argue that bodies (From: and
To:) may be different from envelopes (MAIL and RCPT), though.

The bottom line is that it is still a bad practice to use aliases in
mail address domains for these reasons.  Instead, we can just use A
records in most cases.

> PS: alias is a DNS concept, SMTP requires valid names (aliases or canonical
> names) with a restriction in the character set (only digits, letters and
> the character "-" not in the first position) for labels (names are made up
> by labels separated by dots). Note that SMTP does not require the name
> exists...

Grrr...:-)

Best regards,

	Eijiro


  reply	other threads:[~2005-03-31 13:05 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-30 14:19 Still problems with the main ocaml web page Martin Sandin
2005-03-30 15:01 ` [Caml-list] " Yaron Minsky
2005-03-30 15:11 ` Christopher Campbell
2005-03-30 15:29 ` Xavier Leroy
2005-03-30 19:24   ` Dimitri Timofeev
2005-03-30 23:48     ` Marc Herbert
2005-03-30 20:30   ` Eijiro Sumii
2005-03-30 20:38     ` webmaster@caml.inria.fr is not a "legal" mail address (Re: [Caml-list] Re: Still problems with the main ocaml web page) Eijiro Sumii
2005-03-31 12:21       ` Francis Dupont
2005-03-31 13:05         ` Eijiro Sumii [this message]
2005-03-31 13:35           ` webmaster@caml.inria.fr is not a "legal" mail address Francis Dupont
2005-03-31 18:37             ` [OT] " Eijiro Sumii
2005-03-31 20:08               ` Eijiro Sumii

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=20050331.080520.68550579.eijiro_sumii@anet.ne.jp \
    --to=eijiro_sumii@anet.ne.jp \
    --cc=Francis.Dupont@enst-bretagne.fr \
    --cc=Xavier.Leroy@inria.fr \
    --cc=caml-list@inria.fr \
    --cc=webmaster@brion.inria.fr \
    /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).