Re: Usenet Filters Question
Ralph Fox
me/2 <nu...@127.0.0.1> wrote:
> I've been using Agent since the Version 1 days, upgrading as new
> versions came out and am now using Version 6.
>
> Something new that I noticed recently while still running Version 5 is
> that expired usenet filters are no longer being deleted after they
> expire. I hadn't checked my filter list is quite a while and when I
> checked it a month or so before Version 6 came out I found hundreds of
> primarily Kill filters still showing up in the filter list that had
> all expired. They all counted down to ZERO days in the checked off
> "Expire this filter after __ days" setting but the filters were not
> deleted like I seem to remember Agent doing in the past.
>
> After upgrading to Version 6 I checked and found the same thing to be
> happening. I then deleted the FILTERS.DAT and FILTERS.IDX files,
> started up the program and created a couple of test Kill filters. Sure
> enough the same thing happened. The filters counted down to ZERO days
> remaining but still appeared in the filter list. BTW, the same thing
> happens whether I set the filter to expire after X number of days or
> after X number of days of inactivity.
Curous. Here, expired filters do seem to be automatically deleted from the filters list.
> So, am I imagining things when I remeber that Agent used to delete
> expired filters as stated in the help files?
No, you are not imagining things.
> If it used to do that are
> there any ideas what to change to get that behavior back?
I don't yet know what makes it behave your way.
PS: If you are testing this by changing your system clock, make sure that Agrent
is off-line (Agent's status bar says "offline") before you change your system clock.
If you don't, it seems that Agent does not always realize that the date has changed
when you manually change it.
> Thanks,
> me/2
--
Regards
Ralph
sf
>So, am I imagining things when I remeber that Agent used to delete
>expired filters as stated in the help files?
2x seems to toss old filters. So far I haven't found what you've seen
to be true.
>If it used to do that are
>there any ideas what to change to get that behavior back?
No idea.
--
I love cooking with wine.
Sometimes I even put it in the food.
pyotr filipivich
2009 23:35:39 -0700 did write/type or cause to appear in
alt.usenet.offline-reader.forte-agent the following:
>On Wed, 09 Dec 2009 12:05:27 -0800, Garrapata <garr...@09.netcom.com>
>wrote:
>
>:>On Sun, 06 Dec 2009 20:51:01 -0700, me/2 <nu...@127.0.0.1> wrote:
>:>
>:>>Something new that I noticed recently while still running Version 5 is
>:>>that expired usenet filters are no longer being deleted after they
>:>>expire.
>:>
>:> I didn't check all of my filters but a month ago I copied the titles
>:>of a dozen that showed 0 days remaining. Today all but 1 were still
>:>there 10 still showed 0 days and 1 had evidently been triggered during
>:>the month, it showed 5 days remaining.
>:>I use a default priority of 600 and a scope of global
>
>At least it's not just me. :-)
>
>I did upgrade from V5 to V6 "over the top" but the symptoms never changed
>between the 2 versions. BTW, since I started with V1 I've always done "over
>the top" upgrades to Agent with no issues. In this case I had been using V5
>since it came out and only had this issue crop up a few months ago. I was
>running V5 on 32bit WinXP when the problem first started, Nothing changed
>with V5 when I did a clean install of 64bit Win7 and the problem did not go
>away when I upgraded Agent to V6.
>
>I'm hoping it may turn out to be as simple as the old problem many versions
>back where if the XPOST.DAT file got corrupted all sorts of wierd unrelated
>things would happen. The solution for that was just to delete the XPOST.DAT
>and let the file start rebuilding itself. Unfortunately Agent no longer uses
>that file. I did try deleting all DAT files I could find that appeared to
>ralate to the usenet filters. I then created a couple of test filters both
>with "expire after X number of days" and with "expire after X number of days
>of inactivity". In either case it still didn't work correctly.
>
Interesting.
I haven't upgraded, if I do it will be a while.
But the "undeleted but expired filters" comment at the top of this
not intrigued me. In a previous news reader (back in the dark ages of
a Unix shell account), expired filters didn't disappear, which meant I
could search for them, and reactivate the "useful ones".
Something I have on occasion wished for. Expired filters not just
disappearing. But then again, that also required user involvement in
clearing out the deadwood. Did I mention this was a Unix Shell
account?
pyotr
-
pyotr filipivich.
Just about the time you finally see light at the end of the tunnel,
you find out it's a Government Project to build more tunnel.
pyotr filipivich
2009 12:45:50 -0600 did write/type or cause to appear in
alt.usenet.offline-reader.forte-agent the following:
>me/2 <nu...@127.0.0.1> wrote:
>
>> I've been using Agent since the Version 1 days, upgrading as new
>> versions came out and am now using Version 6.
>>
>> that expired usenet filters are no longer being deleted after they
>> checked it a month or so before Version 6 came out I found hundreds of
>> primarily Kill filters still showing up in the filter list that had
>> all expired. They all counted down to ZERO days in the checked off
>> "Expire this filter after __ days" setting but the filters were not
>> deleted like I seem to remember Agent doing in the past.
>>
>> After upgrading to Version 6 I checked and found the same thing to be
>> happening. I then deleted the FILTERS.DAT and FILTERS.IDX files,
>> started up the program and created a couple of test Kill filters. Sure
>> enough the same thing happened. The filters counted down to ZERO days
>> remaining but still appeared in the filter list. BTW, the same thing
>> after X number of days of inactivity.
>>
>> there any ideas what to change to get that behavior back?
>>
>> me/2
>
> May be it's YOU or ME, but the filters do expired on me so years ago when
>Usenet was much calmer I usually set to expire in 30 days, then 60 days.
>Now, I am getting older to enjoy all none-sense and vass amount of requests
>so I set my filter to expire in 100 days, still not enough so I increased to
>200 days and lately I changed to 300 days.
>
> IOW, if mine ain't expired like yours then I wouldn't have to go through
>all those troubles.
Sometimes, I set the filter to never expire, and just leave it at
that. If I never see them again, it will be too soon.
pyotr filipivich
or about Mon, 14 Dec 2009 10:59:29 -0500 did write/type or cause to
appear in alt.usenet.offline-reader.forte-agent the following:
><ph...@mindspring.com> wrote, by way of
><0egbi5tu5tgvdf3j8...@4ax.com>, in
>alt.usenet.offline-reader.forte-agent -->
>
><....>
>
>>Just about the time you finally see light at the end of the tunnel,
>>you find out it's a Government Project to build more tunnel.
>
>end of the tunnel is an oncoming train." <g>
Or ... see sig. B=)
pyotr
-
pyotr filipivich
Just when you think you see the light at the end of the tunnel,
you find out it's a 900lb gorilla with a flashlight!!