From: jpranav@nonono.com (Pranav K. Tiwari)
Subject: Re: expire behaviour in nnimap
Date: Thu, 21 Sep 2006 09:57:18 +0530 [thread overview]
Message-ID: <uodt9sv2x.fsf@nonono.com> (raw)
In-Reply-To: <ur6z955v3.fsf@nonono.com>
Any ideas on how to avoid downloading an article while expiring, when it
is already present in agent cache?
-p
jpranav@nonono.com (Pranav K. Tiwari) writes:
> I use nnimap backend, and cache the articles locally using agent. The
> expired articles go into an nnml folder.
>
> When expired articles are moved to the nnml folder, nnimap reads the
> articles from the server, even if agent has a copy. This doesn't matter
> over a fast link, but when I have a slow link, expiring a 5MB article
> takes a lot of time reading it from the server, even if I have a local
> copy. Note that reading an article is fine - it picks it up from the
> copy in the agent cache.
>
> Anyone else seeing this, or is it broken in my config? I'm using:
>
> emacs version: GNU Emacs 21.3.1 (i386-msvc-nt5.1.2600)
> gnus version : No Gnus v0.6
>
> regards,
> -p
>
>
>
> --
> Pranav Tiwari.
--
Pranav Tiwari.
prev parent reply other threads:[~2006-09-21 4:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-22 12:09 Pranav K. Tiwari
2006-09-21 4:27 ` Pranav K. Tiwari [this message]
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=uodt9sv2x.fsf@nonono.com \
--to=jpranav@nonono.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).