Re: Agent downloads too many headers

[Henrik Enberg <henrik@enberg.org>]

kai.grossjohann@uni-duisburg.de (Kai Großjohann) writes:

> Henrik Enberg <henrik@enberg.org> writes:
>
>> WIBNI `gnus-agent-consider-all-articles' could be made to respect
>> `gnus-agent-expire-days' so it only tries to keep all articles frome
>> the last n days in the agent?  My server has some really complex expiry
>> rules, in some groups the articles stay arount for months, but in some
>> groups they expire after just a week or so.
>>
>> It seems like `gnus-agent-consider-all-articles' tries to keep all
>> articles the server knows about in the agent.  This can lead to cases
>> where the agent first expires a bunch of articles and then fetches them
>> again when you do a new fetch.  
>>
>> Or maybe I'm misunderstanding something?
>
> I think you are right.  I did not consider expiry when I made my
> change.  It should, however, be fairly simple to add it: add a
> predicate to the list of agent predicates and then you can use
> `unexpired' or `(not expired)' or whatever in the predicate for the
> category.
>
> Can you do this yourself?

Yes, there's even an example in the manual.  I really need to sit down
and re-read it some day :)

> My long-term goal is to have the agent reflect the server status.  So
> when a message disappears on the server, it should be removed from
> the agent, too.  I don't know how to do that, though.

I'm not all that familiar with the news protocol, but if there's a way
to ask the server for the expiry time of each group, then maybe
gnus-agent-expire-days could have the special value 'server which tells
the agent to expire stuff at the same time the server does.

-- 
Booting... /vmemacs.el