Topic
MX record
About: MX record is a research topic. Over the lifetime, 179 publications have been published within this topic receiving 7805 citations. The topic is also known as: MX record.
Papers published on a yearly basis
Papers
More filters
01 Nov 1987
TL;DR: This RFC is the revised specification of the protocol and format used in the implementation of the Domain Name System and it obsoletes RFC-883.
Abstract: This RFC is the revised specification of the protocol and format used
in the implementation of the Domain Name System. It obsoletes RFC-883.
This memo documents the details of the domain name client - server
communication.
1,904 citations
01 Nov 1987
TL;DR: This memo describes the domain style names and their used for host address look up and electronic mail forwarding and discusses the clients and servers in the domain name system and the protocol used between them.
Abstract: This RFC is the revised basic definition of The Domain Name System. It
obsoletes RFC-882. This memo describes the domain style names and
their used for host address look up and electronic mail forwarding. It
discusses the clients and servers in the domain name system and the
protocol used between them.
1,559 citations
01 Nov 1981
TL;DR: The objective of SMTP is to transfer mail reliably and efficiently and requires only a reliable ordered data stream channel.
Abstract: The objective of Simple Mail Transfer Protocol (SMTP) is to transfer
mail reliably and efficiently. SMTP is independent of the particular
transmission subsystem and requires only a reliable ordered data
stream channel. Obsoletes RFC 788, 780, and 772.
708 citations
01 Jun 1992
TL;DR: This document redefines the format ofmessage bodies to allow multi-part textual and non-textual message bodies to be represented and exchanged without loss of information.
Abstract: STD 11, RFC 822 defines a message representation protocol which specifies considerable detail about message headers, but which leaves the message content, or message body, as flat ASCII text. This document redefines the format of message bodies to allow multi-part textual and non-textual message bodies to be represented and exchanged without loss of information. This is based on earlier work documented in RFC 934 and STD 11, RFC 1049, but extends and revises that work. Because RFC 822 said so little about message bodies, this document is largely orthogonal to (rather than a revision of) RFC 822.
480 citations
13 Aug 1982
TL;DR: In this paper, the authors revises the specifications in RFC 733, in order to serve the needs of the larger and more complex ARPA Internet Some of RFC733's features failed to gain adequate acceptance In order to simplify the standard and the software that follows it, these features have been removed and a different addressing scheme is used, to handle the case of internetwork mail.
Abstract: This document revises the specifications in RFC 733, in order to serve
the needs of the larger and more complex ARPA Internet Some of RFC
733's features failed to gain adequate acceptance In order to
simplify the standard and the software that follows it, these features
have been removed A different addressing scheme is used, to handle
the case of internetwork mail; and the concept of re-transmission has
been introduced Obsoletes RFC 733, NIC 41952
463 citations