Search results
Results from the WOW.Com Content Network
This is a list of Simple Mail Transfer Protocol (SMTP) response status codes. Status codes are issued by a server in response to a client's request made to the server. Unless otherwise stated, all status codes described here is part of the current SMTP standard, RFC 5321. The message phrases shown are typical, but any human-readable alternative ...
Email spoofing is the creation of email messages with a forged sender address. [1] The term applies to email purporting to be from an address which is not actually the sender's; mail sent in reply to that address may bounce or be delivered to an unrelated party whose identity has been faked.
A session may include zero or more SMTP transactions. An SMTP transaction consists of three command/reply sequences: MAIL command, to establish the return address, also called return-path, [24] reverse-path, [25] bounce address, mfrom, or envelope sender. RCPT command, to establish a recipient of the message. This command can be issued multiple ...
Optionally, users can set a different "reply-to" address for each "send as" address. [41] When using this feature, the address chosen will appear in the "From:" field of the message header. However, the SMTP envelope sender address will contain the name of the Gmail account used to send the message.
encoding of certain header fields (subject, sender's and recipient's names, sender's organization and reply-to name) and, optionally, body in a content-transfer encoding; encoding of non-ASCII characters in one of the Unicode transforms; negotiating the use of UTF-8 encoding in email addresses and reply codes
The envelope-from address is transmitted at the beginning of the SMTP dialog. If the server rejects the domain, the unauthorized client should receive a rejection message, and if that client was a relaying message transfer agent (MTA), a bounce message to the original envelope-from address may be generated.
But the mail header is a part of the mail data (SMTP command DATA), and MTAs typically don't look into the mail. They deal with the envelope, that includes the MAIL FROM address (a.k.a. Return-Path, Envelope-FROM, or "reverse path") but not, e.g., the RFC 2822-From in the mail header field From. These details are important for schemes like BATV.
A non-standard but widely used way to request return receipts is with the "Return-Receipt-To:" (RRT) field in the e-mail header, with the email return address specified. The first time a user opens an email message containing this field in the header, the client will typically prompt the user whether to send a return receipt.