WTH....This message is no longer available.......?


A

Allen Drake

I get this occasionally when I try to read posts. Why would posts be
no longer available? I tried to find this one in Google but still
nothing.

Al.
----------------------------------------------------------------

Subject: Re: Changing MB and CPU W7
From: Allen Drake <[email protected]>
Date: Sun, 08 Jan 2012 05:53:59 -0500
Lines: 117

[Sorry. This message is no longer available.]


Message-ID: <[email protected]>

nntp://news60.forteinc.com/alt.windows7.general/65482

----------------------------------------------------------------
 
Ad

Advertisements

R

richard

I get this occasionally when I try to read posts. Why would posts be
no longer available? I tried to find this one in Google but still
nothing.

Al.
----------------------------------------------------------------

Subject: Re: Changing MB and CPU W7
From: Allen Drake <[email protected]>
Date: Sun, 08 Jan 2012 05:53:59 -0500
Lines: 117

[Sorry. This message is no longer available.]


Message-ID: <[email protected]>

nntp://news60.forteinc.com/alt.windows7.general/65482

----------------------------------------------------------------
hiccups.
Wait awhile and try it again.
It is there and available on my server.
 
B

BillW50

In
Allen said:
I get this occasionally when I try to read posts. Why would posts be
no longer available? I tried to find this one in Google but still
nothing.

Al.
----------------------------------------------------------------

Subject: Re: Changing MB and CPU W7
From: Allen Drake <[email protected]>
Date: Sun, 08 Jan 2012 05:53:59 -0500
Lines: 117

[Sorry. This message is no longer available.]


Message-ID: <[email protected]>

nntp://news60.forteinc.com/alt.windows7.general/65482

----------------------------------------------------------------
I see it under eternal-september. I used to see errors like this before
the news server got an upgrade.
 
J

John Williamson

