From: "Steven E. Harris" <seh@panix.com>
To: Greg Troxel <gdt@work.lexort.com>
Cc: dale.hagglund@gmail.com, ding@gnus.org
Subject: Re: does agent expire cached articles when server expires them?
Date: Tue, 17 Feb 2009 07:56:40 -0500 [thread overview]
Message-ID: <uskmdb4s7.fsf@torus.sehlabs.com> (raw)
In-Reply-To: <smufxidtgle.fsf@linuxpal.mit.edu> (Greg Troxel's message of "Tue\, 17 Feb 2009 07\:04\:13 -0500")
Greg Troxel <gdt@work.lexort.com> writes:
> I view it as a bug that the agent retains messages that have been
> deleted on the IMAP server;
Same here. Even though my agent-related expiration duration is /lower/
than my normal mail expiration duration, the agent entries still stick
around until I manually run `gnus-agent-expire-group'. I still don't
understand why agent expiration doesn't happen automatically, or, if it
does, why it refuses to clean up old entries long since deleted from the
backing IMAP server.
--
Steven E. Harris
next prev parent reply other threads:[~2009-02-17 12:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-15 23:44 dale.hagglund
2009-02-17 12:04 ` Greg Troxel
2009-02-17 12:56 ` Steven E. Harris [this message]
2009-03-01 5:28 ` dale.hagglund
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=uskmdb4s7.fsf@torus.sehlabs.com \
--to=seh@panix.com \
--cc=dale.hagglund@gmail.com \
--cc=ding@gnus.org \
--cc=gdt@work.lexort.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).