J
joeu2004
Please forgive this off-topic inquiry. I appreciate your indulgence
and your patience.
Can some tell me what MS Community Newsgroup or public
newsgroup (e.g. microsoft.public.*), if any, that I can post to
in order to get help or a knowledgable explanation about
missing articles that I posted to MS CN, or to confirm a
potential problem with MS CN?
I sent email to Customer Service. Either they are clueless,
or they treat everyone with a question as if they are novices.
I am far from that. In any case, Customer Service has been
no help so far.
I have searched the list of MS CNs and public newsgroups,
but I did not find one that seemed on-topic.
Alternatively, perhaps someone can offer some insight into
the problem.
I posted two responses using MS CN. Even as long as,
now, 29 hours later, the responses do not appear in MS
CN. However, the articles are visible in the corresponding
public newsgroup using Google Groups.
(The second posted response was an abridged version of
the first response -- an attempt to repost while at the same
time "correcting" a presumed problem with the original article.)
My question is: why aren't the articles visible using MS CN?
It is not a question of delay, first because other articles that
I posted later do appear in a timely manner in that MS CN,
and second because the "delay" has really been too long.
I suspect that the articles might have been too long. Does
MS CN have a limit on article size, be it lines or characters?
Alternatively, perhaps there is a problem with the article
records on the MS CN news server(s) -- that is, something
is out of sync. But honestly, I am not familiar enough with
NNTP and how news servers are implemented to speculate
further.
I could try reposting "the" article again, but breaking it into
two responses in the hopes of (a) bypassing any size limit,
and (b) "resyncing" with the news server. But having done
that once already (but not __drastically__ reducing the size),
I am relunctant to take another "shot in the dark" without
some knowledgable insight into the root cause of the problem
might be.
TIA.
and your patience.
Can some tell me what MS Community Newsgroup or public
newsgroup (e.g. microsoft.public.*), if any, that I can post to
in order to get help or a knowledgable explanation about
missing articles that I posted to MS CN, or to confirm a
potential problem with MS CN?
I sent email to Customer Service. Either they are clueless,
or they treat everyone with a question as if they are novices.
I am far from that. In any case, Customer Service has been
no help so far.
I have searched the list of MS CNs and public newsgroups,
but I did not find one that seemed on-topic.
Alternatively, perhaps someone can offer some insight into
the problem.
I posted two responses using MS CN. Even as long as,
now, 29 hours later, the responses do not appear in MS
CN. However, the articles are visible in the corresponding
public newsgroup using Google Groups.
(The second posted response was an abridged version of
the first response -- an attempt to repost while at the same
time "correcting" a presumed problem with the original article.)
My question is: why aren't the articles visible using MS CN?
It is not a question of delay, first because other articles that
I posted later do appear in a timely manner in that MS CN,
and second because the "delay" has really been too long.
I suspect that the articles might have been too long. Does
MS CN have a limit on article size, be it lines or characters?
Alternatively, perhaps there is a problem with the article
records on the MS CN news server(s) -- that is, something
is out of sync. But honestly, I am not familiar enough with
NNTP and how news servers are implemented to speculate
further.
I could try reposting "the" article again, but breaking it into
two responses in the hopes of (a) bypassing any size limit,
and (b) "resyncing" with the news server. But having done
that once already (but not __drastically__ reducing the size),
I am relunctant to take another "shot in the dark" without
some knowledgable insight into the root cause of the problem
might be.
TIA.