Announcements and discussions for Gnus, the GNU Emacs Usenet newsreader
 help / color / mirror / Atom feed
From: Tassilo Horn <tassilo@member.fsf.org>
To: info-gnus-english@gnu.org
Subject: Re: fs-change-smtp and draft messages
Date: Tue, 14 Aug 2007 20:39:03 +0200	[thread overview]
Message-ID: <87fy2mhsfs.fsf@baldur.tsdh.de> (raw)
In-Reply-To: <m2r6m6vxom.fsf@cam.ac.uk>

Leo <sdl.web@gmail.com> writes:

Hi Leo,

> I am curious about how news posting work.

Via NNTP.

--8<---------------cut here---------------start------------->8---
RFC 977                                                    February 1986
Network News Transfer Protocol

3.10.  The POST command

3.10.1.  POST

   POST

   If posting is allowed, response code 340 is returned to indicate that
   the article to be posted should be sent. Response code 440 indicates
   that posting is prohibited for some installation-dependent reason.

   If posting is permitted, the article should be presented in the
   format specified by RFC850, and should include all required header
   lines. After the article's header and body have been completely sent
   by the client to the server, a further response code will be returned
   to indicate success or failure of the posting attempt.

   The text forming the header and body of the message to be posted
   should be sent by the client using the conventions for text received
   from the news server:  A single period (".") on a line indicates the
   end of the text, with lines starting with a period in the original
   text having that period doubled during transmission.

   No attempt shall be made by the server to filter characters, fold or
   limit lines, or otherwise process incoming text.  It is our intent
   that the server just pass the incoming message to be posted to the
   server installation's news posting software, which is separate from
   this specification.  See RFC850 for more details.

   Since most installations will want the client news program to allow
   the user to prepare his message using some sort of text editor, and
   transmit it to the server for posting only after it is composed, the
   client program should take note of the herald message that greeted it
   when the connection was first established. This message indicates
   whether postings from that client are permitted or not, and can be
   used to caution the user that his access is read-only if that is the
   case. This will prevent the user from wasting a good deal of time
   composing a message only to find posting of the message was denied.
   The method and determination of which clients and hosts may post is
   installation dependent and is not covered by this specification.
--8<---------------cut here---------------end--------------->8---

Bye,
Tassilo
-- 
People say that  if you play Microsoft CD's  backwards, you hear satanic
things,  but that's  nothing, because  if you  play them  forwards, they
install Windows.

  reply	other threads:[~2007-08-14 18:39 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-14 11:19 Hadron
2007-08-14 13:24 ` Tassilo Horn
     [not found] ` <mailman.4764.1187097864.32220.info-gnus-english@gnu.org>
2007-08-14 13:54   ` Hadron
2007-08-14 15:28     ` Slackrat
2007-08-14 15:14   ` Hadron
2007-08-14 15:39     ` Slackrat
2007-08-14 16:39     ` Tassilo Horn
2007-08-14 17:22       ` Leo
2007-08-14 18:39         ` Tassilo Horn [this message]
     [not found]     ` <mailman.4771.1187109611.32220.info-gnus-english@gnu.org>
2007-08-15  9:58       ` Hadron

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87fy2mhsfs.fsf@baldur.tsdh.de \
    --to=tassilo@member.fsf.org \
    --cc=info-gnus-english@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).