s-o-1036 June 1994

[< Prev] [TOC] [ Next >]
6.1. Followup-To

The Followup-To header contents specify  which  newsgroup(s)
followups should be posted to:

     Followup-To-content = Newsgroups-content / "poster"

The  syntax  is  the same as that of the Newsgroups content,
with the exception that the magic word "poster"  means  that
followups  should  be  mailed to the article's reply address
rather than posted.  In  the  absence  of  Followup-To,  the
default  newsgroup(s)  for a followup are those in the News-
groups header.

     NOTE: The way to request that followups be  mailed
     to  a specific address other than that in the From
     line is  to  supply  "Followup-To: poster"  and  a
     Reply-To header.  Putting a mailing address in the
     Followup-To  line  is  incorrect;  posting  agents
     should reject or rewrite such headers.

     NOTE:   There  is  no  syntax  for  "no  followups
     allowed"  because   "Followup-To: poster"   accom-
     plishes this effect without extra machinery.

Although it is generally desirable to limit followups to the
smallest reasonable set of newsgroups, especially  when  the
precursor was cross-posted widely, posting agents SHOULD not
supply a Followup-To header except at the poster's  explicit
request.

     NOTE: In particular, it is incorrect for the post-
     ing agent to assume that  followups  to  a  cross-
     posted  article  should  be  directed to the first
     newsgroup only.  Trimming the list  of  newsgroups

INTERNET DRAFT to be        NEWS                    sec. 6.1


     should  be  the poster's decision, not the posting
     agent's.  However, when an article is to be cross-
     posted  to  a considerable number of newsgroups, a
     posting agent might wish to SUGGEST to the  poster
     that followups go to a shorter list.
[< 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 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
RFC 1036 December 1987

--- ../rfc1036/Followup-To.out          December 1987
+++ ../s-o-1036/Followup-To.out          June 1994
@@ -1,11 +1,45 @@
-2.2.3.  Followup-To
+6.1. Followup-To
 
-    This line has the same format as "Newsgroups".  If present, follow-
-    up messages are to be posted to the newsgroup or newsgroups listed
-    here.  If this line is not present, follow-ups are posted to the
-    newsgroup or newsgroups listed in the "Newsgroups" line.
-
-    If the keyword poster is present, follow-up messages are not
-    permitted.  The message should be mailed to the submitter of the
-    message via mail.
+The Followup-To header contents specify  which  newsgroup(s)
+followups should be posted to:
+
+     Followup-To-content = Newsgroups-content / "poster"
+
+The  syntax  is  the same as that of the Newsgroups content,
+with the exception that the magic word "poster"  means  that
+followups  should  be  mailed to the article's reply address
+rather than posted.  In  the  absence  of  Followup-To,  the
+default  newsgroup(s)  for a followup are those in the News-
+groups header.
+
+     NOTE: The way to request that followups be  mailed
+     to  a specific address other than that in the From
+     line is  to  supply  "Followup-To: poster"  and  a
+     Reply-To header.  Putting a mailing address in the
+     Followup-To  line  is  incorrect;  posting  agents
+     should reject or rewrite such headers.
+
+     NOTE:   There  is  no  syntax  for  "no  followups
+     allowed"  because   "Followup-To: poster"   accom-
+     plishes this effect without extra machinery.
+
+Although it is generally desirable to limit followups to the
+smallest reasonable set of newsgroups, especially  when  the
+precursor was cross-posted widely, posting agents SHOULD not
+supply a Followup-To header except at the poster's  explicit
+request.
+
+     NOTE: In particular, it is incorrect for the post-
+     ing agent to assume that  followups  to  a  cross-
+     posted  article  should  be  directed to the first
+     newsgroup only.  Trimming the list  of  newsgroups
+
+INTERNET DRAFT to be        NEWS                    sec. 6.1
+
+
+     should  be  the poster's decision, not the posting
+     agent's.  However, when an article is to be cross-
+     posted  to  a considerable number of newsgroups, a
+     posting agent might wish to SUGGEST to the  poster
+     that followups go to a shorter list.
 

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