Re: Why is an eMail to karl@202.34.123.45 not possible ?
- From: "Brian Tillman" <tillman1952@xxxxxxxxx>
- Date: Thu, 21 Dec 2006 10:26:29 -0500
Tim Tuples <titu@xxxxxxxxx> wrote:
We have a deidcated server with a fixed IP (e.g =202.34.123.45)
and a running mail server but NO domain associated with it.
I tried to send several times from serveral mail accounts from all
over the world emails to an eMail account on this server (e.g. to
karl@xxxxxxxxxxxxx). Unfortunately this doens't work.
The SMTP mail delivery system seems to need a domain name and NOT an
IP. Why?
According to RFC 2821, the format of the address you're using is almost acceptable to SMTP mail agents. Here's a quote:
4.1.3 Address Literals
Sometimes a host is not known to the domain name system and
communication (and, in particular, communication to report and repair
the error) is blocked. To bypass this barrier a special literal form
of the address is allowed as an alternative to a domain name. For
IPv4 addresses, this form uses four small decimal integers separated
by dots and enclosed by brackets such as [123.255.37.2], which
indicates an (IPv4) Internet Address in sequence-of-octets form. For
IPv6 and other forms of addressing that might eventually be
standardized, the form consists of a standardized "tag" that
identifies the address syntax, a colon, and the address itself, in a
format specified as part of the IPv6 standards [17].
So, the RFC for SMTP mail dictates that you should be able to specify karl@[202.34.123.45]. However, Outlook doesn't like that. When I tried it without the brackets, Outlook accepted the address, but the message never arrived. Apparently, Outlook is not a standard-conforming mail program, but then, you knew that already.
--
Brian Tillman
.
- Prev by Date: Re: Need help with wireless settings for Westell 327W
- Next by Date: Re: Transmitting but Not Receiving Packets on NIC
- Previous by thread: Re: Why is an eMail to karl@202.34.123.45 not possible ?
- Next by thread: Unable to ftp
- Index(es):
Relevant Pages
|
