usefor-article-11 June 2003

[< Prev] [TOC] [ Next >]
5.2.  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].
[< Prev] [TOC] [ Next >]
#Diff to first older
NewerOlder
usefor-usefor May 2005
usefor-usefor April 2005
usefor-usefor November 2004
usefor-usefor September 2004
News Article Format and Transmission May 2004
News Article Format and Transmission November 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-10/From.out          April 2003
+++ ../usefor-article-11/From.out          June 2003
@@ -1,36 +1,18 @@
 5.2.  From
 
    The From-header contains the email address(es), possibly including
-   the full name(s), of the article's poster(s). The content syntax
-   makes use of syntax defined in [RFC 2822].
+   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
 
-        Observe that there is no provision for parameters in this
+        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).
-
-   Each mailbox in the From-content SHOULD be a valid address, belonging
-   to the poster(s) of the article, or person or agent on whose behalf
-   the post is being sent (see the Sender-header, 6.2).  When, for
-   whatever reason, the poster does not wish to include such an address,
-   the From-content SHOULD then be an address which ends in the top
-   level domain of ".invalid" [RFC 2606].
-
-        NOTE: Since such addresses ending in ".invalid" are
-        undeliverable, user agents Ought to warn any user attempting to
-        reply to them and Ought Not, in any case, to attempt to deliver
-        to them (since that would be pointless anyway).  Whether or not
-        a valid address can subsequently be extracted from such an
-        address falls outside the scope of this standard (obviously,
-        posters wishing to disguise their address need to do more than
-        just add ".invalid" to it).
-
-        Be warned, however, that some injecting agents which are unable
-        to detect that the address belongs to the poster may choose to
-        insert a Sender-header (but see 8.2.2) or some entry in an
-        Injector-Info-header (6.19) which discloses some valid address
-        for the poster.
+        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].
 

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