usefor-usefor-01 September 2004

[< Prev] [TOC] [ Next >]
3.1.1  From

   The From header is the same as that specified in Section 3.6.2 of
   [RFC2822] with the added restrictions detailed in Section 2.2.
[< Prev] [TOC] [ Next >]
#Diff to first older
NewerOlder
usefor-usefor May 2005
usefor-usefor April 2005
usefor-usefor November 2004
News Article Format and Transmission May 2004
News Article Format and Transmission November 2003
News Article Format June 2003
News Article Format April 2003
News Article Format February 2003
News Article Format August 2002
News Article Format May 2002
News Article Format November 2001
News Article Format July 2001
News Article Format April 2001
News Article Format February 2000
Son of 1036 June 1994
RFC 1036 December 1987

--- ../usefor-article-13/From.out          May 2004
+++ ../usefor-usefor-01/From.out          September 2004
@@ -1,18 +1,5 @@
-5.2.  From
+3.1.1  From
 
-   The From-header contains the email address(es), possibly including
-   the full name(s), of the article's poster(s), or of the person or
-   agent on whose behalf the article is posted (see the Sender-header,
-   6.2).  The content syntax makes use of syntax defined in [RFC 2822].
-
-      header              =/ From-header
-      From-header         = "From" ":" SP From-content
-      From-content        = mailbox-list
-
-        NOTE: Observe that there is no provision for parameters in this
-        header, or in other headers containing addresses likely to be
-        used for sending email (see 4.2.2).  When, for whatever reason,
-        a poster does not wish to use a valid address, the mailbox
-        concerned SHOULD end in the top level domain ".invalid" [RFC
-        2606].
+   The From header is the same as that specified in Section 3.6.2 of
+   [RFC2822] with the added restrictions detailed in Section 2.2.
 

Documents were processed to this format by Forrest J. Cavalier III