469,609 Members | 1,376 Online
Bytes | Developer Community
New Post

Home Posts Topics Members FAQ

Post your question to a community of 469,609 developers. It's quick & easy.

NNTP Login

Hi,

I am working on an NNTP Client via windows forms and am actually try
to login into this group to no avail. I am sending

AUTHINFO USER username <where username=myemail address
AUTHINFO PASS password <where password=my groups.google password

Any suggestions, what am i doing wrong. I keep getting 502 permission
denied.

Sep 22 '07 #1
3 2489
Posting from outlook express...

"Alexander Higgins" <al************@hotmail.comwrote in message
news:11**********************@57g2000hsv.googlegro ups.com...
Hi,

I am working on an NNTP Client via windows forms and am actually try
to login into this group to no avail. I am sending

AUTHINFO USER username <where username=myemail address
AUTHINFO PASS password <where password=my groups.google password

Any suggestions, what am i doing wrong. I keep getting 502 permission
denied.

Sep 22 '07 #2
The microsoft news server does not require a password to be sent to login to it.
Why don't you login directly to the Microsoft news server ( msnews.microsoft.com ) ?

Just create an account for msnews.microsoft.com in Outlook Express...and login.
I wouldn't include a real email address, though.

Either garble it a bit...or use a fake one.


Juan T. Llibre, asp.net MVP
asp.net faq : http://asp.net.do/faq/
foros de asp.net, en español : http://asp.net.do/foros/
======================================
"Alexander Higgins" <Al************@hotmail.comwrote in message news:e0**************@TK2MSFTNGP03.phx.gbl...
Posting from outlook express...

"Alexander Higgins" <al************@hotmail.comwrote in message
news:11**********************@57g2000hsv.googlegro ups.com...
>Hi,

I am working on an NNTP Client via windows forms and am actually try
to login into this group to no avail. I am sending

AUTHINFO USER username <where username=myemail address
AUTHINFO PASS password <where password=my groups.google password

Any suggestions, what am i doing wrong. I keep getting 502 permission
denied.


Sep 22 '07 #3
Thanks for the reply.

Here's a little background. I am building a VB.NET News Reader and can
successfully list news groups, and messages in each newsgroup. A response
from the server for a posted message will look like below.

I am trying to display the posts in a thread, much like you see in outlook
or any other news reader. There References Header seems to be the only
thing that relates the post to one another. I was trying to use the check
command which requires authentication, to look up the corresponding
crossposts. It seems that the only way I can cross reference the post is to
do this:

Query the news server for a list of posts in a group, and then use the HXDR
command to gets the message-id for every post. Once I have the headers, I
need to loop through all the headers and match the reference ID to the
Article ID. Once I have the Article ID for each referenced post I can then
lookup each post listed in the references header. This seems like a pain
with lots of uneccesary communication between the client and the server.
Does anyone know of an easier way to do this?

Client: group microsoft.public.dotnet.framework.aspnet
Server: 211 11566 471296 483110 microsoft.public.dotnet.framework.aspnet
Client: Article 483080
Server:
220 483080 <OG**************@TK2MSFTNGP04.phx.gbl>
From: "Juan T. Llibre" <no***********@nowhere.com>
References: <11**********************@57g2000hsv.googlegroups. com>
<e0**************@TK2MSFTNGP03.phx.gbl>
Subject: Re: NNTP Login
Date: Sat, 22 Sep 2007 06:37:19 -0400
Lines: 35
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.3790.2725
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.4073
X-RFC2646: Format=Flowed; Response
Message-ID: <OG**************@TK2MSFTNGP04.phx.gbl>
Newsgroups: microsoft.public.dotnet.framework.aspnet
NNTP-Posting-Host: 123stb62.codetel.net.do 66.98.12.123
Path: TK2MSFTNGP01.phx.gbl!TK2MSFTNGP04.phx.gbl

The microsoft news server does not require a password to be sent to login to
it.
Why don't you login directly to the Microsoft news server (
msnews.microsoft.com ) ?

Just create an account for msnews.microsoft.com in Outlook Express...and
login.
I wouldn't include a real email address, though.

Either garble it a bit...or use a fake one.


Juan T. Llibre, asp.net MVP
asp.net faq : http://asp.net.do/faq/
foros de asp.net, en espa?ol : http://asp.net.do/foros/
======================================
"Alexander Higgins" <Al************@hotmail.comwrote in message
news:e0**************@TK2MSFTNGP03.phx.gbl...
Posting from outlook express...

