
	Where results make sense

Topic: Simple Mail Transfer Protocol

Related Topics

Simple Network Management Protocol

Telnet

Post Office Protocol

MIME

SMTP

Email

Datagram Congestion Control Protocol

Stream Control Transmission Protocol

Fiber distributed data interface

File Transfer Protocol

Telnet

POP3

DomainKeys

Application layer

TCPIP

	RFC 2821 (rfc2821) - Simple Mail Transfer Protocol
		SMTP clients that transfer all traffic, regardless of the target domain names associated with the individual messages, or that do not maintain queues for retrying message transmissions that initially cannot be completed, may otherwise conform to this specification but are not considered fully-capable.
		The SMTP protocol allows a server to formally reject a transaction while still allowing the initial connection as follows: a 554 response MAY be given in the initial connection opening message instead of the 220.
		SMTP clients that experience a connection close, reset, or other communications failure due to circumstances not under their control (in violation of the intent of this specification but sometimes unavoidable) SHOULD, to maintain the robustness of the mail system, treat the mail transaction as if a 451 response had been received and act accordingly.
	www.faqs.org /rfcs/rfc2821.html (18604 words)

	Simple Mail Transfer Protocol - Wikipedia, the free encyclopedia
		SMTP is a relatively simple, text-based protocol, where one or more recipients of a message are specified (and in most cases verified to exist) and then the message text is transferred.
		To determine the SMTP server for a given domain name, the MX (Mail eXchange) DNS record is used, falling back to a simple A record in the case of no MX (not all MTAs (Mail Transfer Agents) support fallback).
		RFC 2821 The Simple Mail Transfer Protocol (obsoletes RFC 821 aka STD 10, RFC 974, and RFC 1869)
	en.wikipedia.org /wiki/Simple_Mail_Transfer_Protocol (1373 words)

	[No title]
		SMTP replies are sent from the receiver-SMTP to the sender-SMTP in response to the commands.
		This command causes the mail data from this command to be appended to the mail data buffer.
		SMTP REPLIES Replies to SMTP commands are devised to ensure the synchronization of requests and actions in the process of mail transfer, and to guarantee that the sender-SMTP always knows the state of the receiver-SMTP.
	www.ietf.org /rfc/rfc0821.txt (11071 words)

	SMTP, Simple Mail Transfer Protocol (Site not responding. Last check: 2007-10-24)
		SMTP commands are ASCII strings terminated by a CRLF combination.
		The initial client and server roles are short-lived, as the point is to allow the intermittently-connected host to request mail held for it by a service provider.
		An MTA normally has a mail client component which processes the outgoing mail queues, attempting to send mail for particular domains, based on time or event (such as new mail being placed in the queue, or receipt of an ETRN command by the SMTP server component).
	www.networksorcery.com /enp/protocol/smtp.htm (572 words)

	SMTP (Simple Mail Transfer Protocol) - Glossary Entry - Mobile Phone Directory
		SMTP (Simple Mail Transfer Protocol) is the main protocol used to control the transfer of electronic mail (e-mail) messages on the Internet.
		SMTP is a TCP/IP protocol, and this specifies the format of the messages, and how servers and terminals are to interact.
		SMTP is usually employed only for the sending of the messages, with other protocols used to receive them - e.g.
	www.mobile-phone-directory.org /Glossary/S/SMTP.html (116 words)

	SIMPLE MAIL TRANSFER PROTOCOL
		Replies to SMTP commands are devised to ensure the synchronization of requests and actions in the process of mail transfer, and to guarantee that the sender-SMTP always knows the state of the receiver-SMTP.
		The SMTP transmission channel is a TCP connection established between the sender process port U and the receiver process port L. This single full duplex connection is used as the transmission channel.
		The SMTP transmission channel is established via NCP between the sender process socket U and receiver process socket L. The Initial Connection Protocol [5] is followed resulting in a pair of simplex connections.
	www.ostrosoft.com /vb/rfc/rfc821.html (10761 words)

	[No title]
		Fully-capable SMTP implementations, including the relays used by these less capable Klensin Standards Track [Page 5] RFC 2821 Simple Mail Transfer Protocol April 2001 ones, and their destinations, are expected to support all of the queuing, retrying, and alternate address functions discussed in this specification.
		If accepted, the SMTP server returns a 354 Intermediate reply and considers all succeeding lines up to but not including the end of mail data indicator to be the message text.
		Klensin Standards Track [Page 22] RFC 2821 Simple Mail Transfer Protocol April 2001 There may be circumstances where an address appears to be valid but cannot reasonably be verified in real time, particularly when a server is acting as a mail exchanger for another server or domain.
	www.ietf.org /rfc/rfc2821.txt (18420 words)

	Related Documentation
		RFC 3461 Simple Mail Transfer Protocol (SMTP) Service Extension for Delivery Status Notifications (DSNs)
		RFC 555 Responses to critiques of the proposed mail protocol
		RFC 539 Thoughts on the mail protocol proposed in RFC 524
	www.hypermail.org /rfcs.html (2196 words)

	HTTP/1.1: References
		The Internet Gopher Protocol (a distributed document search and retrieval protocol)
		MIME (Multipurpose Internet Mail Extensions) Part Three: Message Header Extensions for Non-ASCII Text
		Network Time Protocol (Version 3) Specification, Implementation and Analysis
	www.w3.org /Protocols/rfc2616/rfc2616-sec17.html (345 words)

Try your search on: Qwika (all wikis)