|
Copyright © 1990-2010 by Prof. Timo Salmi Last modified Wed 29-Dec-2010 08:40:56 |
|
The number one rule of cross-posting is that cross-posting should never be used indiscriminately. If you feel that it is necessary to cross-post, consider carefully your selection, and keep it down. Avoid cross-posting to groups that are branches of the same sub-hierarchy, that is don't cross-post to adjacent newsgroups.
What goes for newsgroup selection in general, also applies to cross-posting. Never cross-post to newsgroups which do not coincide with your subject.
There is one very important DON'T in cross-posting. Do not send the same message separately to different newsgroups, i.e. do not multi-post. If your posting indeed is necessary and relevant in more than one newsgroup, always use the cross-posting facility of the news (Newsgroups:). If you repeat a message separately in different newsgroups, the readers will have to see your posting many times over, and will get annoyed. Furthermore, the potential followups will fragment all over the different newsgroups and much of the cohesiveness and usefulness of the discussion will be lost. Thus, if you multi-post you have a good chance of justifiably ending up flamed or at least considered a nuisance that is best avoided in the future. Even worse, your site's administrators might get complaints about your multiple postings, if you persist.
I have heard that there are some newsreader programs that do not allow editing the headers. I can only suggest contacting your system manager or some other local guru about it. I have no further information on this unusual dilemma since on most news programs editing the headers is not a problem. Be careful, however, if you edit the headers. Learn their exact requirements. If you make mistakes, the posting may fail, and/or the followups to it by other users may fail because of your editing errors. For example
Newsgroups: comp.lang.pascal.borland,comp.os.msdos.programmer,
would result in an error in following up because of the trailing comma.
At the end of this page there are true examples of the full headers of crosspostings with followups redirected. The first one is what is seen in the sending phase of a message when using (this time) Pnews for posting a message. The second one is what is seen when reading a posting (this time) with the rn newsreader. What exactly is given and shown naturally depends on the programs used.
If you set the followups to a newsgroup that is not included in the original distribution, you may wish to consider including that newsgroup in your "Newsgroups:" header. That way the readers will better know what the posting is about. Of course, this also depends on the specific situation.
Some users put the word poster in there to redirect the potential replies directly to them by email. The problem with this method is that even if it should work, it is not guaranteed to do so. Some system configurations and newsreaders do not handle this correctly. For example I usually get a bounce if I reply to such a posting.
----------------------------------------------------------------------------
alt.msdos.batch #29973 (16 more)
Path: news.uwasa.fi!majakka.uwasa.fi!not-for-mail
From: ts(ät)uwasa.fi (Timo Salmi)
Newsgroups: alt.msdos.batch,comp.os.msdos.misc
Subject: ">>> READ FIRST: Frequently Asked Questions about MS-DOS batches <<<"
Followup-To: alt.msdos.batch
Date: 20 Apr 2000 11:59:01 +0300
Organization: University of Vaasa, Finland
Lines: 150
Expires: Fri, 28 Apr 2000 08:59:00 GMT
Message-ID: <ts0004200859.19117@majakka.uwasa.fi>
NNTP-Posting-Host: majakka.uwasa.fi
Mime-Version: 1.0
Content-Type: text/plain
Content-Transfer-Encoding: 8bit
X-Trace: haavi.uwasa.fi 956221182 20336 193.166.122.16 (20 Apr 2000 08:59:42 GMT)
X-Complaints-To: abuse(ät)uwasa.fi
NNTP-Posting-Date: 20 Apr 2000 08:59:42 GMT
Summary: An automatically posted, regular pointer
X-No-Archive: yes
X-Warning: Junk / bulk email will be auto-filtered, traced and reported
X-Password: Spam foiling, elm filter will first return a required email password
Xref: news.uwasa.fi alt.msdos.batch:29973 comp.os.msdos.misc:84203