"Alexander Higgins" <al************@hotmail.comwrote in message
news:11**********************@57g2000hsv.googlegro ups.com...
>Hi,

I am working on an NNTP Client via windows forms and am actually try
to login into this group to no avail. I am sending

AUTHINFO USER username <where username=myemail address
AUTHINFO PASS password <where password=my groups.google password

Any suggestions, what am i doing wrong. I keep getting 502 permission
denied.

Shortened for brevity, this will get the last one hundred headers, in
actuality you may have to query thousands of headers.
Client: xhdr message-id 483010-483110
221 Xhdr information follows
483010 <ut**************@TK2MSFTNGP04.phx.gbl>
483011 <#o**************@TK2MSFTNGP02.phx.gbl>
483012 <FE**********************************@microsoft.co m>
483013 <#O**************@TK2MSFTNGP05.phx.gbl>
483014 <#n**************@TK2MSFTNGP06.phx.gbl>
483015 <eh**************@TK2MSFTNGP06.phx.gbl>
483016 <OI**************@TK2MSFTNGP04.phx.gbl>
483017 <11*********************@50g2000hsm.googlegroups.c om>
483018 <#T**************@TK2MSFTNGP05.phx.gbl>
483019 <#7*************@TK2MSFTNGP05.phx.gbl>
483020 <OA*************@TK2MSFTNGP05.phx.gbl>
483021 <11**********************@57g2000hsv.googlegroups. com>
483022 <84**********************************@microsoft.co m>
483023 <eS**************@TK2MSFTNGP05.phx.gbl>
483024 <#j**************@TK2MSFTNGP03.phx.gbl>
483025 <eG**************@TK2MSFTNGP06.phx.gbl>
483026 <u3**************@TK2MSFTNGP02.phx.gbl>
483027 <ep**************@TK2MSFTNGP02.phx.gbl>
483028 <%2********************@bignews6.bellsouth.net>
483029 <#d**************@TK2MSFTNGP03.phx.gbl>
483030 <11**********************@19g2000hsx.googlegroups. com>
483031 <Od**************@TK2MSFTNGP02.phx.gbl>
483032 <O2*************@TK2MSFTNGP06.phx.gbl>
483033 <ub*************@TK2MSFTNGP06.phx.gbl>
483034 <13*************@corp.supernews.com>
483035 <13*************@corp.supernews.com>
483036 <13*************@corp.supernews.com>
483037 <11*********************@22g2000hsm.googlegroups.c om>
483038 <11**********************@57g2000hsv.googlegroups. com>
483039 <AE**********************************@microsoft.co m>
483040 <11**********************@o80g2000hse.googlegroups .com>
483041 <11**********************@o80g2000hse.googlegroups .com>
483042 <11**********************@y42g2000hsy.googlegroups .com>
483043 <#2**************@TK2MSFTNGP02.phx.gbl>
483044 <11*********************@n39g2000hsh.googlegroups. com>
483045 <73**********************************@microsoft.co m>
483046 <7895594e80f1a@uwe>
483047 <up**************@TK2MSFTNGP06.phx.gbl>
483048 <29**********************************@microsoft.co m>
483049 <84**********************************@microsoft.co m>
483050 <11**********************@w3g2000hsg.googlegroups. com>
483051 <OU**************@TK2MSFTNGP05.phx.gbl>
483052 <OP**************@TK2MSFTNGP06.phx.gbl>
483053 <#b**************@TK2MSFTNGP02.phx.gbl>
483054 <14**********************************@microsoft.co m>
483055 <D6**********************************@microsoft.co m>
483056 <02**********************************@microsoft.co m>
483057 <ur**************@TK2MSFTNGP05.phx.gbl>
483058 <#Y*************@TK2MSFTNGP06.phx.gbl>
483059 <#P*************@TK2MSFTNGP06.phx.gbl>
483060 <wY3Ji.2142$Hv4.0@amstwist00>
483061 <O9**************@TK2MSFTNGP03.phx.gbl>
483062 <34**********************************@microsoft.co m>
483063 <11*********************@k79g2000hse.googlegroups. com>
483064 <#k*************@TK2MSFTNGP04.phx.gbl>
483065 <11**********************@n39g2000hsh.googlegroups .com>
483066 <OQ**************@TK2MSFTNGP06.phx.gbl>
483067 <11*********************@g4g2000hsf.googlegroups.c om>
483068 <Oy**************@TK2MSFTNGP04.phx.gbl>
483069 <11**********************@o80g2000hse.googlegroups .com>
483070 <#2**************@TK2MSFTNGP03.phx.gbl>
483071 <#v**************@TK2MSFTNGP03.phx.gbl>
483072 <3d*************************@msnews.microsoft.co m>
483073 <3d*************************@msnews.microsoft.co m>
483074 <11**********************@57g2000hsv.googlegroups. com>
483075 <e0**************@TK2MSFTNGP03.phx.gbl>
483076 <ut**************@TK2MSFTNGP05.phx.gbl>
483077 <#Z**************@TK2MSFTNGP02.phx.gbl>
483078 <OC**************@TK2MSFTNGP05.phx.gbl>
483079 <uH**************@TK2MSFTNGP04.phx.gbl>
483080 <OG**************@TK2MSFTNGP04.phx.gbl>
483081 <Ov**************@TK2MSFTNGP04.phx.gbl>
483082 <eT**************@TK2MSFTNGP04.phx.gbl>
483083 <eN**************@TK2MSFTNGP02.phx.gbl>
483084 <#N**************@TK2MSFTNGP05.phx.gbl>
483085 <Ou**************@TK2MSFTNGP03.phx.gbl>
483086 <#S**************@TK2MSFTNGP03.phx.gbl>
483087 <uN**************@TK2MSFTNGP02.phx.gbl>
483088 <11**********************@k79g2000hse.googlegroups .com>
483089 <eE**************@TK2MSFTNGP06.phx.gbl>
483090 <O5**************@TK2MSFTNGP02.phx.gbl>
483091 <11**********************@y42g2000hsy.googlegroups .com>
483092 <3d*************************@msnews.microsoft.co m>
483093 <OZ**************@TK2MSFTNGP02.phx.gbl>
483094 <uL**************@TK2MSFTNGP03.phx.gbl>
483095 <eH**************@TK2MSFTNGP02.phx.gbl>
483096 <13*************@corp.supernews.com>
483097 <94**********************************@microsoft.co m>
483098 <uW**************@TK2MSFTNGP06.phx.gbl>
483099 <#L**************@TK2MSFTNGP05.phx.gbl>
483100 <11**********************@k79g2000hse.googlegroups .com>
483101 <Oa*************@TK2MSFTNGP06.phx.gbl>
483102 <F1**********************************@microsoft.co m>
483103 <30**********************************@microsoft.co m>
483104 <Ow**************@TK2MSFTNGP03.phx.gbl>
483105 <11**********************@r29g2000hsg.googlegroups .com>
483106 <95**********************************@microsoft.co m>
483107 <1A**********************************@microsoft.co m>
483108 <9F**********************************@microsoft.co m>
483109 <11**********************@n39g2000hsh.googlegroups .com>
483110 <#d**************@TK2MSFTNGP03.phx.gbl>