Allen said:
I get this occasionally when I try to read posts. Why would posts be
no longer available? I tried to find this one in Google but still
nothing.
Posts in news servers are normally only retained for a defined period.
Your server (Easynews, if I've read your headers right) retains posts on
text groups for 600 or 200 days, depending on how you access the group.

The post you quote is new, so:-

Another possibility is that your news reader is sending the wrong
message ID, or the ID is getting corrupted between your machine and the
server, and you're getting a message from the server saying there's no
such message. Alternatively, your news server may be overloaded, and if
this is the case, then re-trying may help.

In theory, it is possible for the original poster to delete a post, but
in 99.99% of cases, it doesn't work, as many servers don't honour delete
requests coming from outside.
 
A

Allen Drake

I get this occasionally when I try to read posts. Why would posts be
no longer available? I tried to find this one in Google but still
nothing.

Al.
----------------------------------------------------------------

Subject: Re: Changing MB and CPU W7
From: Allen Drake <[email protected]>
Date: Sun, 08 Jan 2012 05:53:59 -0500
Lines: 117

[Sorry. This message is no longer available.]


Message-ID: <[email protected]>

nntp://news60.forteinc.com/alt.windows7.general/65482

----------------------------------------------------------------
hiccups.
Wait awhile and try it again.
It is there and available on my server.
I have seen this far to many times and have no way to know if I am
able to receive posts from others or I am missing them. I also see new
posts that start in the middle of a discussion and begin with re: I am
afraid to flush everything and start by downloading all new headers as
I might miss something. I am trying to keep up with every post if I
can. I wonder if I should try another newsreader. I have always used
Agent. I wonder if others find some better then Agent(not the free
one).

Al.
 
A

Allen Drake

In
Allen said:
I get this occasionally when I try to read posts. Why would posts be
no longer available? I tried to find this one in Google but still
nothing.

Al.
----------------------------------------------------------------

Subject: Re: Changing MB and CPU W7
From: Allen Drake <[email protected]>
Date: Sun, 08 Jan 2012 05:53:59 -0500
Lines: 117

[Sorry. This message is no longer available.]


Message-ID: <[email protected]>

nntp://news60.forteinc.com/alt.windows7.general/65482

----------------------------------------------------------------
I see it under eternal-september. I used to see errors like this before
the news server got an upgrade.
I think from what I see in your sig that you use Outlook as a reader?
I used to use it and OE-Quote Fix when Comcast had groups. I liked the
colors that separated the posts. I am not sure if I can install that
with Win7.

Al.
 
Ad

Advertisements

A

Allen Drake

Posts in news servers are normally only retained for a defined period.
Your server (Easynews, if I've read your headers right) retains posts on
text groups for 600 or 200 days, depending on how you access the group.

The post you quote is new, so:-

Another possibility is that your news reader is sending the wrong
message ID, or the ID is getting corrupted between your machine and the
server, and you're getting a message from the server saying there's no
such message. Alternatively, your news server may be overloaded, and if
this is the case, then re-trying may help.

In theory, it is possible for the original poster to delete a post, but
in 99.99% of cases, it doesn't work, as many servers don't honour delete
requests coming from outside.

I believe I am using APN because they are much cheaper then EasyNews.
Maybe I should use a different account. This one only costs $2.95 per
month.

Al.
 
V

VanguardLH

Allen said:
I get this occasionally when I try to read posts. Why would posts be
no longer available? I tried to find this one in Google but still
nothing.

Al.
----------------------------------------------------------------

Subject: Re: Changing MB and CPU W7
From: Allen Drake <[email protected]>
Date: Sun, 08 Jan 2012 05:53:59 -0500
Lines: 117

[Sorry. This message is no longer available.]

Message-ID: <[email protected]>

nntp://news60.forteinc.com/alt.windows7.general/65482

----------------------------------------------------------------
Not a Windows 7 issue. To discuss news servers, visit the
alt.free.newsservers group (even if using a paid one since the community
there is more familiar than this one about operation of NNTP servers).

There are 2 databases, not 1, that have to get synchronized to each
other: overview database (headers) and articles database (bodies). Then
there are spooled articles that are lost if the server crashes without
flushing (updating the databases with the) spooled articles. Could be
the overview and articles databases are out of sync. Users (the ones
who submitted the posts) can cancel their own posts (if cancels are
honored by the server). You would have to ask your NNTP provider is
they honor cancels direct from their users or when syncing to their
peered NNTP servers. A cancel requests removal of the article. If the
article was posted with your same NNTP server, you can look in the
control.cancel newsgroup to see if the poster requested a cancel.
Syncing of the overview database is not immediate. Instead the sync
gets scheduled so you'll have to ask your NNTP server admin how often
they sync their overview and articles databases. Some only do it once
per day. Cancels are not the only cause for the overview and articles
databases to get out of sync. Spooled articles will get lost if the
NNTP server crashes; see http://www.eyrie.org/~eagle/faqs/inn.html,
section 4.4 as an example. I've seen some NNTP servers undergo
maintenance or upgrades and it takes a day or two before the full sync
and usually results from user complaints initiating the NNTP admin to
perform a pre-scheduled sync. If the Usenet provider is running an NNTP
server farm (especially someone like EasyNews who is a 3rd tier provider
contracting with Highwinds for NNTP service), there can be a delay
between [incremental] syncing of the NNTP servers.

All NNTP servers have a fixed amount of storage space. Despite the ever
increasing size of hard disks, any implementation using them will have a
fixed maximum storage capability. Plus there's the problem of bandwidth
to supply all those articles. Giganews has a retention of somewhere
around 5 years (for text groups; I don't know what it is for binary
groups but expect it to be far shorter). Google Groups can only go back
as far as Deja News archives went back and, I think, that was back to
1982 (although Google has become pretty bad in the last 3 years so
expect to discover a lot of missing articles, or articles so impossible
to find even if they are recorded that you won't find them using
Google's inadequate search algorithms). EasyNews, your Usenet provider,
probably has whatever Highwinds has for retention of articles. When an
article gets expired, you cannot retrieve it anymore. However, as noted
above, it can be several hours before the overview database gets
synchronized to the articles database, so your newsreader can find the
headers (from the overview database) for the expired article but cannot
retrieve the body (from the articles database). From a quick glance at
the EasyNews web site, retention is 1200 days (212 days if you use their
webnews-for-boobs interface). I think that's malarky. Highwinds, the
Usenet backbone provider they use and who is really providing the Usenet
service, has a retention of 1080+ days but only the last 500 days are
available in the header index (overview database). That means your
newsreader can only get the last 500 days of headers and not the 1080+
days that are retained on the server.

How often is "occasionally"? Does the error disappear after a day?
You'll have to ask your Usenet provider how often they sync their
overview and articles databases. It's a batch update to get the
overview database in sync to the articles database after cancels have
changed the articles database. Because of the overhead involved and
impact to the server, and because most NNTP servers don't honor cancels,
the batch op doesn't get run immediately on every articles database
update or even every hour but something like 4 or 24 hours. It's all up
to the NNTP admin how update they run a batch update to ensure the
overview database (just the headers for fast access by the majority of
accesses) is synchronized to the articles database. I don't remember
which but when I asked one NNTP admin about this he said that the batch
sync gets run once per day. EasyNews has no control over when the sync
occurs because they are a 3rd tier Usenet provider contracting with
Highwinds for the Usenet backbone service.

One possible reason why the Google Groups search failed is if the poster
used the "X-No-Archive: Yes" header (or put it in the first line of
their body), the article gets deleted after an indeterminate amount of
time *if* the NNTP server honors the request. Google expires articles
with this header that are over 6 days old. Other NNTP servers that may
honor this header (they are rare) can specify any expiration period they
want. Since this is rude behavior by the poster to punch holes in a
thread, my expiration is 0 days (i.e., immediate deletion). Hey, the
poster declared their message had no value for it to stick around but
they don't get to configure anyone's NNTP server or client as to the
expiration period. They want others to honor their cancel request to
delete their self-proclaimed worthless article so I oblige and expire
immediately. The header only requests that their article be removed.
It doesn't state when their article gets removed.

It's also possible your NNTP client's message store is corrupted. You
would have to reset the newsgroup or unsubscribe, clear any remnant, and
resubscribe to recollect all the article headers. How the reset or
fresh subscribe gets done depends on the NNTP client. However, the
message you described is probably issued by the NNTP server, not by your
NNTP client although a log might show from where the error originated.
Folks over in the Forte newsgroup might better know how that NNTP client
works (alt.usenet.offline-reader.forte-agent), like using a debug log,
since this is not an issue with any version of Windows.

You won't find a search result hunting for articles in Google Groups for
this newsgroup. Google doesn't index the alt.windows7.general group.
See the result from http://groups.google.com/group/alt.windows7.general
or go to http://groups.google.com/ and enter "alt.windows7.general" in
the "Search for a group" textbox. If the article was cross-posted to
another group then you can find the article (in another newsgroup) but
not if it was posted only to this newsgroup.
 
J

John Williamson

Allen said:
I believe I am using APN because they are much cheaper then EasyNews.
Maybe I should use a different account. This one only costs $2.95 per
month.
I've no idea how the Easynews bit got into your headers, then.

But *only* $2.95 a month for newsgroup access? I use
news.individual.net, which is 10 Euros (About thirteen Bucks) per year.
Eternal September is free, as are a number of others. NIN and E-S have a
very good record of not missing posts and excellent uptime and
propogation, and they both run software that gets rid of most of the
spam before you see it.

Unless you're wanting binary groups, $2.95 a month is, IMHO, expensive.
 
A

Allen Drake

Allen said:
I get this occasionally when I try to read posts. Why would posts be
no longer available? I tried to find this one in Google but still
nothing.

Al.
----------------------------------------------------------------

Subject: Re: Changing MB and CPU W7
From: Allen Drake <[email protected]>
Date: Sun, 08 Jan 2012 05:53:59 -0500
Lines: 117

[Sorry. This message is no longer available.]

Message-ID: <[email protected]>

nntp://news60.forteinc.com/alt.windows7.general/65482

----------------------------------------------------------------
Not a Windows 7 issue. To discuss news servers, visit the
alt.free.newsservers group (even if using a paid one since the community
there is more familiar than this one about operation of NNTP servers).

There are 2 databases, not 1, that have to get synchronized to each
other: overview database (headers) and articles database (bodies). Then
there are spooled articles that are lost if the server crashes without
flushing (updating the databases with the) spooled articles. Could be
the overview and articles databases are out of sync. Users (the ones
who submitted the posts) can cancel their own posts (if cancels are
honored by the server). You would have to ask your NNTP provider is
they honor cancels direct from their users or when syncing to their
peered NNTP servers. A cancel requests removal of the article. If the
article was posted with your same NNTP server, you can look in the
control.cancel newsgroup to see if the poster requested a cancel.
Syncing of the overview database is not immediate. Instead the sync
gets scheduled so you'll have to ask your NNTP server admin how often
they sync their overview and articles databases. Some only do it once
per day. Cancels are not the only cause for the overview and articles
databases to get out of sync. Spooled articles will get lost if the
NNTP server crashes; see http://www.eyrie.org/~eagle/faqs/inn.html,
section 4.4 as an example. I've seen some NNTP servers undergo
maintenance or upgrades and it takes a day or two before the full sync
and usually results from user complaints initiating the NNTP admin to
perform a pre-scheduled sync. If the Usenet provider is running an NNTP
server farm (especially someone like EasyNews who is a 3rd tier provider
contracting with Highwinds for NNTP service), there can be a delay
between [incremental] syncing of the NNTP servers.

All NNTP servers have a fixed amount of storage space. Despite the ever
increasing size of hard disks, any implementation using them will have a
fixed maximum storage capability. Plus there's the problem of bandwidth
to supply all those articles. Giganews has a retention of somewhere
around 5 years (for text groups; I don't know what it is for binary
groups but expect it to be far shorter). Google Groups can only go back
as far as Deja News archives went back and, I think, that was back to
1982 (although Google has become pretty bad in the last 3 years so
expect to discover a lot of missing articles, or articles so impossible
to find even if they are recorded that you won't find them using
Google's inadequate search algorithms). EasyNews, your Usenet provider,
probably has whatever Highwinds has for retention of articles. When an
article gets expired, you cannot retrieve it anymore. However, as noted
above, it can be several hours before the overview database gets
synchronized to the articles database, so your newsreader can find the
headers (from the overview database) for the expired article but cannot
retrieve the body (from the articles database). From a quick glance at
the EasyNews web site, retention is 1200 days (212 days if you use their
webnews-for-boobs interface). I think that's malarky. Highwinds, the
Usenet backbone provider they use and who is really providing the Usenet
service, has a retention of 1080+ days but only the last 500 days are
available in the header index (overview database). That means your
newsreader can only get the last 500 days of headers and not the 1080+
days that are retained on the server.

How often is "occasionally"? Does the error disappear after a day?

Well that sure is a lot of info. Thank you very much. I am now seeing
posts I just made today getting marked as no longer available. It
seems that checking on my posts would be a bit of trouble if I have to
re-read all the threads I posted to by looking in my send folder to
see if they are all there.



You'll have to ask your Usenet provider how often they sync their
overview and articles databases. It's a batch update to get the
overview database in sync to the articles database after cancels have
changed the articles database. Because of the overhead involved and
impact to the server, and because most NNTP servers don't honor cancels,
the batch op doesn't get run immediately on every articles database
update or even every hour but something like 4 or 24 hours. It's all up
to the NNTP admin how update they run a batch update to ensure the
overview database (just the headers for fast access by the majority of
accesses) is synchronized to the articles database. I don't remember
which but when I asked one NNTP admin about this he said that the batch
sync gets run once per day. EasyNews has no control over when the sync
occurs because they are a 3rd tier Usenet provider contracting with
Highwinds for the Usenet backbone service.
I don't think I use Easynews. I use APN. I get regular email from
EaasyNews to get me to go back to them. Maybe I will. It just seemed
like more then I needed. I don't go to binary groups and only read
this one and the hardware group. I'm lucky if I have time to keep up
with just the two.

One possible reason why the Google Groups search failed is if the poster
used the "X-No-Archive: Yes" header (or put it in the first line of
their body), the article gets deleted after an indeterminate amount of
time *if* the NNTP server honors the request. Google expires articles
with this header that are over 6 days old. Other NNTP servers that may
honor this header (they are rare) can specify any expiration period they
want. Since this is rude behavior by the poster to punch holes in a
thread, my expiration is 0 days (i.e., immediate deletion). Hey, the
poster declared their message had no value for it to stick around but
they don't get to configure anyone's NNTP server or client as to the
expiration period. They want others to honor their cancel request to
delete their self-proclaimed worthless article so I oblige and expire
immediately. The header only requests that their article be removed.
It doesn't state when their article gets removed.
I don't think I have that in my header although I will check. I don't
have it setup to see any of them.
It's also possible your NNTP client's message store is corrupted. You
would have to reset the newsgroup or unsubscribe, clear any remnant, and
resubscribe to recollect all the article headers. How the reset or
fresh subscribe gets done depends on the NNTP client. However, the
message you described is probably issued by the NNTP server, not by your
NNTP client although a log might show from where the error originated.
Folks over in the Forte newsgroup might better know how that NNTP client
works (alt.usenet.offline-reader.forte-agent), like using a debug log,
since this is not an issue with any version of Windows.
Thanks. I will visit that group and do some reading. I hate to
remove the account and reenter the settings if I would lose any posts.
You won't find a search result hunting for articles in Google Groups for
this newsgroup. Google doesn't index the alt.windows7.general group.
See the result from http://groups.google.com/group/alt.windows7.general
or go to http://groups.google.com/ and enter "alt.windows7.general" in
the "Search for a group" textbox. If the article was cross-posted to
another group then you can find the article (in another newsgroup) but
not if it was posted only to this newsgroup.
Well that sure explains a lot. Thanks again for this.

Al.
 
A

Allen Drake

I've no idea how the Easynews bit got into your headers, then.

But *only* $2.95 a month for newsgroup access? I use
news.individual.net, which is 10 Euros (About thirteen Bucks) per year.
Eternal September is free, as are a number of others. NIN and E-S have a
very good record of not missing posts and excellent uptime and
propogation, and they both run software that gets rid of most of the
spam before you see it.

Unless you're wanting binary groups, $2.95 a month is, IMHO, expensive.
I guess I should shop around or just go with the ones you suggested.
EasyNews is $9.95 a month.

http://www.newsgroupreviews.com/easynews-review.html
 
Ad

Advertisements

B

BillW50

In
Allen said:
I think from what I see in your sig that you use Outlook as a reader?
I used to use it and OE-Quote Fix when Comcast had groups. I liked the
colors that separated the posts. I am not sure if I can install that
with Win7.

Al.
Yes I am using OE6 and OE-QuoteFix currently. The only non-OE that I
heard will run OE-QuoteFix (with some tweaks) is Vista's Windows Mail.
And some have copied WM over to Windows 7. Another option is WLM
QuoteFix. But it isn't anything as good as OE-QuoteFix

Windows Live Mail QuoteFix
http://www.dusko-lolic.from.hr/wlmquote/
 
P

Paul

Allen said:
Well that sure explains a lot. Thanks again for this.

Al.
If you want to debug what is happening a bit, and are connected
to port 119 on a newsserver (unencrypted), you can use a packet
sniffer like Wireshark and watch what happens when you attempt
to read a posting. The transaction is pretty easy to follow.
It might give you more info to give your NSP (news provider).

Paul
 
V

VanguardLH

Allen said:
I don't think I use Easynews. I use APN. I get regular email from
EaasyNews to get me to go back to them. Maybe I will. It just seemed
like more then I needed. I don't go to binary groups and only read
this one and the hardware group. I'm lucky if I have time to keep up
with just the two.
From your headers:

Path: ...!voer-me.highwinds-media.com!news-in-01.newsfeed.easynews.com!easynews!core-easynews-01!easynews.com!en-nntp-09.dc1.easynews.com.POSTED!not-for-mail

Your posts are submitted to EasyNews (who uses Highwinds as their Usenet
backbone provider). If you are using APN then they are even farther
down the chain (4th tier). Any Usenet provider can sell off part of
their service to someone else, so Highwinds provides the worldwide mesh
network of NNTP servers (a Usenet backbone) that EasyNews contracts to
use and EasyNews sells off some of its service to APN.

At least EasyNews is honest about posts originating from them as they
show themself as the injection (first) node in the Path string. Each
NNTP server prepends itself to the existing Path value, so the first one
(that announces itself) is at the right-end of the string. APN doesn't
even identify themself. Apparently APN doesn't even bother to have
their own NNTP server or a separate one allocated to them at EasyNews
(or at Highwinds through EasyNews). APN just redirects to EasyNews.

You'll notice APN doesn't even identify themself in the X-Complaints-To
header. That shows EasyNews as the contact. So APN has absolutely no
real hardware. They're just reselling service they get directly from
EasyNews. Wow, what a non-service is APN. APN gets by being cheaper
because they don't have the full services that EasyNews has. APN just
has a portion of EasyNews' service. APN can be cheaper because they
only provide part of EasyNews' service (and EasyNews can sell their
service to many lower-tier Usenet providers).

So Forte has their Agent Premium News (APN), 3rd or 4th tier (or worse)
Usenet provider, that has no actual hardware resources and redirects all
submissions to EasyNews who is themself a 2nd/3rd tier Usenet provider
that contracts with Highwinds for their Usenet backbone service. A
basic account at EasyNews is $10/month but they're reselling their
bandwidth to lower-tier providers, like APN, who can then charge less
(because they are lesser provider). You have Highwinds selling their
service to those who resell [a portion] of their service who resell [a
portion] of their service and then you're down to APN.

Despite that APN is using EasyNews for their actual Usenet provider, APN
should still be inserting themself as the injection node in the Path
header along with identifying themself in the X-Complaints-To header.
However, since they aren't actually providing any real Usenet service
and simply having their customers use EasyNews then I can see why APN
[wrongly] doesn't identify themself.

As further proof that APN is a lower-tier provider using EasyNews for
their real Usenet service, do the following:

nslookup news20.forteinc.com

Notice right away that the alternate domain shown is:

forte.easynews.com

Then do a reverse lookup on the IP address:

nslookup 69.16.186.7

and again you see the host in on EasyNews' domain. Forte's APN service
has a host identified on EasyNews' domain. They may have admin
privileges on that EasyNews host to allow them to create, delete, and
maintain their accounts there (much like my ISP (Comcast) had a
Giganews-owned NNTP server that Comcast was allowed to [partially]
manage).

You might be paying Forte for their APN service. Despite APN never
properly identifying itself as the injection point for your submissions,
they are using EasyNews as the actual Usenet provider.
 
V

VanguardLH

Allen said:
I am now seeing posts I just made today getting marked as no longer
available. It seems that checking on my posts would be a bit of
trouble if I have to re-read all the threads I posted to by looking
in my send folder to see if they are all there.
Have you contacted APN regarding their Usenet service? Looks like
they're having database problems. Of course, they only have a web form
to submit inquiries and complaints which probably end up getting
redirected to EasyNews since that's the real Usenet provider.

http://www.forteinc.com/apn/contact.php
 
V

VanguardLH

John said:
I've no idea how the Easynews bit got into your headers, then.
Highwinds sells their Usenet backbone service to EasyNews who resells a
portion of their Usenet service to APN (Forte's Usenet service). APN
does not properly identifying itself by placing its own domain as the
injection node in the Path header or by identifying themself in the
X-Complaints-To header. You'd think they'd know better but for some
reason they hide.

APN really doesn't have a Usenet service. Instead they use EasyNews.
Do a lookup on Forte's NNTP server's hostname and you'll see its a host
at the EasyNews domain. Each lower-tiered reseller is selling their
service to customers and also to multiple even lower-tiered providers
(who can also resell their service). Each drop down the tier means a
lesser provider hence the lower cost: they're selling off the part they
contract with their upper-tier provider.
But *only* $2.95 a month for newsgroup access? I use
news.individual.net, which is 10 Euros (About thirteen Bucks) per year.
Eternal September is free, as are a number of others. NIN and E-S have a
very good record of not missing posts and excellent uptime and
propogation, and they both run software that gets rid of most of the
spam before you see it.

Unless you're wanting binary groups, $2.95 a month is, IMHO, expensive.
Another free Usenet provider is Albasani.net (the one that I now use).
I use to use Eternal-September but gave up during their equipment and
server migration (from Motzarella) and have stuck with Albasani since
although I still have an account with E-S to use as a backup.

I have been tempted to buy an annual account at individual.net (because
it's cheap) simply because Albasani, E-S, and other freebie servers tend
to go down a bit more than I care for. Not often but they do go down.
It is not a rare event. Considering that I'm not always connected to
their server (you only connect to retrieve or send, not to read what
you've already downloaded) and that there has been a number of times
during just those times of their server being unusable (i.e., they're
down only during those times I'm sampling their service), they do go
down more often than I ever recall when using Giganews (as my ISP's
contracted Usenet provider). Be interesting to know what the uptime (or
how often there is downtime) at the student-managed university-operated
individual.net server.
 
Ad

Advertisements

R

richard

I get this occasionally when I try to read posts. Why would posts be
no longer available? I tried to find this one in Google but still
nothing.

Al.
----------------------------------------------------------------

Subject: Re: Changing MB and CPU W7
From: Allen Drake <[email protected]>
Date: Sun, 08 Jan 2012 05:53:59 -0500
Lines: 117

[Sorry. This message is no longer available.]


Message-ID: <[email protected]>

nntp://news60.forteinc.com/alt.windows7.general/65482

----------------------------------------------------------------
hiccups.
Wait awhile and try it again.
It is there and available on my server.
I have seen this far to many times and have no way to know if I am
able to receive posts from others or I am missing them. I also see new
posts that start in the middle of a discussion and begin with re: I am
afraid to flush everything and start by downloading all new headers as
I might miss something. I am trying to keep up with every post if I
can. I wonder if I should try another newsreader. I have always used
Agent. I wonder if others find some better then Agent(not the free
one).

Al.
There are many reasons for seeing the "re:" and not the original thread
subject. Crossposting groups added by the responder, or the original thread
subject may have expired either in the server, or the client,. You may have
deleted the original thread subject.The original poster may have posted
using "X-no-Archive:yes", this causes the post to expire and be deleted on
the server in 7 days (if the server honors that request that is).

Every now and then I clean out the group. Deleting all of the threads, then
downloading a fresh set of headers.
 
R

richard

I believe I am using APN because they are much cheaper then EasyNews.
Maybe I should use a different account. This one only costs $2.95 per
month.

Al.
I tried APN for awhile and found they routinely missed full threads while
the full thread was available on newsguy. If you go with newsguy I think
you'll find it a better service.

www.newsguy.com
 
R

richard

I've no idea how the Easynews bit got into your headers, then.

But *only* $2.95 a month for newsgroup access? I use
news.individual.net, which is 10 Euros (About thirteen Bucks) per year.
Eternal September is free, as are a number of others. NIN and E-S have a
very good record of not missing posts and excellent uptime and
propogation, and they both run software that gets rid of most of the
spam before you see it.

Unless you're wanting binary groups, $2.95 a month is, IMHO, expensive.
Forte does not actually have their own servers. They rent from easynews.

Newsguy has a deal where if you want usenet service on your domain, all
they do is install a cgi script and you tap off of their servers. But they
don't tell your clients in the headers where the feed is originated from.
 
Ad

Advertisements

E

Evan Platt

There are many reasons for seeing the "re:" and not the original thread
subject.
"original thread subject?"

It's called the Original Post, bullis.
Crossposting groups added by the responder, or the original thread
subject may have expired either in the server, or the client,. You may have
deleted the original thread subject.The original poster may have posted
using "X-no-Archive:yes",
There's a space after: .
this causes the post to expire and be deleted on
the server in 7 days (if the server honors that request that is).
And about the only server that honors that is Google Groups.
Every now and then I clean out the group. Deleting all of the threads, then
downloading a fresh set of headers.
Why? Completely unnecessary.
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top