 | | Re: NNTP interface broken?
|
|
(...) Ah, OK. I get the same thing by telnetting to port 119. Thanks. (...) OK, this group is correct. The last article number is 188, and there are 186 articles present, because 2 in this group were cancelled. (...) OK, this group is incorrect. The (...) (21 years ago, 27-May-03, to lugnet.admin.nntp)
|
| |
| | Re: NNTP interface broken?
|
|
Ok, it seems you just fix it. This is what I get now: GROUP lugnet.loc.it 211 13087 1 13106 lugnet.loc.it "estimated" < "last": OE is fine with it. Thanks. BTW: why is "estimated" <> "last" - "first"? -- Cheers Carlo LugNet #24 (21 years ago, 27-May-03, to lugnet.admin.nntp)
|
| |
| | Re: Problems with Outlook Express and LUGNet
|
|
Hello Todd, (...) fix (...) seems you just did it because now I don't have that error anymore. Thank you ;) Carsten (21 years ago, 27-May-03, to lugnet.admin.nntp)
|
| |
| | Re: Problems with Outlook Express and LUGNet
|
|
"Todd Lehman" <todd@lugnet.com> wrote in message news:HFK0u1.1Do7@lugnet.com... (...) would (...) and (...) matching (...) fix (...) What is wierd is that it isn't affecting all groups. For example, lugnet.admin.nntp works fine. I am having (...) (21 years ago, 27-May-03, to lugnet.admin.nntp)
|
| |
| | Re: NNTP interface broken?
|
|
"Todd Lehman" <todd@lugnet.com> wrote in message news:HFK07y.17Mo@lugnet.com... (...) It is just the NNTP part of the packets. I just did a trace with Ethereal, and this is what I get: GROUP lugnet.loc.eu 211 186 1 188 lugnet.loc.eu GROUP (...) (21 years ago, 27-May-03, to lugnet.admin.nntp)
|
