Driving a newbie nuts...
Steve@DS
While I've subscribed to a few groups for a while now, I'm new to
posting and I'm having difficulty understanding why some of my postings
are received and posted while others are not. This even happens on the
test site.
Can anyone please explain why that should be the case? Are there any
limitations of any kind?
Many thanks,
Steve.
--
====== Please DELETE This Line and Everything Below It When Replying! ====
THIS NEWSGROUP is only for questions about newsgroups and the Internet.
IF YOU HAVE questions on other topics, search for appropriate newsgroups
using http://members.fortunecity.com/nnqweb/ngroups.html
LEARN about newsgroups at the news.newusers.questions Web site:
http://members.fortunecity.com/nnqweb/
===== The moderators append this notice to non-crossposted articles; =====
======= It does not imply that the article is on topic or correct ========
Alan Connor
<nnq.427bc834$1...@mk-nntp-2.news.uk.tiscali.com>, "Steve@DS"
wrote:
> Hi, everyone.
>
> While I've subscribed to a few groups for a while now, I'm new
> to posting and I'm having difficulty understanding why some of
> my postings are received and posted while others are not. This
> even happens on the test site.
>
> Can anyone please explain why that should be the case? Are
> there any limitations of any kind?
>
> Many thanks, Steve.
>
>
It could be your From header.
Have you ever seen anyone on the Usenet with an "@" in their
name? (that wasn't part of a full email address).
I haven't, until now.
Newbies should be following the examples of others until
they learn the ropes, don't you think?
AC
Jon Bell
Steve@DS <date...@hotmail.co.uk> wrote:
>
>While I've subscribed to a few groups for a while now, I'm new to
>posting and I'm having difficulty understanding why some of my postings
>are received and posted while others are not. This even happens on the
>test site.
If you tell us which groups you've tried to post to, and approximately
when, someone can look and see whether the postings are on their servers.
If you've tried to post using other addresses than the one you've used
here, you'd better tell us what to look for.
Normally you should be able to see your own postings on your own server
(Tiscali) pretty quickly. You might have to tell your newsreading
software to show you all the postings in the group. Many newsreaders
automatically hide postings that you've read, on the assumption that you
don't want to see them again.
The only major exception that I can think of is with moderated groups. If
a group is moderated, your news server mails your postings to the
moderator(s), who then post them (if approved) on their server, whereupon
the postings have to propagate back to your server before you can see
them. If the moderators reject your postings, or if they never receive
them at all because your server isn't configured properly, you won't see
them.
--
Jon Bell <jtb...@presby.edu> Presbyterian College
Dept. of Physics and Computer Science Clinton, South Carolina USA
Rodger Whitlock
> On news.newusers.questions, in
> <nnq.427bc834$1...@mk-nntp-2.news.uk.tiscali.com>, "Steve@DS"
> wrote:
> > While I've subscribed to a few groups for a while now, I'm new
> > to posting and I'm having difficulty understanding why some of
> > my postings are received and posted while others are not. This
> > even happens on the test site.
> >
> > Can anyone please explain why that should be the case? Are
> > there any limitations of any kind?
> It could be your From header.
>
> Have you ever seen anyone on the Usenet with an "@" in their
> name? (that wasn't part of a full email address).
>
> I haven't, until now.
>
> Newbies should be following the examples of others until
> they learn the ropes, don't you think?
It's possible that the handle "Steve@DS" violates the RFC for such
things. In that case, the news client and/or NNTP server Steve@DS uses
aren't enforcing the RFC -- but this might be a venial sin. Once that
embedded @ leaks out into the wide world, it causes all sorts of
interesting malfunctions.
But whether permitted by the RFC or not, I can well believe that a
handle with an embedded "@" will cause lots of software to fall over.
--
Rodger Whitlock
Victoria, BC, Canada
to send email, change atlantic to pacific
and invalid to net
Alan Connor
<nnq.427d092...@news.newsguy.com>, "Rodger Whitlock"
wrote:
I see a lot of really screwed-up From: headers. Like those with
non-printing characters in them.
And most of them I check out at:
http://groups.google.com/advanced_group_search
don't have any posting history, yet the posters are obviously
very familiar with the Usenet.
Sadly, the Usenet is being destroyed by ignorant children
with their mommy's computers, which is what most trolls
are. They are nothing more than vandals, really.
The best groups are all retreating to mailing-lists and
private newsservers.
If newsadmins don't start requiring posters to use the same alias
every time they post, so that killfiles will actually work, the
Usenet is dead.
A very bummed out,
AC
Dr.Ruud
> It's possible that the handle "Steve@DS" violates the RFC for such
> things.
The term "violates" is a bit strong.
From RFC 1036:
<quote>
the three permissible forms are:
From: ma...@cbosgd.ATT.COM
From: ma...@cbosgd.ATT.COM (Mark Horton)
From: Mark Horton <ma...@cbosgd.ATT.COM>
Full names may contain any printing ASCII characters from space
through tilde, except that they may not contain "(" (left
parenthesis), ")" (right parenthesis), "<" (left angle bracket), or
">" (right angle bracket). Additional restrictions may be placed on
full names by the mail standard, in particular, the characters ","
(comma), ":" (colon), "@" (at), "!" (bang), "/" (slash), "="
(equal), and ";" (semicolon) are inadvisable in full names.
</quote>
So the '@' is one of the inadvisable characters inside a full name.
By the mail standard. Adn may be. And the role of the enclosing ""
is not mentioned here. But inadvisable it is.
--
Affijn, Ruud
Rodger Whitlock
wrote:
Does "full name" refer to the "Mark Horton" or to the "mark" preceding
the @? The RFC should define this a little earlier on, but perhaps you
can save us the trouble of looking it up ourselves.