Search the Archives

RFC 2822: There is no "To" field required in RFC2822 because the...

Reader comments:

Comment by Zygo Blaxell
Submitted on 9/19/2005
Related RFC: RFC 2822
Rating: Not yet rated	Rate this comment:
There is no "To" field required in RFC2822 because the destination is found in RFC2821 "RCPT TO:" commands.If this is causing you delivery problems, your implementation is broken. RFC2822 specifies message contents--transport is handled by some other protocol. Serious problems can occur if the transport addresses are confused with the headers of the mail message itself--in some cases these are intentionally different, as in mailing lists and mail sent to a secret list of recipients. Sometimes mailing lists are gatewayed onto non-Internet mail systems which can't distinguish between RFC2821 envelope addresses and RFC2822 header addresses, and cause mail loops as a result.Some non-email protocols (e.g. netnews and HTTP) use RFC822 or RFC2822 as a base, but there is sensible value for the "To" field in messages carried by these protocols.

FAQS.ORG makes no guarantees as to the accuracy of the posts. Each post is the personal opinion of the poster. These posts are not intended to substitute for medical, tax, legal, investment, accounting, or other professional advice. FAQS.ORG does not endorse any opinion or any product or service mentioned mentioned in these posts.

<< Back to: RFC 2822