Now that I have the message-id of the last 100 posts, loolp through each
until I find the reference id's

Dim References() as string = new string()
{"<11**********************@57g2000hsv.googlegroup s.com>",
"<e0**************@TK2MSFTNGP03.phx.gbl>"}

for I as integer = 0 to ubound(split(XHDR, vbnewline))
for j as integer = 0 to ubound(references)
if split(XHDR, vbnewline)(i).split(" ")(1) = referenences(j) then
References(j) = split(XHDR, vbnewline)(i).split(" ")(0)
next
next
return references

Now There references *should* contain the corrersponding articleID
' References(0) = 483074 References(1) = 483075
For I as integer =0 to ubound(references)
Dim article as string = GetArticle(references(i)
next

Function GetArticle(byval ArticleID as integer)
NNTP.Query("Article " & articleID & environment.newline)
End function

Client: Article 483075
Server: ----- Returns Articles similar to that above.
As you can see, there seems to be a lot of overhead head here going back and
forth. Is this how it needs to be done or is there a simpler way?

Sep 23 '07 #4

This discussion thread is closed

Replies have been disabled for this discussion.

Similar topics

2 posts views Thread by Rodney Pont | last post: by
4 posts views Thread by NightChild | last post: by
reply views Thread by Gene Mat | last post: by
8 posts views Thread by Roland Hall | last post: by
12 posts views Thread by Craig Kenisston | last post: by
11 posts views Thread by Jim | last post: by
9 posts views Thread by Sandman | last post: by
11 posts views Thread by Michael Torrie | last post: by
By using this site, you agree to our Privacy Policy and Terms of Use.